@readystack/view-in-browser-leak-audit@1.0.1
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 and paywall telemetry to the publisher without documenting it in the README. The payloads are limited and have opt-outs, so this is suspicious telemetry rather than credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the CLI in a terminal; free runs report usage, while missing or invalid licences can report a paywall event.
Impact
The publisher can learn that the CLI was used and whether a licence was missing or invalid. The inspected payloads do not include credentials or scanned content.
Mechanism
The CLI posts event type, package slug, source, and reason to getreadystack.com/api/ev. Telemetry can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY and is suppressed in CI.
AI rationale
The source sends runtime usage and paywall telemetry to the publisher without documenting it in the README. The payloads are limited and have opt-outs, so this is suspicious telemetry rather than credential exfiltration.
Evidence
cli.jslicense.js
Network endpoints1
getreadystack.com/api/ev
Decision evidence
public snapshotAI called this Suspicious at 97.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run sends a usage event containing only the event type, package slug, source, and reason to getreadystack.com/api/ev.
- The usage event is sent for human terminal runs unless telemetry opt-outs or CI are detected; the README does not disclose this collection.
- When a licence is missing or invalid, the paywall event likewise contains only the package slug, source, and reason.
Evidence against
- The package’s stated purpose is to audit HTML files, and the CLI performs those scans locally.
- The inspected event payloads do not include scanned file contents, credentials, hostnames, usernames, or project paths.
- The telemetry has opt-out environment variables and is limited to terminal or MCP sessions.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 flaggedlicense.jsView file
2'use strict';
L3: const https = require('https'), fs = require('fs'), path = require('path'), os = require('os');
L4: const ORG_ID = 'a5cdf664-d8e7-4f87-8895-056717aaba17';
...
L9: const RECHECK_MS = 7 * 24 * 3600 * 1000; // re-ask Polar every 7 days (refunds / cancellations)
L10: function storePath() { return path.join(process.env.READYSTACK_HOME || path.join(os.homedir(), '.config', 'readystack'), SLUG + '.json'); }
L11: function load() { try { return JSON.parse(fs.readFileSync(storePath(), 'utf8')); } catch (e) { return {}; } }
L12: function save(o) { try { fs.mkdirSync(path.dirname(storePath()), { recursive: true }); fs.writeFileSync(storePath(), JSON.stringify(o)); } catch (e) { /* read-only home: still work...
...
L31: req.on('error', function () { resolve({ ok: false, offline:
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L22Trigger-reachable chain: manifest.bin -> cli.js -> license.js
L2: 'use strict';
L3: const https = require('https'), fs = require('fs'), path = require('path'), os = require('os');
L4: const ORG_ID = 'a5cdf664-d8e7-4f87-8895-056717aaba17';
...
L9: const RECHECK_MS = 7 * 24 * 3600 * 1000; // re-ask Polar every 7 days (refunds / cancellations)
L10: function storePath() { return path.join(process.env.READYSTACK_HOME || path.join(os.homedir(), '.config', 'readystack'), SLUG + '.json'); }
L11: function load() { try { return JSON.parse(fs.readFileSync(storePath(), 'utf8')); } catch (e) { return {}; } }
L12: function save(o) { try { fs.mkdirSync(path.dirname(storePath()), { recursive: true }); fs.writeFileSync(storePath(), JSON.stringify(o)); } catch (e) { /* read-only home: still work...
...
L31
Findings
2 Critical2 High4 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
HighSandbox Evasion Gated Capabilitylicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencecli.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @readystack/view-in-browser-leak-audit@1.0.1.
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.1 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.