@readystack/view-in-browser-leak-audit
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
This report shows the evidence for @readystack/view-in-browser-leak-audit@1.0.3. 0 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends undisclosed runtime usage and paywall telemetry to the vendor by default, though the payload contains no scanned content or credentials and has opt-out controls. This is suspicious telemetry, not evidence of credential exfiltration or malicious behavior.
Decision evidence
public snapshot- A free CLI run sends a `use` event with the product slug, CLI source and reason to `getreadystack.com/api/ev`.
- A missing or invalid license can send a `paywall` event to the same endpoint; telemetry has opt-out environment variables.
- The manifest has no lifecycle scripts; the package is a CLI for scanning HTML files.
- The telemetry payload contains usage and product fields, not scanned file contents or credentials.
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.3.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/view-in-browser-leak-audit@1.0.3 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.