@readystack/red-doc-en18031-lint@1.0.4
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.
Checks an EU declaration of conformity for radio equipment against Delegated Regulation (EU) 2022/30 and the EN 18031:2024 citations
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package’s core behavior matches its linter purpose, and the flagged license-key traffic goes to Polar or the vendor’s rule service for the package’s own licensing and rules. However, interactive use sends undisclosed runtime telemetry by default, so this merits a warning under the telemetry rule.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs a free scan in an interactive terminal, or reaches a missing/invalid-license path in an interactive terminal or MCP session.
Impact
The vendor learns that the tool was used or that a license check failed. The inspected event payloads do not include project or credential data; the telemetry is not disclosed in the README.
Mechanism
The CLI sends a small event to getreadystack.com containing the tool slug, source, and reason. DO_NOT_TRACK=1, READYSTACK_NO_TELEMETRY, and CI suppress these events.
AI rationale
The package’s core behavior matches its linter purpose, and the flagged license-key traffic goes to Polar or the vendor’s rule service for the package’s own licensing and rules. However, interactive use sends undisclosed runtime telemetry by default, so this merits a warning under the telemetry rule.
Evidence
cli.jslicense.jsREADME.md~/.config/readystack/red-doc-en18031-lint.json (or READYSTACK_HOME/red-doc-en18031-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 91.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- An interactive free CLI run automatically sends a usage event to getreadystack.com after scanning.
- The usage event contains only the tool slug, CLI source, and a fixed reason; it skips sending when telemetry opt-out variables or CI are set.
- Missing or invalid license checks can also send a paywall event with the tool slug, source, and reason.
- The license key is sent to api.polar.sh for validation, and a saved key is sent to getreadystack.com to retrieve this tool's rules.
Evidence against
- The package is a CLI linter whose manifest points to cli.js, consistent with its stated purpose.
- Telemetry is limited to tool-use and paywall metadata; inspected payloads do not include hostnames, usernames, paths, file contents, or credentials.
- The usage telemetry has opt-out checks and is limited to interactive terminal or MCP use.
- The README describes free linting and paid folder sweeps, while the inspected source contains no install lifecycle scripts.
Behavioral surface
EnvironmentVarsFilesystemNetwork
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/red-doc-en18031-lint@1.0.4.
See all versions of @readystack/red-doc-en18031-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/red-doc-en18031-lint@1.0.4 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.