Dependency manifest uses unpinned versions
stHYPE (Valantis Labs)'s assessment for RD-F-133 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No public Solidity contracts repository found for stHYPE. The sthype-sdk repo is TypeScript only; no foundry.toml is available for the stHYPE contracts. Cannot assess dependency version pinning.
Sources #
- InternalData cache — no foundry.toml found.research/protocols/staked-hype/00-data-cache.json github.foundry_toml_present: falseretrieved 2026-05-17
- ValantisLabs GitHub org — no public Solidity contracts repogithub.com/ValantisLabs — no stHYPE Solidity contracts repo foundretrieved 2026-05-17
Methodology #
Determine whether `package.json`, `Cargo.toml`, or `foundry.toml` uses `^` or `~` version ranges for security-critical libraries (OpenZeppelin, Solady, etc.).
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol staked-hype factor RD-F-133 score gray collected_at 2026-05-17 13:02:38