Code complexity vs audit coverage
Midas's assessment for RD-F-024 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Four audit engagements covering the full contract suite (24 contracts in Sherlock 2024-08 scope). Test coverage 100% per Sherlock 2024-05 README (109/109 statements). Audit breadth appears adequate for the contract count. However, the private main repo prevents independent LOC/complexity assessment via Slither metrics, and the second Hacken engagement has unconfirmed date/scope. Yellow as a conservative assessment given private repo opacity on current HEAD complexity versus audited commit complexity.
Sources #
- GitHubSherlock 2024-05 MidasSherlock 2024-05 README — 100% test coverage, 13 contracts in scoperetrieved 2026-05-16
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 →