Skip to content
We manage your security to weather the AI storm →
Portfolio · Findings database

Smart contract audit findings database

The database lists the findings from Guardian's public audit reports. Search by keyword, or narrow the list by severity, fix status, chain, sector, language, team or vulnerability class.

9,100+ findings from 300+ public reports, published from March 2022 to November 2026. Each one links to its place in the report.

The database in numbers

Findings
9,100+
Critical and high
1,100+
Public reports
300+
Teams
95+

The data

What the findings show

By severity

Every finding in the database, by severity.
  • 320+Critical3%
  • 800+High8%
  • 2,000+Medium22%
  • 3,900+Low43%
  • 2,000+Informational22%

76% of the critical and high findings are marked resolved in their reports.

The team's response to each finding, by severity, as its report records it. Shares are rounded down.
SeverityFindingsResolvedPartialAcknowledgedOther
Critical320+87%3%6%2%
High800+71%4%18%5%
Medium2,000+53%2%36%6%
Low3,900+49%1%43%5%
Informational2,000+42%1%48%7%

By chain

Chains with ten or more public reports. A report on several chains counts toward each.
ChainReportsFindingsCritical and high
Arbitrum130+4,000+600+
Ethereum120+3,700+410+
Base60+2,600+310+
Avalanche45+1,100+180+
Optimism45+1,300+150+
Polygon30+640+50+
Hyperliquid30+520+40+
BNB Chain25+570+60+
Monad15+240+8
Ink10+95+0
Solana10+400+25+
Blast10+250+60+

By sector

Sectors with ten or more public reports. A report in several sectors counts toward each.
SectorReportsFindingsCritical and high
Perpetuals75+2,700+400+
Stablecoins50+700+15+
Infrastructure25+660+40+
DEXs and AMMs25+1,300+210+
Cross-chain20+410+10+
Token launches20+590+130+
Yield and vaults20+910+150+
Lending20+730+90+
Derivatives15+970+100+
Tokens15+430+25+
Staking10+510+45+
AMM hooks10+630+85+
NFTs10+220+15+

By vulnerability class

Findings by vulnerability class. Classes come from fixed rules; the rest are filed under Other.
ClassFindingsCritical and high
Access control140+35+
Oracles and price feeds230+20+
Reentrancy70+8
Rounding and precision260+25+
Signatures and replay100+6
Liquidations260+65+
Slippage, front-running and MEV200+40+
Upgrades and initialization80+4
Accounting errors70+20+
Input validation960+70+
Denial of service and griefing690+160+

By language

Findings by the language of the code in scope.
LanguageReportsFindings
Solidity270+8,500+
Rust15+470+
TypeScript5190+
Soroban425+
JavaScript325+
DAML2100+

Method

About this data

  • Each finding is shown as its published report records it: ID, title, severity and the team's response. The report PDF in the GuardianAudits repository is the version of record.
  • Status is the response recorded when the report was published. A fix shipped later may not be reflected.
  • Chains and sectors follow the portfolio's tags for each report. A report tagged with several counts toward each of them.
  • Vulnerability classes come from fixed rules over the report's own category and the finding's title. In a hand check of a random sample, 95% were classed correctly. Findings the rules cannot place are filed under Other.
  • The database updates when a new public report is published. The latest is dated November 11, 2026.
  • To cite it: Guardian Security, Smart contract audit findings database, https://guardian.security/portfolio/findings/

Put your code through the same review.

Every finding here started with a conversation about scope. Tell us what you are building and we will plan the review with you.

Get a quote