@readystack/cran-policy-submission-lint@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.
Catch the CRAN Repository Policy violations before the volunteer team does
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source shows limited runtime telemetry to the vendor on failed license checks, with an opt-out but no README disclosure. It does not show credential or project-data exfiltration, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- On a paywall check, the package sends a runtime event containing the package slug, CLI or MCP source, and reason to getreadystack.com/api/ev.
- The paywall event is sent unless opt-out variables are set; it is limited to TTY or MCP sessions.
- The README documents license requirements but does not mention this telemetry.
- The telemetry payload contains only the event type, package slug, source, and reason; it does not include credentials or project data.
- The separate license-feed request sends the package’s own license key to getreadystack.com to retrieve rules.
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.6.
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.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.