@readystack/iot-data-notice-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.
Checks a smart-device product data notice against Data Act Article 3(2)-(3) in VS Code
This report shows the evidence for @readystack/iot-data-notice-lint@1.0.2. 0 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package performs undisclosed runtime telemetry when users run free CLI checks, which warrants a warning under the review rules. The observed event contains only package-use metadata, and license-key requests go to the publisher's own service.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the CLI for a free check in an interactive terminal; a missing or invalid license can also trigger a paywall event.
Impact
The publisher can count free CLI use and paywall encounters; the observed payload does not expose credentials or project data.
Mechanism
The CLI posts package usage and context fields to the publisher's /api/ev endpoint. Environment-variable opt-outs, CI, and non-interactive execution suppress the free-use event.
AI rationale
The package performs undisclosed runtime telemetry when users run free CLI checks, which warrants a warning under the review rules. The observed event contains only package-use metadata, and license-key requests go to the publisher's own service.
Evidence
cli.jslicense.js
Network endpoints1
getreadystack.com/api/ev
Decision evidence
public snapshotAI called this Suspicious at 93.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run sends a usage event to getreadystack.com containing only the event type, package slug, CLI source and reason.
- The usage event runs after free checks; it is suppressed by opt-out environment variables, CI, or when there is no TTY.
- The README describes the CLI and MCP features but does not disclose runtime usage telemetry.
Evidence against
- The manifest has no lifecycle scripts, and the CLI is the package's documented entry point.
- The usage event does not include credentials, file contents, paths, hostnames or usernames.
- License keys are sent to the publisher's service for license validation or rule-feed access.
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
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/iot-data-notice-lint@1.0.2.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/iot-data-notice-lint@1.0.2 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.