Fork retains upstream audit coverage
stHYPE (Valantis Labs)'s assessment for RD-F-131 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No upstream fork — upstream audit coverage retention factor is not applicable. Protocol has its own independent audit history (6 engagements).
Sources #
- GitHubValantisLabs audits repository — independent audit historygithub.com/ValantisLabs/audits — 6 independent stHYPE auditsretrieved 2026-05-17
- Protocol profile §5 — original implementation.research/protocols/staked-hype/00-profile.md §5retrieved 2026-05-17
Methodology #
Determine whether the fork's deployed code is covered by either: (a) the upstream audit plus a delta-audit for fork-specific changes, or (b) a fresh independent audit of the fork.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol staked-hype factor RD-F-131 score not_applicable collected_at 2026-05-17 13:02:38