@readystack/coppa-notice-lint-2026@1.0.7
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 CLI sends runtime usage telemetry to the publisher’s service, and the README does not disclose it. The event payload is limited to usage metadata and has opt-outs, so this is suspicious telemetry rather than evidence of credential exfiltration.
Decision evidence
public snapshot- A free CLI run sends a usage event containing the package slug, CLI source, and event reason to getreadystack.com/api/ev.
- A paywall event sends the package slug, CLI or MCP source, and a reason to the same endpoint.
- The events are gated on interactive use and can be suppressed with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY; CI is also excluded.
- The event payloads contain usage categories, not file contents, credentials, hostnames, or usernames.
- The package is a COPPA notice linter with a CLI entry point.
- License keys are used for this package’s licensing and rule-feed features.
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/coppa-notice-lint-2026@1.0.7.
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.7 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.