Solidity Scanners
Solidity Scanners: How Static Analysis Finds Smart Contract Bugs
How static analysis reads your Solidity code, which bug classes it catches, and where it stops.
Vanguard detects reentrancy, access control issues and unsafe patterns, groups related findings, and runs in GitHub Actions.
For Solidity projects on Foundry or Hardhat.
Calibrated on 150+ security audits.

Each built-in detector targets one vulnerability class and reasons about how your code behaves, not just how it reads.
// 001
Reentrancy across multiple contracts, including read-only reentrancy through shared storage.
// 002
External calls whose return values are never validated.
// 003
Precision loss caused by operator order.
// 004
Variables read before they are initialized.
// 005
Logic an attacker can exploit within a single flash loan transaction.
// 006
Funds that can end up stuck inside a contract.
Plus 11 more built-in detectors, from missing or incorrect access control and low-level call hijacking to unsafe ERC20 approvals, ERC4626 checks and Uniswap callback validation, and custom detectors for your own patterns.
Vanguard uses abstract interpretation to model your contracts. It follows calls and value across contract boundaries, so it understands interleaved transactions a pattern match would miss.
// 001

Foundry or Hardhat, Solidity 0.8.4 and newer.
// 002

Pick your detectors, Vanguard models every contract and call path.
// 003

Each report comes with call graphs, value flow and inferred access controls.
Scout flags a suspicious call path in your protocol. Vanguard checks it and returns the evidence: the call graph, the value flow and the exact lines involved.
Scout AI - Findings
Line 11
Suspicious call path in withdraw
Vanguard - Evidence
Cross-contract reentrancy detected
The call graph, the value flow and the exact lines involved.
// CROSS-CONTRACT REENTRANCY
Write detectors in a concise query language, share them across your organization, or start from the standard library for ERC20, ERC4626 and Uniswap patterns. They run on the same engine and land in the same findings table.

Vanguard runs in your CI and reports during development, not after the fact. Mark a root cause once and every related false alarm clears in bulk.
Working with a coding agent? Run Vanguard from your session through AuditHub MCP.
Vanguard runs first, for breadth. OrCa follows and fuzzes your contracts against the behavior you specify in [V], returning exact inputs and traces when a property fails.
Detects unsafe patterns across contract boundaries, for breadth.
// 01 Vanguard
Tests whether your contracts honor the behavior you specify.
// 02 OrCa
Explore OrCa →Vanguard checks your code continuously, so your auditors start on cleaner code and spend their time on design and logic. The audit still gives you a signed expert review.
Before audit
During audit
After audit



It examines your contract code without executing it to find vulnerabilities before deployment. Vanguard goes further than pattern matching: it models how your contracts behave across calls.
Solidity 0.8.4 and newer, on Foundry and Hardhat projects.
Its detectors are calibrated on 150+ security audits, related findings are grouped, and marking a root cause clears linked false alarms in bulk.
Yes. Custom detectors use a concise query language and run on the same engine as the built-in ones.
No. It checks your code continuously between audits, and the audit gives you a signed expert review.
Still have questions? Contact us
Solidity Scanners
How static analysis reads your Solidity code, which bug classes it catches, and where it stops.
Solidity Security
Twelve practices for Solidity code, from access control to external calls, with the bugs each one prevents.
Security Tools
What static analysis, fuzzing and formal proofs each catch, and how they fit together in one workflow.
Run Vanguard on your Solidity code today.