~/care
Defensive only. No exceptions.
A tool that finds credentials can help the person who leaked them or the person hunting them. Leaksweep is built, in its code and in its terms, to be useful only to the first.
if you are here because something leaked
Rotate it now. Read the rest later.
Anything Leaksweep finds should be treated as already compromised. Revoke or rotate it at the issuer first. Deleting the line, rewriting history, or making the repo private does not make a leaked value safe. Neither does a masked report from us.
01 · scope
Your code, or public code reviewed for defense.
Leaksweep scans code you own or control, and code that is already public when your purpose is defensive: auditing a dependency, checking your own open source project, reviewing a fork of your work. Every sweep requires you to confirm this. Repo URL sweeps only fetch public repositories from GitHub and GitLab. Private code enters only when you upload it yourself.
02 · masking
A found secret is never shown in full.
ghp_••••••••••••0eIo
First four and last four characters. Values under twelve characters keep two and two, and under eight keep nothing, because first-four plus last-four of a short password is the password. This applies to the console, reports, exports, emails, logs, and model prompts. There is no reveal button and no admin view that bypasses it.
03 · storage
Raw secrets are never stored.
A saved finding is a masked value, a keyed HMAC fingerprint that cannot be reversed, and a file and line. Source code is processed in memory and dropped when the request ends.
04 · no validation
We never try the key.
Leaksweep does not call a provider with a found credential to see if it is live. That is what an attacker does. Risk is judged from context, and you confirm by rotating.
05 · no exploitation
Impact, never technique.
Findings describe what access a third party would gain so you can prioritize. They do not include steps for using a credential, and the model is instructed to refuse them.
06 · what we refuse
- ×Sweeping third-party code you do not control in order to find credentials to use. This is the line between a scanner and a harvesting tool, and it is in our Terms.
- ×Bulk sweeps of other people's repositories. Rate limits, size caps, and the absence of any search-the-internet feature are deliberate.
- ×Requests to reveal, reconstruct, or validate a masked secret. The data to do so does not exist on our side.
- ×Accounts that show this pattern are closed. If you found someone else's leaked key by accident, tell them, and do not use it.
07 · your code
- Private to your account.
- Encrypted in transit and at rest.
- Never used to train models.
- Purged on delete. A real delete, with no recovery window.
report
Found a problem with Leaksweep itself?
Write to security@leaksweep.net. We acknowledge within one business day and we do not pursue good-faith researchers. If you see Leaksweep being used against code its user does not control, tell us at the same address. Details of how the service is secured are on the security page.
$ leaksweep init
Sweep what is yours.
Three sweeps a month, free. Masked from the first byte.