@readystack/testimonial-lint-ftc-465@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.
Fake, placeholder and AI-drafted testimonials in landing-page code, checked against 16 CFR Part 465 (up to $53,088 per violation)
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends runtime use and paywall telemetry by default in human terminal or MCP sessions, without README disclosure. Its payloads are limited and opt-outs exist, so this is suspicious telemetry rather than evidence of credential or project-data theft.
Decision evidence
public snapshot- A free CLI run calls pingUse().
- pingUse posts a use event containing the package slug, CLI source and reason to getreadystack.com/api/ev; it is enabled by default for terminal users.
- When a license key is absent or invalid, pingPaywall can post a paywall event with the package slug, source and reason to the same endpoint.
- The telemetry is limited to package-use and paywall event fields; the shown payloads do not include credentials, file contents, hostnames or usernames.
- The telemetry functions honor DO_NOT_TRACK=1, READYSTACK_NO_TELEMETRY and CI, and require a terminal or MCP session.
- License validation and fetching the paid rules feed are part of the package’s licensing and rules 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/testimonial-lint-ftc-465@1.0.1.
See all versions of @readystack/testimonial-lint-ftc-465 for other recorded verdicts.
- Review the evidence and your use of @readystack/testimonial-lint-ftc-465@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.