Dependency manifest uses unpinned versions
Spiko's assessment for RD-F-133 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
EVM package.json uses caret versioning: @openzeppelin/contracts ^5.4.0 and @chainlink/contracts ^0.8.0 - allows minor/patch updates, not exact pinning. This is a yellow finding per taxonomy (OZ and Chainlink not pinned to exact versions). Soroban Cargo.toml pins soroban-sdk to exact version 22.0.8 (green). Cairo package management not directly inspected.
Sources #
- GitHubspiko-tech/contracts package.jsonpackage.json OZ ^5.4.0 and Chainlink ^0.8.0 caret versioningretrieved 2026-05-16
- spiko-tech/stellar-contracts Cargo.tomlCargo.toml soroban-sdk = 22.0.8 exact pinningretrieved 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 spiko factor RD-F-133 score yellow collected_at 2026-05-15 22:52:13