Connection String & Secret Audit — 8 Stacks
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.
26 rules and 32 safe-replacement snippets for hardcoded connection strings, keys and kubeconfigs across 8 VS Code stacks. Runs on your machine and sends nothing anywhere.
Install
connection-string-secret-audit file
Node 18+. The same 26 rules as the VS Code extension, from a terminal or CI.
Free
- Audits the file you have open, or only the lines you highlighted, against all 26 rules and prints every finding with its line number; inserts any of the 32 safe replacement snippets at the cursor; lists every rule and snippet that ships inside. No key, no account, nothing leaves the machine.
--ruleslists every rule
With a licence ($29 once)
- Runs that same audit across every file in the workspace instead of one, and writes the findings out as a CSV, JSON or HTML file you keep in the repo and hand to a reviewer or an auditor.
connection-string-secret-audit --dir ./templates --report html --out report.html
GitHub Secret Protection is published at $19 per active committer per month, billed every month and re-counted as committers come and go (GitHub Docs, checked 2026-09-08)
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "connection-string-secret-audit": { "command": "connection-string-secret-audit", "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: Connection String & Secret Audit — 8 Stacks
run: pip install rulestamp-connection-string-secret-audit && connection-string-secret-audit --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-connection-string-secret-audit
connection-string-secret-audit --help
Metadata
Release files for rulestamp-connection-string-secret-audit 0.1.7
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_connection_string_secret_audit-0.1.7.tar.gz | 15.6 kB | Without provenance | Details for rulestamp_connection_string_secret_audit-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_connection_string_secret_audit-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_connection_string_secret_audit-0.1.7-py3-none-any.whl |
Total release size: 33.1 kB
Release files / rulestamp_connection_string_secret_audit-0.1.7.tar.gz
| Download URL | rulestamp_connection_string_secret_audit-0.1.7.tar.gz |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d87fdb8e45976099f6bcaf3879bceea33da1af79739e1fff8d9f79e5d1d4942a
|
|
BLAKE2b-256 checksum How to use checksums |
73b6774968c0868aef331d97db86f350df804604b80d8eaa80dda0f7cf15c92b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_connection_string_secret_audit-0.1.7-py3-none-any.whl
| Download URL | rulestamp_connection_string_secret_audit-0.1.7-py3-none-any.whl |
|---|---|
| Size | 17.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
74ecadae71a08ffa270df3ed6d21c2b3da106b87f30042f56dce2c2540046e0f
|
|
BLAKE2b-256 checksum How to use checksums |
84ff19f46bda672893478e4fcbdcc1c99bfc4e4a84a663ba6668f4c44bf485b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-connection-string-secret-audit 0.1.7
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.