Audit count
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-004 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Distinct audit firms per component: v2 = PeckShield (1); v3-core = ABDK + ToB (upstream Uniswap only, not Sushi-specific); RP3 = Zellic (1 Sushi-specific). BentoBox = PeckShield + Certora FV. MISO = Code4rena. At the protocol level ≥3 firm names appear, but no single deployed sub-component has ≥2 independent Sushi-specific auditors. Threshold: yellow = 1 firm; green = ≥2 distinct firms. The v2-core component has 1 firm (PeckShield); v3-core has 0 Sushi-specific firms.
Sources #
- AuditZellic SushiSwap RouteProcessor3 AuditZellic RP3 (1 Sushi-specific firm for RouteProcessor3)retrieved 2026-05-17
- sushiswap/v3-core audits directory (ABDK + ToB)ABDK + ToB in v3-core audits dir — upstream Uniswap v3 reports, not Sushi-specificretrieved 2026-05-17
- PeckShield-Audit-Report-SushiSwap-v1.0.pdfPeckShield v2 audit (1 firm for v2-core)retrieved 2026-05-17
Methodology #
Count the number of distinct audit firms whose reports cover any portion of the currently-deployed bytecode.
See the full factor methodology and distribution across all protocols →