Dependency manifest uses unpinned versions

Midas's assessment for RD-F-133 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

This factor measures fork-lineage dependency manifest pinning. As an original issuer with no upstream lineage to track, this factor is not applicable. Additionally the main repo is private (U6 safe_api_gap), preventing independent manifest inspection.

Sources #

Curator note
Profile §4 and §5Profile §4 — github_private:true (U6); Profile §5 — original issuerretrieved 2026-05-16

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 midas factor RD-F-133 score not_applicable collected_at 2026-05-16 09:34:55