Open source · runs in your environment

89% of Klarion's alerts are a real secret.

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.

Install Read the benchmark
Measured on CredData: 337 real repositories, code outside test folders. Klarion also found about 1.7x more real secrets than gitleaks. Method and caveats.
$ klarion scan .

✔ 1,204 files scanned in 612ms
  2 secrets · 198 suppressed

CRITICAL  aws secret key
  config/prod.env:14
  verdict: SECRET · 0.97, production
  config, not a fixture

HIGH      stripe key
  services/billing.py:39
  verdict: SECRET · 0.96, sk_live in app code

198 suppressed — fixtures, placeholders,
look-alikes. audit: --show-suppressed
Why Klarion

Scoped, explained, and checked before it reaches you.

Detection was never the hard part. Trusting the alert is.

Adjudicated, not guessed

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%. Across 61,514 files of Java, Go, TypeScript and PHP it reported 11 findings — gitleaks 361, detect-secrets 12,073.

candidates  5,571
verdict: secret  12
verdict: noise  5,559

A reason for every finding

Not "high-entropy string, line 42." You get what it is, why it's a secret, and how to fix it.

"Git commit SHA pinned to
actions/checkout — version
pin, not a secret."

Runs where your code lives

Open-source engine on your machine or in your CI. Only each candidate and a few nearby lines go to the model you choose; with a local Ollama model nothing leaves.

$ brew install 0x1Adi/tap/klarion
→ no telemetry · no account
→ MIT licensed
Demo

It blocks the write, not the pull request.

A coding agent is told to hardcode an AWS key pair. The pre-tool hook stops it before the file exists — and the agent cannot route around it through Bash either.

A coding agent is told to hardcode an AWS key pair. Klarion's pre-tool hook blocks the write at 95 percent confidence, and the agent reports it cannot land the credentials through Bash or the file tools.
Blocked at 95% confidence. In the agent's own words: “Blocked — not by me this time.”
Compare

Open and trustworthy.

Regex tools are open but noisy. Closed platforms are precise but you can't see the engine.

 KlarionGitleaksTruffleHogGitGuardian
Open-source coreYesYesAGPLCLI only
AI verdict + reasonYesNoNoFilter
Published precision benchmarkYesNoNoNo
Runs in your environmentYesYesYesPartial
Open source

Free, and the whole engine is in the open.

Klarion
Free
MIT licensed · available now
  • CLI, GitHub Action, GitLab CI, commit hooks
  • Claude Code plugin and MCP server
  • Bring your own model, or let your agent judge
Install
provmcp
Soon
The other half of the gate
  • Catches npm supply chain attacks
  • Before npm install runs
  • Klarion guards what you write, provmcp guards what you pull in
Coming soon

Nothing to buy today. Klarion is open source and stays that way.
No API key? A hosted version with no setup is coming. Join the list.

Stop triaging false positives.

Drop Klarion into one repo and see the real leaks in five minutes.

Install