A short guide to Secret Leak Scanner
Check the rule, then test the assumption.
Scan pasted text locally for secret-shaped values and explain what to rotate or remove. Here is the practical way to prepare the input, read the output, and decide what to check next.
01
When to reach for it
Checks text against the reviewed AWS, private-key, Stripe-like, JWT-shaped, email, and credential-assignment patterns. It is most useful when you are dealing with credential in diff or API key. Start with the smallest example that still shows the behavior.
- Look for credential in diff, API key, private key.
- Reduce the example until one observation can change the result.
02
How to prepare the input
Paste a focused example in logs, diffs, fixtures, or source text. Leave out unrelated noise so the result stays easy to verify.
- Use the accepted format: logs, diffs, fixtures, or source text.
- Keep the facts that make the behavior reproducible.
- Do not treat missing context as a reason to invent an answer.
Example input
Safe sample
apiKey=[REDACTED_SECRET] normal=value
Run this first to see the shape of the result. Then change one meaningful fact and confirm that the output changes with it.
03
How to read the result
Lists the supported secret-shaped pattern categories found in the supplied text. Read the finding beside the evidence that produced it. The result narrows the next check; it does not claim to have changed your system.
- Separate the observed fact from the suggested next check.
- Prefer the smallest reversible experiment that can confirm or reject the finding.
- Save the output when it belongs in an incident note, review, or handoff.
04
Know the boundary
A rule finding is a focused lead, not proof that the surrounding system has no other failure.