leakwarden 0.2.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Leon Krasnik
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
@@ -0,0 +1,120 @@
1
+ Metadata-Version: 2.4
2
+ Name: leakwarden
3
+ Version: 0.2.0
4
+ Summary: Find leaked API keys, tokens and passwords in your code and git history before you deploy
5
+ Author: Leon Krasnik
6
+ License-Expression: MIT
7
+ Project-URL: Homepage, https://leakwarden.dev
8
+ Project-URL: Source, https://github.com/CrazyJinji/leakwarden
9
+ Keywords: security,secrets,scanner,git,supabase,ai
10
+ Classifier: Programming Language :: Python :: 3
11
+ Classifier: Environment :: Console
12
+ Classifier: Topic :: Security
13
+ Requires-Python: >=3.8
14
+ Description-Content-Type: text/markdown
15
+ License-File: LICENSE
16
+ Dynamic: license-file
17
+
18
+ # LeakWarden
19
+
20
+ Find leaked API keys, tokens and passwords in your code and in your git history before you deploy. One Python file, standard library only, runs on your machine.
21
+
22
+ It is built for projects made with Claude Code, Cursor and Lovable, where a key often lands in a commit before anyone notices. Deleting the key from the file does not help if it is still in an old commit, so LeakWarden reads the history too.
23
+
24
+ This is the free edition, MIT licensed. [LeakWarden Pro](https://leakwarden.dev) adds checks for mistakes that are specific to AI-built apps (see the end of this page).
25
+
26
+ ## Run it
27
+
28
+ ```
29
+ curl -O https://leakwarden.dev/download/leakwarden.py
30
+ python3 leakwarden.py /path/to/your/project
31
+ ```
32
+
33
+ You need Python 3.8 or newer. The history scan needs `git`. The SHA-256 of the current file is on [leakwarden.dev](https://leakwarden.dev#free) if you want to check the download.
34
+
35
+ ## What it finds
36
+
37
+ - API keys and tokens: OpenAI, Anthropic, OpenRouter, Stripe, GitHub, Slack, SendGrid, AWS, Google, Polar, Supabase secret and `service_role` keys, private key blocks.
38
+ - Hard-coded passwords and secret-looking values, and database URLs with a password in them.
39
+ - Keys that were committed and later deleted. It reads the added lines of the last 500 commits by default.
40
+ - `.env` files that are tracked by git, or present and not covered by `.gitignore`. A committed `.env` that only holds browser-public values (`VITE_SUPABASE_URL`, `..._ANON_KEY`) is reported as low.
41
+
42
+ Keys that are public by design, such as the Supabase anon key and Stripe publishable keys, are not reported.
43
+
44
+ ## Example
45
+
46
+ ```
47
+ leakwarden 0.2.0 (free edition) ./my-app
48
+
49
+ Coverage
50
+ - secrets (working tree): checked 12 text files
51
+ - secrets (git history): checked 2 commit(s) (limit 500), added lines only
52
+ ...
53
+
54
+ Findings: 4 high, 1 medium, 0 low, 0 info
55
+
56
+ [HIGH] Stripe live secret key (secret.stripe_live)
57
+ .env:1
58
+ > STRIPE_SECRET_KEY=[REDACTED:redacted]
59
+ Fix: Rotate this credential now, then load it from an environment variable or a secret manager.
60
+
61
+ [HIGH] GitHub token (in git history) (secret.github) [history 4b9b722b]
62
+ config.js:1
63
+ > export const githubToken = '[REDACTED:redacted]'
64
+ Fix: Rotate this credential now. Rewriting history (git filter-repo) only helps after the key is rotated.
65
+
66
+ ...
67
+ ```
68
+
69
+ The report also lists the areas it did not check, so a quiet report is not mistaken for a safe one.
70
+
71
+ ## Options
72
+
73
+ ```
74
+ --format text|json|markdown report format (default: text)
75
+ --output FILE write the report to a file
76
+ --min-severity LEVEL hide findings below info, low, medium or high (default: low)
77
+ --fail-on LEVEL exit with status 1 at or above this level, or never (default: high)
78
+ --no-history skip the git history scan
79
+ --max-commits N how many commits to read (default: 500)
80
+ --history-range BASE..HEAD read only these commits, for example in CI on a pull request
81
+ ```
82
+
83
+ Exit status is 0 when nothing reaches `--fail-on`, 1 when something does, and 2 on a usage error.
84
+
85
+ ## Ignoring a finding
86
+
87
+ Put `leakwarden:ignore` anywhere on a line to skip it, in the working tree and in history.
88
+
89
+ Or add a `.leakwardenignore` file at the project root. One entry per line: a path glob, a rule filter, or both.
90
+
91
+ ```
92
+ examples/*
93
+ rule:secret.stripe_test
94
+ rule:secret.generic src/fixtures/*
95
+ ```
96
+
97
+ ## What it does not do
98
+
99
+ - It never prints a secret value. Every report format redacts them.
100
+ - It does not run the project's code, and it runs `git` with hooks and fsmonitor turned off, so it is safe to point at a repository you do not trust.
101
+ - It makes no network requests.
102
+
103
+ It is a heuristic scanner. A clean report does not prove a project is secure, and it will miss secrets in formats it has no rule for. It does not check dependencies for known vulnerabilities.
104
+
105
+ ## LeakWarden Pro
106
+
107
+ Pro adds the checks that matter for apps built with AI coding tools:
108
+
109
+ - Supabase row level security in your migrations: tables without RLS, policies that allow everything, views that bypass RLS
110
+ - Webhook handlers with no signature check, prices taken from the client, paywalls decided in the browser
111
+ - Secret keys exposed to the browser through `NEXT_PUBLIC_` or `VITE_` variables, and the service role key in client code
112
+ - CORS, Django settings, committed databases and risky code (`eval`, raw HTML, SQL built from strings)
113
+ - A Claude Code skill that reads the report and helps you fix each finding
114
+ - A GitHub Actions workflow that checks every pull request and annotates the lines
115
+
116
+ $29 one-time at [leakwarden.dev](https://leakwarden.dev).
117
+
118
+ ## License
119
+
120
+ MIT, see [LICENSE](LICENSE).
@@ -0,0 +1,103 @@
1
+ # LeakWarden
2
+
3
+ Find leaked API keys, tokens and passwords in your code and in your git history before you deploy. One Python file, standard library only, runs on your machine.
4
+
5
+ It is built for projects made with Claude Code, Cursor and Lovable, where a key often lands in a commit before anyone notices. Deleting the key from the file does not help if it is still in an old commit, so LeakWarden reads the history too.
6
+
7
+ This is the free edition, MIT licensed. [LeakWarden Pro](https://leakwarden.dev) adds checks for mistakes that are specific to AI-built apps (see the end of this page).
8
+
9
+ ## Run it
10
+
11
+ ```
12
+ curl -O https://leakwarden.dev/download/leakwarden.py
13
+ python3 leakwarden.py /path/to/your/project
14
+ ```
15
+
16
+ You need Python 3.8 or newer. The history scan needs `git`. The SHA-256 of the current file is on [leakwarden.dev](https://leakwarden.dev#free) if you want to check the download.
17
+
18
+ ## What it finds
19
+
20
+ - API keys and tokens: OpenAI, Anthropic, OpenRouter, Stripe, GitHub, Slack, SendGrid, AWS, Google, Polar, Supabase secret and `service_role` keys, private key blocks.
21
+ - Hard-coded passwords and secret-looking values, and database URLs with a password in them.
22
+ - Keys that were committed and later deleted. It reads the added lines of the last 500 commits by default.
23
+ - `.env` files that are tracked by git, or present and not covered by `.gitignore`. A committed `.env` that only holds browser-public values (`VITE_SUPABASE_URL`, `..._ANON_KEY`) is reported as low.
24
+
25
+ Keys that are public by design, such as the Supabase anon key and Stripe publishable keys, are not reported.
26
+
27
+ ## Example
28
+
29
+ ```
30
+ leakwarden 0.2.0 (free edition) ./my-app
31
+
32
+ Coverage
33
+ - secrets (working tree): checked 12 text files
34
+ - secrets (git history): checked 2 commit(s) (limit 500), added lines only
35
+ ...
36
+
37
+ Findings: 4 high, 1 medium, 0 low, 0 info
38
+
39
+ [HIGH] Stripe live secret key (secret.stripe_live)
40
+ .env:1
41
+ > STRIPE_SECRET_KEY=[REDACTED:redacted]
42
+ Fix: Rotate this credential now, then load it from an environment variable or a secret manager.
43
+
44
+ [HIGH] GitHub token (in git history) (secret.github) [history 4b9b722b]
45
+ config.js:1
46
+ > export const githubToken = '[REDACTED:redacted]'
47
+ Fix: Rotate this credential now. Rewriting history (git filter-repo) only helps after the key is rotated.
48
+
49
+ ...
50
+ ```
51
+
52
+ The report also lists the areas it did not check, so a quiet report is not mistaken for a safe one.
53
+
54
+ ## Options
55
+
56
+ ```
57
+ --format text|json|markdown report format (default: text)
58
+ --output FILE write the report to a file
59
+ --min-severity LEVEL hide findings below info, low, medium or high (default: low)
60
+ --fail-on LEVEL exit with status 1 at or above this level, or never (default: high)
61
+ --no-history skip the git history scan
62
+ --max-commits N how many commits to read (default: 500)
63
+ --history-range BASE..HEAD read only these commits, for example in CI on a pull request
64
+ ```
65
+
66
+ Exit status is 0 when nothing reaches `--fail-on`, 1 when something does, and 2 on a usage error.
67
+
68
+ ## Ignoring a finding
69
+
70
+ Put `leakwarden:ignore` anywhere on a line to skip it, in the working tree and in history.
71
+
72
+ Or add a `.leakwardenignore` file at the project root. One entry per line: a path glob, a rule filter, or both.
73
+
74
+ ```
75
+ examples/*
76
+ rule:secret.stripe_test
77
+ rule:secret.generic src/fixtures/*
78
+ ```
79
+
80
+ ## What it does not do
81
+
82
+ - It never prints a secret value. Every report format redacts them.
83
+ - It does not run the project's code, and it runs `git` with hooks and fsmonitor turned off, so it is safe to point at a repository you do not trust.
84
+ - It makes no network requests.
85
+
86
+ It is a heuristic scanner. A clean report does not prove a project is secure, and it will miss secrets in formats it has no rule for. It does not check dependencies for known vulnerabilities.
87
+
88
+ ## LeakWarden Pro
89
+
90
+ Pro adds the checks that matter for apps built with AI coding tools:
91
+
92
+ - Supabase row level security in your migrations: tables without RLS, policies that allow everything, views that bypass RLS
93
+ - Webhook handlers with no signature check, prices taken from the client, paywalls decided in the browser
94
+ - Secret keys exposed to the browser through `NEXT_PUBLIC_` or `VITE_` variables, and the service role key in client code
95
+ - CORS, Django settings, committed databases and risky code (`eval`, raw HTML, SQL built from strings)
96
+ - A Claude Code skill that reads the report and helps you fix each finding
97
+ - A GitHub Actions workflow that checks every pull request and annotates the lines
98
+
99
+ $29 one-time at [leakwarden.dev](https://leakwarden.dev).
100
+
101
+ ## License
102
+
103
+ MIT, see [LICENSE](LICENSE).
@@ -0,0 +1,120 @@
1
+ Metadata-Version: 2.4
2
+ Name: leakwarden
3
+ Version: 0.2.0
4
+ Summary: Find leaked API keys, tokens and passwords in your code and git history before you deploy
5
+ Author: Leon Krasnik
6
+ License-Expression: MIT
7
+ Project-URL: Homepage, https://leakwarden.dev
8
+ Project-URL: Source, https://github.com/CrazyJinji/leakwarden
9
+ Keywords: security,secrets,scanner,git,supabase,ai
10
+ Classifier: Programming Language :: Python :: 3
11
+ Classifier: Environment :: Console
12
+ Classifier: Topic :: Security
13
+ Requires-Python: >=3.8
14
+ Description-Content-Type: text/markdown
15
+ License-File: LICENSE
16
+ Dynamic: license-file
17
+
18
+ # LeakWarden
19
+
20
+ Find leaked API keys, tokens and passwords in your code and in your git history before you deploy. One Python file, standard library only, runs on your machine.
21
+
22
+ It is built for projects made with Claude Code, Cursor and Lovable, where a key often lands in a commit before anyone notices. Deleting the key from the file does not help if it is still in an old commit, so LeakWarden reads the history too.
23
+
24
+ This is the free edition, MIT licensed. [LeakWarden Pro](https://leakwarden.dev) adds checks for mistakes that are specific to AI-built apps (see the end of this page).
25
+
26
+ ## Run it
27
+
28
+ ```
29
+ curl -O https://leakwarden.dev/download/leakwarden.py
30
+ python3 leakwarden.py /path/to/your/project
31
+ ```
32
+
33
+ You need Python 3.8 or newer. The history scan needs `git`. The SHA-256 of the current file is on [leakwarden.dev](https://leakwarden.dev#free) if you want to check the download.
34
+
35
+ ## What it finds
36
+
37
+ - API keys and tokens: OpenAI, Anthropic, OpenRouter, Stripe, GitHub, Slack, SendGrid, AWS, Google, Polar, Supabase secret and `service_role` keys, private key blocks.
38
+ - Hard-coded passwords and secret-looking values, and database URLs with a password in them.
39
+ - Keys that were committed and later deleted. It reads the added lines of the last 500 commits by default.
40
+ - `.env` files that are tracked by git, or present and not covered by `.gitignore`. A committed `.env` that only holds browser-public values (`VITE_SUPABASE_URL`, `..._ANON_KEY`) is reported as low.
41
+
42
+ Keys that are public by design, such as the Supabase anon key and Stripe publishable keys, are not reported.
43
+
44
+ ## Example
45
+
46
+ ```
47
+ leakwarden 0.2.0 (free edition) ./my-app
48
+
49
+ Coverage
50
+ - secrets (working tree): checked 12 text files
51
+ - secrets (git history): checked 2 commit(s) (limit 500), added lines only
52
+ ...
53
+
54
+ Findings: 4 high, 1 medium, 0 low, 0 info
55
+
56
+ [HIGH] Stripe live secret key (secret.stripe_live)
57
+ .env:1
58
+ > STRIPE_SECRET_KEY=[REDACTED:redacted]
59
+ Fix: Rotate this credential now, then load it from an environment variable or a secret manager.
60
+
61
+ [HIGH] GitHub token (in git history) (secret.github) [history 4b9b722b]
62
+ config.js:1
63
+ > export const githubToken = '[REDACTED:redacted]'
64
+ Fix: Rotate this credential now. Rewriting history (git filter-repo) only helps after the key is rotated.
65
+
66
+ ...
67
+ ```
68
+
69
+ The report also lists the areas it did not check, so a quiet report is not mistaken for a safe one.
70
+
71
+ ## Options
72
+
73
+ ```
74
+ --format text|json|markdown report format (default: text)
75
+ --output FILE write the report to a file
76
+ --min-severity LEVEL hide findings below info, low, medium or high (default: low)
77
+ --fail-on LEVEL exit with status 1 at or above this level, or never (default: high)
78
+ --no-history skip the git history scan
79
+ --max-commits N how many commits to read (default: 500)
80
+ --history-range BASE..HEAD read only these commits, for example in CI on a pull request
81
+ ```
82
+
83
+ Exit status is 0 when nothing reaches `--fail-on`, 1 when something does, and 2 on a usage error.
84
+
85
+ ## Ignoring a finding
86
+
87
+ Put `leakwarden:ignore` anywhere on a line to skip it, in the working tree and in history.
88
+
89
+ Or add a `.leakwardenignore` file at the project root. One entry per line: a path glob, a rule filter, or both.
90
+
91
+ ```
92
+ examples/*
93
+ rule:secret.stripe_test
94
+ rule:secret.generic src/fixtures/*
95
+ ```
96
+
97
+ ## What it does not do
98
+
99
+ - It never prints a secret value. Every report format redacts them.
100
+ - It does not run the project's code, and it runs `git` with hooks and fsmonitor turned off, so it is safe to point at a repository you do not trust.
101
+ - It makes no network requests.
102
+
103
+ It is a heuristic scanner. A clean report does not prove a project is secure, and it will miss secrets in formats it has no rule for. It does not check dependencies for known vulnerabilities.
104
+
105
+ ## LeakWarden Pro
106
+
107
+ Pro adds the checks that matter for apps built with AI coding tools:
108
+
109
+ - Supabase row level security in your migrations: tables without RLS, policies that allow everything, views that bypass RLS
110
+ - Webhook handlers with no signature check, prices taken from the client, paywalls decided in the browser
111
+ - Secret keys exposed to the browser through `NEXT_PUBLIC_` or `VITE_` variables, and the service role key in client code
112
+ - CORS, Django settings, committed databases and risky code (`eval`, raw HTML, SQL built from strings)
113
+ - A Claude Code skill that reads the report and helps you fix each finding
114
+ - A GitHub Actions workflow that checks every pull request and annotates the lines
115
+
116
+ $29 one-time at [leakwarden.dev](https://leakwarden.dev).
117
+
118
+ ## License
119
+
120
+ MIT, see [LICENSE](LICENSE).
@@ -0,0 +1,10 @@
1
+ LICENSE
2
+ README.md
3
+ leakwarden.py
4
+ pyproject.toml
5
+ leakwarden.egg-info/PKG-INFO
6
+ leakwarden.egg-info/SOURCES.txt
7
+ leakwarden.egg-info/dependency_links.txt
8
+ leakwarden.egg-info/entry_points.txt
9
+ leakwarden.egg-info/top_level.txt
10
+ tests/test_free.py
@@ -0,0 +1,2 @@
1
+ [console_scripts]
2
+ leakwarden = leakwarden:main
@@ -0,0 +1 @@
1
+ leakwarden