@readystack/view-in-browser-leak-audit@1.0.2
Not affiliated with ReadyStack (readystack.dev). No new versions are published here. These tools continue under the name Rulestamp, by the team behind getreadystack.com.
24 rules read the .html file you are about to open in the browser and flag every line that behaves differently once the page has a public URL: live API keys, localhost and file:// paths, http:// resou
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe source sends runtime usage telemetry to the publisher’s host, but does not disclose it in the README. Its payloads contain only package and event metadata, so this warrants a warning rather than a block.
Decision evidence
public snapshot- A free CLI run sends a usage event to getreadystack.com containing the package slug, CLI source and a fixed reason.
- The usage ping runs after free scans; telemetry is disabled by opt-out environment variables, but the README does not disclose it.
- License or paywall events send only the package slug, source and reason to the same host.
- The reported events do not include file contents, credentials, hostnames or other identifying details.
- The package is a CLI audit tool, and its license checks and rule feed serve its paid scanning features.
- The network pings are limited to interactive or MCP use and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @readystack/view-in-browser-leak-audit@1.0.2.
See all versions of @readystack/view-in-browser-leak-audit for other recorded verdicts.
- Review the evidence and your use of @readystack/view-in-browser-leak-audit@1.0.2 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.