Find hardcoded secrets before they ship
Paste code, a config or .env file, or a git diff. Detection uses a library of provider-specific patterns plus a Shannon-entropy check. Everything runs in your browser, in memory only — your text is never uploaded, stored, or logged. Close the tab and it's gone.
Input
Findings (0)
Paste something or load the sample to see findings here.
Nothing to show yet.
How entropy detection works
Shannon entropy measures how unpredictable a string is, in bits per character. English words and identifiers score roughly 2–4; randomly generated keys and tokens score higher (a random 32-character base64 string is near 5). Tokens of 20+ characters that contain letters and digits and exceed the threshold (default 4.2 bits/char) are flagged. Hex strings use a lower bar (3.0) and a 32-character minimum. The slider lets you trade recall against noise.
False positives & limits
Entropy and pattern matching are heuristics. Expect false positives on hashes, minified assets, IDs and test fixtures — and false negatives on low-entropy passwords or secrets split across lines. UUIDs, env var names, placeholders like ${VAR} and lockfile integrity hashes are ignored. Treat any real finding as compromised: rotate it, don't just delete it — removed lines in a diff are still in git history. This tool complements, not replaces, pre-commit scanners like gitleaks or trufflehog.