Dependency manifest uses unpinned versions
PancakeSwap'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 #
V3 periphery package.json: @openzeppelin/contracts 3.4.2-solc-0.7 (exact version, pinned — green for that dep). pancake-smart-contracts V2 uses @openzeppelin/test-helpers ^0.5.11 (unpinned, but test-only dep). V2 production contracts do not use OZ in core pair/factory. Infinity uses Foundry; library pinning via .gitmodules git-submodule SHAs not inspected — Foundry convention typically pins commits but was not verified. Yellow due to incomplete gitmodules inspection.
Sources #
- GitHubV3 Periphery package.jsonV3 periphery package.json — @openzeppelin 3.4.2-solc-0.7 pinnedretrieved 2026-04-29
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 →