PII-in-Logs Lint (console.log(req.body))
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.
22 rules that name the lines where a Node or TypeScript service writes personal data into logs, crash reports and analytics — with the article it touches and the one-line fix.
Install
log-pii-telemetry-lint file
Node 18+. The same 22 rules as the VS Code extension, from a terminal or CI.
Free
- Names every line in the file you have open that writes personal data into a log, a crash report or an analytics call, with the rule, the article it touches and the one-line fix — enough to clean that file and stop.
--ruleslists every rule
With a licence ($29 once)
- Runs the same 22 rules across every .js/.ts file in the workspace and writes the findings out as a report file you keep for CI, the ticket or the auditor.
log-pii-telemetry-lint --dir ./templates --report html --out report.html
GitHub Advanced Security lists at $49 per active committer per month ($30 Code Security + $19 Secret Protection) and looks for secrets, not for a customer's name travelling in a log line.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "log-pii-telemetry-lint": { "command": "log-pii-telemetry-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: PII-in-Logs Lint (console.log(req.body))
run: pip install rulestamp-log-pii-telemetry-lint && log-pii-telemetry-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-log-pii-telemetry-lint
log-pii-telemetry-lint --help
Metadata
Release files for rulestamp-log-pii-telemetry-lint 1.0.8
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_log_pii_telemetry_lint-1.0.8.tar.gz | 16.6 kB | Without provenance | Details for rulestamp_log_pii_telemetry_lint-1.0.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_log_pii_telemetry_lint-1.0.8-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_log_pii_telemetry_lint-1.0.8-py3-none-any.whl |
Total release size: 35.3 kB
Release files / rulestamp_log_pii_telemetry_lint-1.0.8.tar.gz
| Download URL | rulestamp_log_pii_telemetry_lint-1.0.8.tar.gz |
|---|---|
| Size | 16.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bef90860913802224da5d26f7345909b6f1afdd1a26f9329cbfe05bd388c0527
|
|
BLAKE2b-256 checksum How to use checksums |
7be0867c353c3b0108359ca19c682612583964dc7b295fa74dcac28c72b9baea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_log_pii_telemetry_lint-1.0.8-py3-none-any.whl
| Download URL | rulestamp_log_pii_telemetry_lint-1.0.8-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f39e6e2385c33ea6f1255d14c53952ba549eaa8d360d601de6508d2ae91e490
|
|
BLAKE2b-256 checksum How to use checksums |
da60817c43892d1d3e665ae96614883c6ce1d5323b12bf1c3e271c5ab6896bff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-log-pii-telemetry-lint 1.0.8
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.