Smart contract auditing tools free to start, built on formal methods

For protocol engineers: static analysis, specification guided fuzzing and proof for ZK circuits, run by AI agents or on their own, all four included in every plan.

Trusted by RISC Zero, Succinct and Matter Labs.

One findings table with results from Vanguard, OrCa, ZK Vanguard and Picus, the four checks on a pull request and the Picus Unsafe result.

Trusted by

Four security tools for smart contracts and ZK circuits

Each tool applies one method to your code and returns evidence you can check.

Static analysis

Catches reentrancy, unchecked returns and unsafe patterns across contract boundaries.

Specification guided fuzzing

Tests your contracts against the behavior you specify in [V], and returns exact inputs and traces when a property fails.

Static analysis for ZK circuits

Catches likely underconstrained signals, witness leakage and non-deterministic dataflow.

Formal verification for ZK circuits

Proves your circuits are deterministic, or returns a concrete counterexample.

All four are included on every plan, Free included, at full strength. Compare plans

How the security tools work together

Two pairs, one shape: a fast static pass flags suspects, then a deeper tool returns a failing input or a proof. ZK Vanguard catches likely underconstrained signals; Picus proves their absence.

Smart contracts

Vanguard

Flags suspects

OrCa

Returns a failing input

ZK circuits

ZK Vanguard

Flags suspects

Picus

Returns a proof

Choose the right smart contract security tool

Match the tool to your language and to what you need back.

Vanguard, OrCa, ZK Vanguard and Picus compared by method, languages, output and when to run them
ToolMethodLanguagesReturnsRun it when
VanguardStatic analysisSolidity, on Foundry or HardhatGrouped findings with call graphs and value flowOn every commit, for breadth
OrCaSpecification guided fuzzingSolidity, Rust, SorobanExact inputs and traces for every violationYou can state the behavior you expect
ZK VanguardStatic analysis for ZK circuitsCircom, Halo2, Plonky3, ZirgenFindings in seconds to minutesOn every commit, before proof
PicusFormal verificationCircom, Halo2, Plonky3, ZirgenA proof of determinism, or a counterexampleYou need certainty

Run by AI agents or on their own

Let Scout pick the right tool for each finding, call Vanguard and OrCa from your coding agent through AuditHub MCP, or run them yourself in GitHub Actions on every commit.

GitHub Actions

The tools on every commit, during development.

Smart contract auditing tools, field-tested on 150+ audits

On RISC Zero’s zkVM, Picus surfaced 35 issues during development, running in CI as the code evolved. All four tools were calibrated on 150+ security audits by Veridise auditors.

Smart contract auditing tools FAQ

What are smart contract auditing tools?

Software that checks contract and circuit code for vulnerabilities, before and between audits. AuditHub’s four tools cover static analysis, specification guided fuzzing and formal verification.

What is the difference between static analysis, fuzzing and formal verification?

Static analysis examines code without running it. Fuzzing runs it against many generated inputs. Formal verification proves a property holds for every possible input.

Which tool should I start with?

For Solidity, start with Vanguard, then add OrCa once you can describe the behavior you expect. For ZK circuits, run ZK Vanguard first, then Picus for proof.

Do I need an AI agent to use the tools?

No. Run them on their own in GitHub Actions, through Scout, or, for Vanguard and OrCa, from your coding agent with AuditHub MCP.

Are all four tools on the Free plan?

Yes. Every plan, Free included, runs the same four tools at full strength.

Still have questions? Contact us

Learn more about smart contract security tools

Run all four security tools on your code

Connect a repository and see what the tools catch and prove.