Terraform State Secret Leak Lint
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Names the attributes, outputs and backends that copy a cleartext secret into terraform.tfstate
Install
tfstate-secret-leak-lint file
Node 18+. The same 10 rules as the VS Code extension, from a terminal or CI.
Free
- Scan the Terraform file you have open and name every attribute, output and backend setting that writes a cleartext secret into terraform.tfstate. 10 rules. On the 47-line sample file it returns 8 findings: 6 errors and 2 warnings. The fixed version of the same file returns 0.
--ruleslists every rule
With a licence ($29 once)
- Scan every .tf file in the workspace in one pass and export the finding list as a dated Markdown or JSON evidence file you keep for the audit. $29 once, one licence key per person or CI seat.
tfstate-secret-leak-lint --dir ./templates --report html --out report.html
Hand review runs about $150/hour.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "tfstate-secret-leak-lint": { "command": "tfstate-secret-leak-lint", "args": ["--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: Terraform State Secret Leak Lint
run: pip install rulestamp-tfstate-secret-leak-lint && tfstate-secret-leak-lint --dir . --ci
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install rulestamp-tfstate-secret-leak-lint
tfstate-secret-leak-lint --help
Metadata
Release files for rulestamp-tfstate-secret-leak-lint 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rulestamp_tfstate_secret_leak_lint-1.0.6.tar.gz | 17.3 kB | Without provenance | Details for rulestamp_tfstate_secret_leak_lint-1.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_tfstate_secret_leak_lint-1.0.6-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_tfstate_secret_leak_lint-1.0.6-py3-none-any.whl |
Total release size: 36.9 kB
Release files / rulestamp_tfstate_secret_leak_lint-1.0.6.tar.gz
| Download URL | rulestamp_tfstate_secret_leak_lint-1.0.6.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f32410d60b218cc56b1de9af56b64b37a2650e5b24089d8f65d6971a1639a9e
|
|
BLAKE2b-256 checksum How to use checksums |
487b3ffb347fff680604867b90cb1abfb3b79ae1d7692597fec4d9f6172d6308
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_tfstate_secret_leak_lint-1.0.6-py3-none-any.whl
| Download URL | rulestamp_tfstate_secret_leak_lint-1.0.6-py3-none-any.whl |
|---|---|
| Size | 19.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ada5f03b8bfad664ee0a8aac48ba067b47a63ae9e8d01e3735945905a35ac32a
|
|
BLAKE2b-256 checksum How to use checksums |
f2d1751d60f83628006d3507ce3e91b05429d60e6d8ef3baa350c1b34f5ed98b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-tfstate-secret-leak-lint 1.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.