Code complexity vs audit coverage

Jupiter's assessment for RD-F-024 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Slither complexity metrics and LOC/audit-day ratio computation require Etherscan-verified Solidity source and EVM tooling. Closed-source Rust/BPF binary precludes computation. Qualitatively, 17 engagements across all major sub-protocols suggests adequate coverage by breadth, but the methodology requires computed metrics. Gray.

Sources #

Docs
Jupiter Audit Reports — Jupiter DevelopersAudit index — 17 engagements across sub-protocols (qualitative breadth evidence only)retrieved 2026-04-29

Methodology #

Determine whether the cyclomatic complexity or LOC-per-audit-day ratio exceeds the curator-declared credibility threshold for the audit to be meaningful.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol jupiter factor RD-F-024 score gray collected_at 2026-04-29 11:51:25