For projects built with Claude Code, Cursor and Lovable
Find what leaks before you deploy.
Most scanners probe your live site from the outside. LeakWarden reads your code, your git history and your database schema, so it can see an open table or a committed key that a URL scan never will.
What it checks
The mistakes AI coding tools repeat, because the code runs fine and nothing warns you.
Secrets, in files and in history
API keys, tokens, passwords and database URLs, including ones you deleted but never rotated. Public keys such as the Supabase anon key and Stripe publishable keys are left alone.
Supabase row level security
Tables with RLS off, policies that say true, views that bypass RLS, and API routes that use the service role without checking who is calling.
Webhooks and payments
Handlers without signature verification, prices supplied by the client, and paywalls enforced only in the browser.
Keys in the browser
Secret-looking variables with a public prefix, and the service role used in client files.
Framework settings
Django DEBUG left on, ALLOWED_HOSTS set to any host, open CORS, and secrets that fall back to a hard-coded value.
Files that should not be in git
Committed .env files and SQLite databases, plus eval, raw HTML injection and SQL built from strings.
Free and Pro
The free version finds leaked keys, including the ones still sitting in your git history. Pro adds the checks for mistakes that are specific to AI-built apps.
| Free | Pro | |
|---|---|---|
| API keys, tokens, passwords and database URLs in your files | ✓ | ✓ |
| Keys you deleted but are still in git history | ✓ | ✓ |
| Committed or unignored .env files | ✓ | ✓ |
| Supabase row level security in your migrations | – | ✓ |
| Webhooks with no signature check, prices from the client, browser paywalls | – | ✓ |
| Secret keys exposed to the browser | – | ✓ |
| CORS, Django settings, committed databases, risky code | – | ✓ |
| Claude Code skill that reads the report and helps you fix it | – | ✓ |
| GitHub Actions workflow for every pull request | – | ✓ |
Free version: MIT license · source on GitHub · or pipx install leakwarden · run it with python3 leakwarden.py . · SHA-256 d119b0af7ce55c04a65d8c2cd1608d2fcc1985e09f9de6db68c838919ef55d75
How it works
- Download the free leakwarden.py, or buy Pro for every check plus the Claude Code skill.
- Run python3 leakwarden.py in your project. It reads your files and your git history.
- Get a report in text, JSON or Markdown, with a fix suggestion for each finding.
- With Pro, add the included GitHub Actions workflow to check every pull request.
Built to be trusted
- Your code never leaves your machine. Python standard library only.
- Secrets are redacted in every report.
- It reports what it did not assess, so a quiet result is not mistaken for a safe one.
- Safe to point at an untrusted repo: it does not run the project's code or git hooks.
Honest limits
LeakWarden is a heuristic scanner. A clean report does not prove a project is secure. It does not test the running app and does not check dependencies for known CVEs. Expect some false positives; suppress them with a .leakwardenignore file.
Get LeakWarden Pro
$29 one-time · use it on all your own projects · download right after payment
Buy now