The KeyDrift CLI: scan from your terminal
`keydrift <url>` — exit codes that mean what they say: 0 clean, 1 findings, 2 could-not-scan. JSON output for machines.
Pipelines conflate scanner-failure with app-leaking at their peril.
Usage
# humans:
npx tsx apps/cli/src/main.ts https://app.example.com
# machines:
npx tsx apps/cli/src/main.ts <url> --json --fail-on highExit-code philosophy
0 clean · 1 findings · 2 scanner-failed. Conflating two with one trains teams to disable tooling after outages; separation keeps trust.
Same-engine guarantee
The CLI wraps the identical detection catalog powering the website — fixtures, dispositions, masking included. What CI says matches what /scan shows.
Recipe
Post-deploy job: scan production URL, fail pipeline on exit 1 above threshold, notify via existing plumbing — three lines of YAML.
Why this keeps happening industry-wide
Zoom out and the pattern is bigger than one repo. AI-assisted output has outgrown review capacity everywhere at once, which means thousands of teams are making the same reasonable-looking tradeoffs in the same week. Nobody using modern tooling is uniquely exposed. The failure mode documented above is the modal outcome of velocity without verification, not evidence of carelessness.
How KeyDrift reports this exact finding
Report anatomy matters during incidents, so it is worth reading once calmly: masked string (never the live value — it ceases to exist outside the detection engine), salted fingerprint (trackable within your workspace, useless to strangers), chunk path (your starting point for a "git log -S" hunt), disposition (secret versus public-by-design), confidence (matches below 0.5 never reach the page at all).
Manual check, step by step
The full manual drill, for readers who want zero dependence on any tool: open the deployed site in a private window; launch DevTools → Sources; use Search-all-files (Ctrl/Cmd+Shift+F) for eyJ; then repeat for the other marker families — eyJ, sk_live_, sk-proj-, AKIA, postgres, BEGIN PRIVATE KEY. Decode anything JWT-shaped before reacting, and classify public-by-design formats as expected guests rather than intruders.
Close the loop with monitoring
If you take one operational step from this page, make it this: put the URL under continuous monitoring (free tier covers one project daily). The first scan tells you whether you have a problem today; the schedule tells you whether the problem comes back next month after someone re-adds the convenient line.
What the plans change
- Free $0 — 1 project · daily scans · email alerts · findings always visible.
- Indie $29/mo — 3 projects · hourly · Slack added · 80 chunks per scan.
- Team $89/mo — 15 projects · every 15 minutes · Discord + webhooks · 150 chunks.
- Growth — from $249/mo, quoted display-only until checkout ships.
The constant across every tier: plans limit how much is watched, never what a scan found. Visibility is structural, not promotional — asserted by tests over the entitlements model itself.
Common questions
Windows support?
Anywhere Node 22 runs — Windows terminals natively.
Offline scanning?
URL mode needs network by definition; paste mode accepts local bundles.
Run a free scan at keydrift.dev/scan — paste a URL or the bundle source itself, no account. Findings arrive masked, with the exact chunk they live in.