@readystack/red-doc-en18031-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.
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 CLI sends undisclosed runtime usage telemetry to the publisher’s service by default during interactive free runs. The event is minimal and can be disabled, so this warrants a warning rather than a publish block.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs the CLI interactively; a missing or invalid license can also trigger a paywall event during CLI or MCP use.
Impact
The publisher learns that the package was used or encountered a paywall. The inspected telemetry does not include credentials or project data.
Mechanism
The package posts small events containing the package slug, event type, invocation source and reason to getreadystack.com/api/ev. CLI usage telemetry has environment-variable opt-outs.
AI rationale
The CLI sends undisclosed runtime usage telemetry to the publisher’s service by default during interactive free runs. The event is minimal and can be disabled, so this warrants a warning rather than a publish block.
Evidence
cli.jslicense.jsREADME.md~/.config/readystack/red-doc-en18031-lint.json, or the path selected by READYSTACK_HOME
Network endpoints4
getreadystack.com/api/evgetreadystack.com/api/licgetreadystack.com/api/rules/<slug>api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 96.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package exposes cli.js as its command entry point.
- A normal free CLI run calls pingUse, which sends a usage event to getreadystack.com.
- That event contains only the event type, package slug, CLI source and free-use reason; telemetry can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY.
- The README describes the tool and its license but does not disclose runtime telemetry.
Evidence against
- The reported telemetry payload contains no credentials, file contents, paths, usernames or host details.
- The CLI telemetry is limited to interactive terminal use and has opt-out environment variables.
- License validation sends a license key to the package’s own licensing service, consistent with the package’s licensing function.
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...
...
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/red-doc-en18031-lint@1.0.7.
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.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.