@readystack/cran-policy-submission-lint@1.0.5
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.
Catch the CRAN Repository Policy violations before the volunteer team does
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends usage and paywall telemetry to the publisher by default during interactive use, without documenting that collection in the README. The payload is limited to package and event details, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- Interactive free CLI runs automatically send a usage event to getreadystack.com with the package slug, CLI source and a "free" reason.
- The event is limited to usage or paywall status; it does not include host, user, project, file or credential values.
- The telemetry is enabled by default in interactive sessions and has environment-variable opt-outs, but the README does not disclose it.
- Usage and paywall telemetry are limited to interactive CLI or MCP sessions and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY.
- The license key is sent to getreadystack.com for the package's rules feed, a package feature, and is not sent with the usage event.
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/cran-policy-submission-lint@1.0.5.
See all versions of @readystack/cran-policy-submission-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/cran-policy-submission-lint@1.0.5 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.