CAIN-42 CAIN Studiocain_audit: the deliverable
The tool that turns CAIN-42's engines into something a client pays for. One command scans a codebase, writes the report, signs it, bundles the evidence with a standalone verifier, and refuses to hand anything over that fails its own verification.
#5 of the CAIN-42 Top 25 self-test 6/6 41 tests pass no paid audit delivered yet
to scan, report, sign, bundle and self-verify a 24-file project
independent checks a client can run: the signature, and "is this about my code"
CAIN imports in either client-side checker
Standard fabrication audit (48 hours)
Why this is the money part
CAIN-42's operating plan is to use the technology daily to deliver paid work, not to sell a platform. cain_audit is where that happens: it is the difference between "we have a detector" and "here is your signed audit, and here is how you check it without trusting us."
One command
python3 -m cain_audit.cli audit ./client-repo --client "Acme" --tier standard \
--notes review.md --reviewer "Reviewer Name"
Produces report.md, findings.json, evidence.zip (signed record + report + findings + key +
verifier) and the run's signed ledger. Exit code non-zero if the bundle fails its own verification.
On this site
How it works
Collect, scan, report, sign, bundle, self-check.
The deliverable
Every section of the report, explained.
A real sample
The full report from a real run, plus the files.
Live demo
Hash the sample in your browser; scan a file.
Evidence
Tamper tests, code-check tests, test suites.
Verify it yourself
Check the sample as a client would.
The product line
Seven deliverables and their prices.
Limits
What a report can and cannot tell you.
2026-11-02 upgrade
Four gaps a client would have found.
FAQ
Questions buyers ask.
FIRME AI CORPORATION · CAIN-42 is a Byzantine trust fabric. Numbers marked "our own check" were run by us, not by an independent party. Nothing on these pages is a certification.