@readystack/cran-policy-submission-lint@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.
Catch the CRAN Repository Policy violations before the volunteer team does
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI automatically sends a small usage event to getreadystack.com after free runs, and the README does not disclose it. Its payload contains no sensitive user or project data, so this is suspicious runtime telemetry rather than malicious exfiltration.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A free CLI run in an interactive terminal, unless telemetry is disabled.
Impact
The vendor can count interactive free usage; no user or project data is included in the event.
Mechanism
The CLI posts a minimal usage event to getreadystack.com; it contains the event type, package slug, source and reason.
AI rationale
The CLI automatically sends a small usage event to getreadystack.com after free runs, and the README does not disclose it. Its payload contains no sensitive user or project data, so this is suspicious runtime telemetry rather than malicious exfiltration.
Evidence
cli.jsREADME.md~/.config/readystack/cran-policy-submission-lint.json
Network endpoints3
getreadystack.com/api/evapi.polar.sh/v1/customer-portal/license-keys/validategetreadystack.com/api/rules/
Decision evidence
public snapshotAI called this Suspicious at 95.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run sends a usage event containing only the event type, package slug, CLI source and reason to getreadystack.com.
- The CLI calls this telemetry after free runs; it is gated to interactive terminals and can be disabled with documented-in-source environment flags.
- The README describes MCP and CI usage but does not disclose runtime telemetry.
Evidence against
- The usage event contains no credentials, project paths, file contents or environment values.
- Telemetry code includes opt-outs for DO_NOT_TRACK=1, READYSTACK_NO_TELEMETRY and CI.
- License validation sends the ReadyStack license key to Polar, and the rules feed sends it to the package vendor’s own service.
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/cran-policy-submission-lint@1.0.7.
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.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.