
Log Pii Telemetry Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.1Updated Oct 24, 2026
22 rules that name the lines where a Node or TypeScript service writes personal data into logs, cras
Overview
Lints Node or TypeScript services for log and telemetry lines that write personal data, flagging the offending lines.
- What you can do
- A local stdio MCP server distributed as the npm package @readystack/log-pii-telemetry-lint and run with npx. It applies 22 rules that name the lines where a Node or TypeScript service writes personal data into logs, crash reports or telemetry. The registry description is the only substantive description available; the README covers unrelated VS Code themes and lists no tools.
- When to use it
- Worth adding when an assistant is reviewing or hardening a Node or TypeScript codebase and you want PII-in-logging findings tied to specific lines. It is a narrow, single-purpose lint helper rather than a general code or security tool.
- Requirements
- Runs as a local process on the user's machine via npx, so Node.js and npm are needed. No authentication, environment variables or headers are declared. Desktop only; no web executable.
Installation
In SourceWeft
- Open Log Pii Telemetry Lint in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
