Dependency manifest uses unpinned versions
Lista DAO'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 #
package.json: @openzeppelin/contracts pinned at 4.6.0 (locked — good), @openzeppelin/contracts-upgradeable pinned at 4.6.0 (locked — good), @chainlink/contracts uses ^0.4.1 (not pinned — will resolve to latest compatible minor). .gitmodules: forge-std submodule has NO pinned commit SHA. OZ (security-critical) is pinned; forge-std (development tooling) and Chainlink are not fully pinned.
Sources #
- GitHubLista DAO .gitmodules.gitmodules — forge-std submodule with no pinned commit SHAretrieved 2026-05-12
- Lista DAO package.json Dependenciespackage.json — @openzeppelin 4.6.0 locked; @chainlink/contracts ^0.4.1 unpinned; .gitmodules — forge-std no commit SHAretrieved 2026-05-12
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 →