RepoAudit. Prove what’s exploitable.
Binary-aware verification that finds real zero-days and ships a working exploit with every one. Under 10% false positives — the industry runs over 50%.
- <10% false positives
- Deep reachability
- Zero-day discovery
- PoC with every finding
- CVE-2024-3094 · xz-utils 5.6.1
- CVE-2023-44487 · nghttp2 1.55
- CVE-2024-21626 · runc 1.1.11
- CVE-2023-4863 · libwebp 1.3.0
- CVE-2022-42889 · commons-text 1.9
- CVE-2021-44228 · log4j-core 2.14
- CVE-2023-2650 · openssl 3.0.8
- CVE-2024-24790 · go net/netip
- ZERO-DAY · custom tokenizer.so
- CVE-2024-27980 · node 20.11
- CVE-2023-45853 · zlib 1.3
- CVE-2024-2961 · glibc 2.39
analyzing compiled artifact… tracing call graphs through dependencies… discarding unreachable findings… building proof-of-concept exploits… writing kill-chain + fix… scan complete
- scan
- reach
- prove
- candidate
- tracing
- queued
- unreachable
- reachable
- proving…
- exploit · poc
- zero-day · poc
- no exploit
- cves
- reachable
- proven
Can the software this
agent runs on be trusted?
- traditional SCA — matches names to CVE lists, buries you in unreachable criticals
- RepoAudit — proves what is actually exploitable, with a working exploit
Before you trust the agent, trust the substrate underneath it.
Scan. Reach. Prove.
No source code required. A finding only surfaces if it’s reachable — and every one ships with proof.
- 01
Scan
Analyzes compiled artifacts, containers and CI/CD output — no source code required.
binaries · containers · sbom · ci output - 02
Reach
Traces call graphs through the full dependency tree. A finding only surfaces if it is actually reachable.
entrypoint → call graph → vulnerable sink - 03
Prove
Ships a working PoC exploit, kill-chain, reproduction command and fix with every finding.
poc.py · killchain.md · repro.sh · fix.patch
- Snyk
- Socket
- Endor
- Black Duck
Evidence, not hedge language.
- 01 Binary-aware Sees compiled components source-only tools never catch.
- 02 Reachability-first Only flags what’s actually exploitable in your context.
- 03 Proof-backed A working exploit with every finding — not a guess.
- 04 Pipeline-native Deployable in any CI/CD, no frontier-model access required.
- 01 Binary-aware Found in a statically linked binary. Present in the fat JAR. Unlisted component — no CVE exists. pass pass pass checking
- 02 Reachability-first Reached from the /auth handler. Vulnerable sink never reached. Reached via untrusted model input. pass fail pass checking
- 03 Proof-backed PoC executes; kill-chain attached. No exploit path — not surfaced. Zero-day PoC + repro command. pass partial pass checking
- 04 Pipeline-native Blocked the release in CI. Attestation signed; release allowed. Agent authority lowered via TIM. pass pass pass checking
An exploit becomes a trust signal.
Inside the platform, a newly reachable exploit doesn’t just open a ticket. It lowers the agent’s authority, blocks sensitive data, or triggers requalification — automatically, through TIM.
- allowed
- requalify
- blocked
- Production deploys ci → prod
- Customer data access PII · PHI via PromptVault
- Credential rotation vault write
- Read-only telemetry metrics · logs