YEET LABSYEET LABSSubmit idea →
SCAN. TEST. SURVIVE.

The
Gauntlet.

REAL SECURITY. REAL TESTING. REAL BUILDERS.

A release-blocking security orchestrator. It scans contracts, frontend, backend and deployment code, scores the result, and blocks anything unsafe or incomplete.

Submit to Gauntlet →▷ How it works
Alice in the Gauntlet arena
Good code
survives.

Scan status

● Published scan index
Loading…Verified verdicts appear here from the scan index. Public reports are summary-only.

Gauntlet flow.

01
SUBMIT
Project enters the Gauntlet with gauntlet.yml, threat model and invariants.
02
SCAN
Slither, Echidna, Semgrep, Gitleaks, Foundry tests, npm/pip audit and built-in checks.
03
VERDICT
Findings normalized, scored and graded. Missing required tools fail closed.
04
HERMES
Blocked builds get a fix prompt. Patch the root cause, rerun the full scan.
05
SURVIVE
Passing builds move on to human and independent review.
↺ If security or tests fail, it returns to Hermes for fixes — max 3 rounds, then blocked. A scanner that can't run is an infrastructure issue, not a code finding.

Verdicts

✕BLOCKED
Exploit, failed required check, missing required tool, or score below 85.
◐STATIC_ONLY
Static review of untrusted code. Never a launch approval.
◇TESTNET_ONLY
Checks passed, but the risk tier requires independent review.
!REVIEW_REQUIRED
No automatic blocker, but score is below the pilot threshold.
✓CAPPED_PILOT_CANDIDATE
No blocker found. Launch limited to the stated cap and exact reviewed release.
A
95–100
B
85–94
C
70–84
D
50–69
F
0–49

A high score never overrides a Critical or High finding. A pass applies only to the exact commit and configuration scanned — it is not a safety certificate or formal audit.

Survivors
Confirmed passing reports, tied to a commit.
ENTER →
Cemetery
Blocked, killed and failed — honestly recorded.
ENTER →
Security
Disclosure policy, scanner limits, audit warnings.
ENTER →