Understanding Reports
Learn how to read, interpret, and act on your smart contract security audit reports.
Report Overview#
Every audit generates a security report showing vulnerabilities found in your smart contract code, organized by severity.
Findings Summary
Breakdown of vulnerabilities by severity: Critical, High, Medium, Low, and Info.
Code Locations
Exact file path and line numbers for each vulnerability found.
Fix Recommendations
Actionable remediation advice for each finding with code examples.
PDF Export
Download a professional report to share with your team or stakeholders.
Severity Levels#
Each finding is classified by severity to help you prioritize fixes:
| Severity | Description | Action Required |
|---|---|---|
| Critical | Directly exploitable with significant financial impact | Fix immediately |
| High | Exploitable under specific conditions | Fix before deployment |
| Medium | Potential issue that could become exploitable | Fix recommended |
| Low | Minor issue with limited impact | Consider fixing |
| Info | Best practice or optimization suggestion | Optional |
Finding Details#
Each individual finding includes:
- Title — Name of the vulnerability (e.g. "Reentrancy in withdraw()")
- Severity — Color-coded badge (Critical through Info)
- CWE ID — Common Weakness Enumeration reference for industry context
- File & Line — Exact location in the source code
- Description — What the vulnerability is and how it could be exploited
- Code Snippet — The vulnerable code block
- Recommendation — How to fix the issue with concrete guidance
Export Options#
Reports can be exported for sharing with your team or stakeholders:
- PDF — Professional format with all findings, code snippets, and recommendations
Clean Audit#
If no vulnerabilities are found, the report shows a clean audit result. This means our AI did not detect any issues in the analyzed categories for your audit tier.