Dependency manifest uses unpinned versions
JustLend 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 dependencies: dotenv ^16.0.1 (unpinned), ethers ^5.7.0 (unpinned), tronweb ^4.3.0 (unpinned). All three use ^ prefix allowing minor version bumps. OpenZeppelin is NOT a dependency. However, these are tooling packages (not deployed on-chain) — the smart contracts themselves have no npm dependencies deployed to TVM. Yellow rather than red because security-critical on-chain code (OZ equivalent) is not unpinned; the unpinned deps are tooling-only.
Sources #
- GitHubJustLend package.json — dependency versionspackage.json: dotenv ^16.0.1, ethers ^5.7.0, tronweb ^4.3.0 — all unpinned with ^retrieved 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 →