This part is free in Lite. Pro adds the rest.
Keys stay outof your code.
Adams catches a pasted key before it is committed, and shows where it was so you can move it.
Lite
// the problem
What goes wrong
A key pasted once is public foreverPasting a key into a file to test something is easy. Once it is committed and pushed, it is in the history, and anyone who can read the repo can use it.
AI tools paste keys tooAn AI that is asked to wire up a service can write the key straight into the code it generates. Nobody typed it, so nobody remembers it.
// what adams does
What Adams does
Blocks the commitWhen a key or token looks present in what you are about to commit, the commit stops with the file and the line.
Names the kind, never the valueThe message says what kind of secret and where. It never prints the secret itself.
Points to the fixThe key moves to an env file that git ignores, and the code reads it from the environment.
// worked example
An example
A commit with a key in it
Illustrative output. The first run is stopped, the second passes after the fix.
~/project~/your-project · example
$
git commit -m "add payment config"adams: blocked
A payment key in config.ts:12
Moved to .env, which git ignores
$
git commit -m "add payment config"✓ Committed, no secrets found
// faq
Questions
Is this free?
Yes. The secret, git and leak guards are in Lite, which is free with no trial and no expiry.
Does it send my code anywhere?
No. The checks run on your machine inside your session.
What if a key already leaked?
Replace it at the provider first. Removing it from the code does not remove it from history. The leaked key guide walks through the order.
Can it miss a secret?
Yes, no scanner finds everything. Treat it as a net under good habits, not a replacement for them.
// related