@readystack/streitbeilegung-hinweis-lint@1.0.2
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.
Findet den seit 20.07.2025 toten OS-Plattform-Link, Zitate der aufgehobenen ODR-VO (VO (EU) 2024/3228) und fehlende Hinweise nach § 36 VSBG in Impressum, AGB und Footer.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package performs undisclosed runtime telemetry on interactive free runs, although the event contains only product and usage metadata and has opt-out flags. The credential-related code handles the user’s own license for validation and product rule delivery, with no evidence of unrelated credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
After a free CLI scan, when running interactively and without the telemetry opt-out or CI flags.
Impact
The vendor learns that the package was used; no sensitive user or project data is included in the observed payload.
Mechanism
Posts the product slug, CLI source, and free-run reason to getreadystack.com/api/ev.
AI rationale
The package performs undisclosed runtime telemetry on interactive free runs, although the event contains only product and usage metadata and has opt-out flags. The credential-related code handles the user’s own license for validation and product rule delivery, with no evidence of unrelated credential exfiltration.
Evidence
cli.jslicense.jsREADME.md
Network endpoints1
getreadystack.com/api/ev
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A normal free CLI run calls pingUse after scanning files.
- pingUse sends a use event containing the product slug, CLI source, and free-run reason to getreadystack.com/api/ev.
- The event is skipped when DO_NOT_TRACK=1, READYSTACK_NO_TELEMETRY, or CI is set, or when the process is not interactive.
- The README describes the scanner and its free and licensed features but does not disclose this runtime telemetry.
Evidence against
- The telemetry payload contains only product and event metadata; no file contents, credentials, or environment values are included.
- License validation sends the user-provided product license to Polar, and the rules feed sends it to the package vendor, consistent with the documented licensed features.
- The package’s stated purpose and engine source match a legal notice linting tool.
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...
...
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/streitbeilegung-hinweis-lint@1.0.2.
See all versions of @readystack/streitbeilegung-hinweis-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/streitbeilegung-hinweis-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.