Circom audit tools that prove your circuits are deterministic

Every <-- in a template is a value your constraints must pin down. AI agents review the logic, ZK Vanguard catches likely underconstrained signals, and Picus proves their absence with formal verification.

For Circom templates and circomlib components. Over 96% of ZK circuit layer bugs come from underconstrained logic.

divide.circom reviewed by Scout, ZK Vanguard findings and the Picus Unsafe result with two witnesses.

What AI agents review in your Circom code

Scout reads your templates and the components they wire together, builds a threat model for the circuit, and reports what it finds. It works even before your circuit compiles.

Threat model

What your circuit must guarantee: which signals are public, and what a valid proof should attest.

Template logic

Bit widths, comparator inputs and component wiring, read the way a reviewer would.

Findings backed by tools

Each finding goes to ZK Vanguard or Picus, so it comes back with tool output behind it.

Security tools for Circom circuits

ZK Vanguard catches likely underconstrained signals; Picus proves their absence.

Static analysis for ZK circuits

Detects underconstrained signals, witness leakage, non-deterministic dataflow and unused components across your templates. Results in seconds to minutes.

Formal verification for ZK circuits

Proves every output of your circuit is uniquely determined by its inputs, or returns two distinct witnesses that satisfy the same constraints.

Common Circom vulnerabilities, and the tool that covers each

Most Circom bugs come from the gap between what a template computes and what it constrains.

Common Circom vulnerabilities, and the tool that covers each
VulnerabilityWhat happensCovered by
Assigned, never constrainedA <-- assignment with no matching ===: a prover can set the signal to any value.ZK Vanguard + Picus
Ignored component outputsA circomlib component such as IsZero or LessThan whose output the template never uses.ZK Vanguard
Bit decomposition aliasingNum2Bits over the full field width accepts two binary representations of the same value.Picus
Unchecked comparator inputsLessThan(n) assumes inputs fit in n bits. Without a range check, a false comparison can pass.ZK Vanguard
Division by zero in witness codeAn inverse computed with <-- that breaks, or misleads, when the input is zero.ZK Vanguard
Private input leakageA private signal that reaches a public output and reveals part of the witness.ZK Vanguard

Plus logic errors that are fully constrained but still wrong: Scout reviews those against your threat model.

From Circom finding to formal proof

Scout flags a signal your template assigns with <-- and never constrains. Picus verifies the circuit and returns the evidence: two distinct witnesses that satisfy every constraint.

divide.circom flagged by Picus: Unsafe with two witnesses for the same inputs, results across three circuits and the Picus check.
Finding (Scout) → Evidence (Picus): two witnesses

Fits your Circom and circomlib toolchain

Keep writing templates with circom and circomlib, and keep your prover. Determinism is a property of your constraints, so the result holds whether you prove with Groth16, PLONK or fflonk.

// 001

Connect your repository

Your Circom templates on GitHub.

// 002

Run on every commit

ZK Vanguard and Picus run in GitHub Actions and report during development.

Working with a coding agent? Run AuditHub’s tools from your session through AuditHub MCP.

Alongside your Circom audit

ZK Vanguard and Picus check your templates on every commit, so your auditors start from circuits Picus has already verified and spend their time on protocol logic. The audit still gives you a signed expert review.

Before audit

During audit

After audit

ZK Vanguard // EVERY CHANGE
ZK Vanguard task summary: steps, findings and artifacts.
AuditHub ZK Vanguard check on a pull request.
ZK Vanguard recent tasks across versions v1 to v3.
Picus // EVERY CHANGE
Picus task summary: steps, findings and artifacts.
AuditHub Picus check on a pull request.
Picus recent tasks across versions v1 to v3.

Picus in production at RISC Zero

RISC Zero runs Picus in its CI to verify determinism across its zkVM circuits. 35 issues were found and mitigated during development, and every new change is checked as the code evolves.

Other languages AuditHub checks

Circom security FAQ

What is an underconstrained signal in Circom?

A signal your constraints do not pin to a single value. It usually comes from a <-- assignment with no matching ===, and it lets a prover create a valid proof for a wrong result.

Can Picus prove a Circom circuit is deterministic?

Yes. Picus returns verified when every output is uniquely determined by the inputs, unsafe with two distinct witnesses when it is not, or unknown when it can give neither.

How do ZK Vanguard and Picus work together?

ZK Vanguard runs first and catches likely underconstrained signals in seconds to minutes. Picus follows and proves their absence, or returns a concrete counterexample.

Do these tools replace a Circom audit?

No. They check your circuits continuously between audits, and the audit gives you a signed expert review.

Still have questions? Contact us

Learn more about Circom

Prove your Circom circuits are deterministic before launch

Run ZK Vanguard and Picus on your templates today.