POLICY. LIMITS. DISCLOSURE.
Security
first.
How we scan, what our results mean, what they don’t, and how to report a vulnerability.

Trust
the
process.
the
process.
Reading statuses
awaiting reviewWaiting on a human decision.
pausedHermes job registered, waiting for owner resume.
scan unavailableA required scanner couldn’t run. Infrastructure issue, not a finding.
blockedA blocker remains or fix rounds ran out.
killedRejected by admins.
readyPassed on the exact commit. Not deployed.
deployedA human merged and released it.
Scanner limits
01
Not a certificate
A Gauntlet pass is not a formal audit or safety guarantee.
02
Exact commit only
Any new commit after a pass needs a fresh scan.
03
Funds need audits
Projects touching funds require independent review before launch.
04
Static for strangers
Untrusted code gets static-only scans. Never a launch approval.
Published scans
○ IndexLoading…Summary only: score, grade, verdict, severity counts and check statuses. Never file paths, line numbers or unresolved findings.
Responsible disclosure
Report vulnerabilities privately — never in public issues. Give us time to fix before disclosure. Public scan reports are summary-only: no file paths, line numbers or unresolved findings.
