@readystack/lockfile-due-diligence-lint@1.0.0
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.
npm install scripts, integrity and sources under EU CRA Art. 13(5)
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package performs undisclosed runtime telemetry by default after interactive free scans, though the event contains only product-use fields and can be disabled. The flagged license traffic is for the package’s own licensing and rule-feed features, and no credential or project-data theft was identified.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
After a free CLI scan completes in an interactive terminal.
Impact
The vendor can track interactive free usage; no credentials, file contents, or project details are included in this event.
Mechanism
The CLI posts a small usage event containing the product slug, source, and fixed reason to getreadystack.com. Environment-variable opt-outs are available.
AI rationale
The package performs undisclosed runtime telemetry by default after interactive free scans, though the event contains only product-use fields and can be disabled. The flagged license traffic is for the package’s own licensing and rule-feed features, and no credential or project-data theft was identified.
Evidence
cli.jslicense.js~/.config/readystack/lockfile-due-diligence-lint.json
Network endpoints3
getreadystack.com/api/evgetreadystack.com/api/rules/api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run automatically calls the usage ping after scanning files.
- The ping sends only the product slug, CLI source, and a fixed “free” reason to getreadystack.com; it does not include scanned file contents.
- The ping can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY, but the README does not disclose it.
Evidence against
- No install lifecycle scripts are declared.
- Folder scans and report generation require an explicit command or MCP tool call.
- License validation and rule-feed requests send a user-provided or saved product license key to the package vendor or its license provider.
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
2 Critical2 High4 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
HighSandbox Evasion Gated Capabilitylicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencecli.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @readystack/lockfile-due-diligence-lint@1.0.0.
See all versions of @readystack/lockfile-due-diligence-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/lockfile-due-diligence-lint@1.0.0 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.