⊘
.env Editor and Secret Scanner
Parse and tidy a .env file — comments kept, quotes and escapes per dotenv — and run 25 credential patterns over the values, graded definite / likely / low entropy / placeholder. All local, nothing stored.
Runs in browserSecret.env
Loading tool…
How to use
- Paste a .env into the editor: comments and blank lines are kept verbatim, and quotes, export prefixes and escapes follow dotenv.
- An unquoted value containing # is kept whole rather than treated as a comment — that is what dotenv does, and the only choice that never truncates a password.
- The scan runs the pattern table over each value and grades it: definite format, likely shape, low entropy, placeholder. Only the first two count as to-handle.
- Placeholders such as your_key_here or the AWS documentation string AKIAIOSFODNN7EXAMPLE are still listed, marked as placeholders, so you can see they were seen rather than assume the tool missed them.
- The any-text tab scans logs and code, but without the variable-name weighting, so the same match may grade one level lower.
- After a hit the right move is to rotate that credential, not just delete it from the file: it already exists everywhere you pasted it.
- This is a heuristic, not a guarantee: an unrecognised credential will not match, and no hit does not mean no leak.