@readystack/cran-policy-submission-lint
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
This report shows the evidence for @readystack/cran-policy-submission-lint@1.0.8. 0 of 7 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package performs undisclosed runtime telemetry during interactive use, which is a warning-level telemetry finding under the review rules. The observed event payloads contain no credentials or scanned file contents.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A free CLI scan in an interactive terminal, or a licensing check from a terminal or MCP session.
Impact
The vendor learns that the package was used or that a licensing check encountered a paywall condition; no credentials or scanned file contents are included in these event payloads.
Mechanism
HTTPS POST events report the product slug, source, and event reason to the vendor's /api/ev endpoint.
AI rationale
The package performs undisclosed runtime telemetry during interactive use, which is a warning-level telemetry finding under the review rules. The observed event payloads contain no credentials or scanned file contents.
Evidence
cli.jslicense.js
Network endpoints1
getreadystack.com/api/ev
Decision evidence
public snapshotAI called this Suspicious at 96.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run calls the usage ping after scanning files.
- The ping sends the product slug, source, and a fixed reason to getreadystack.com; it can be disabled with documented environment-variable checks in code.
- When licensing is needed, the package sends a paywall event containing the slug, source, and reason to getreadystack.com/api/ev.
- The README describes the linting and licensing features but does not disclose runtime telemetry.
Evidence against
- The telemetry payloads contain product and event labels, not credentials or file contents.
- Telemetry is limited to terminal or MCP sessions and has opt-out environment variables.
- License validation sends the package's own license key to the vendor's licensing service, consistent with the stated licensing feature.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
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...
...
L33: 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...
...
L33
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.8.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/cran-policy-submission-lint@1.0.8 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.