Fast local checks flag anything that looks like a secret. Then a model reads each one with the code around it and rules out the fixtures, placeholders and identifiers. You triage what is left.
$ klarion scan . --explain ✔ 1,204 files · 3,180 commits 2 secrets · 198 suppressed CRITICAL aws secret key config/prod.env:14 verdict: SECRET · live credential, S3 write access HIGH stripe key services/billing.py:39 verdict: SECRET · live payments key 198 suppressed — dead keys, fixtures, look-alikes. audit: --show-suppressed
Detection was never the hard part. Trusting the alert is.
An AI issues a verdict on every candidate: real secret or noise. On CredData, 89% of what it let through was real. detect-secrets: 34%.
Not "high-entropy string, line 42." You get what it is, why it's a secret, and how to fix it.
Open-source engine on your machine. Your code and secrets never leave — and you can verify that.
Regex tools are open but noisy. Closed platforms are precise but you can't see the engine.
| Klarion | Gitleaks | TruffleHog | GitGuardian | |
|---|---|---|---|---|
| Open-source core | Yes | Yes | AGPL | CLI only |
| AI verdict + reason | Yes | No | No | Filter |
| Published precision benchmark | Yes | No | No | No |
| Runs in your environment | Yes | Yes | Yes | Partial |
npm install runsNothing to buy today. Klarion is open source and stays that way.
Drop Klarion into one repo and see the real leaks in five minutes.
Install