@readystack/coppa-notice-lint-2026@1.0.6
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.
18 clauses of the amended COPPA Rule, checked against the notice in your repo
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe source sends undisclosed runtime telemetry to the package vendor after ordinary free scans and license checks. The events are limited to package and event metadata, so this warrants a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
After a free CLI scan, or when a CLI or MCP request checks a missing or rejected license.
Impact
The vendor can count free use and license failures. No credential or user content collection was identified; the concern is undisclosed runtime telemetry.
Mechanism
The package posts the event type, package slug, source, and reason to getreadystack.com/api/ev. CLI usage telemetry is gated to interactive runs and can be disabled with environment flags; MCP paywall telemetry can run without a TTY.
AI rationale
The source sends undisclosed runtime telemetry to the package vendor after ordinary free scans and license checks. The events are limited to package and event metadata, so this warrants a warning rather than a block.
Evidence
cli.jslicense.js
Network endpoints1
getreadystack.com
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- After free scans, the CLI sends a usage event to getreadystack.com containing the package slug, CLI source, and a fixed reason.
- When a license key is missing, the licensing code sends a paywall event to getreadystack.com with the slug, CLI or MCP source, and reason.
- The telemetry is gated by opt-out and CI checks; the CLI usage event also requires a TTY, while MCP paywall events bypass that TTY check.
Evidence against
- The observed telemetry fields do not include credentials, file contents, paths, hostnames, or usernames.
- The event endpoint is the package vendor’s own domain, and the README describes the tool’s free and licensed features without mentioning telemetry.
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
3 Critical2 High3 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
CriticalPrevious Version Dangerous Deltacli.js
HighSandbox Evasion Gated Capabilitylicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @readystack/coppa-notice-lint-2026@1.0.6.
See all versions of @readystack/coppa-notice-lint-2026 for other recorded verdicts.
- Review the evidence and your use of @readystack/coppa-notice-lint-2026@1.0.6 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.