How it works

Every finding has to earn its verdict.

Guardix maps your system, hunts for bugs in parallel, then puts every finding on trial.

Audit runningStage 4 of 8
  1. 01✓Analyzing codebase6m 24s
  2. 02✓Architecture mapping23m 42s
  3. 03✓Interface analysis11m 12s
  4. 04Security analysis
    Reentrancy and callback checks
  5. 05·Attack vector scan
  6. 06·Specialized analysis
  7. 07·Design review
  8. 08·Validating findings

One run, start to finish. From commit to report in 2 to 10 hours, depending on code size.

373

Checks on every run. Checklist agents work through every one, while specialist agents and attack-vector scans go deeper.

PoolVaultOracleLiquidation

System first. It maps contracts, roles and value flows before it looks for bugs.

Dismissed

Oracle price can go stale

87
88require(age <= MAX_AGE);
89

No citation, no dismissal. A finding is rejected only with the line of code that stops it.

  • Confirmed68
  • Design tradeoff51
  • Dismissed19

A verdict on every finding. What stays unclear goes to a human.

Coverage

What it catches, and what it doesn't

Strongest where an attack can be reproduced and a defense can be cited. Where neither is possible, a human still wins.

Strong at

  • Reentrancy
  • Oracle and price manipulation
  • Access control
  • Accounting drift
  • Unchecked external calls

Where a human still wins

  • Novel attack paths
  • Economic and game-theory design

Run it on your own commit.

Connect a repo, pick a commit, and read the verdicts in one report.