@readystack/kassenbeleg-tse-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.
15 Regeln prüfen eine Belegvorlage gegen § 6 KassenSichV und § 146a AO; in der mitgelieferten Beispielvorlage findet der Lint 8 Verstöße — 7 Fehler und 1 Warnung. § 379 Abs. 4 AO nennt für Verstöße ge
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends runtime usage and paywall telemetry to the vendor without describing it in the README. The payloads contain limited event metadata and have opt-outs, so this warrants a warning rather than a malicious verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A person runs the CLI interactively; free runs report use, while paid operations without a valid key may report a paywall event.
Impact
The vendor learns that the package was used or reached its paywall. The inspected telemetry fields do not include host, user, project, file or credential data.
Mechanism
HTTPS POST requests send the package slug, event type, CLI or MCP source, and a reason field. DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY disables the events.
AI rationale
The CLI sends runtime usage and paywall telemetry to the vendor without describing it in the README. The payloads contain limited event metadata and have opt-outs, so this warrants a warning rather than a malicious verdict.
Evidence
cli.jslicense.jsREADME.md~/.config/readystack/kassenbeleg-tse-lint.json
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 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run sends a usage event to getreadystack.com with the package slug, source and reason fields.
- When a paid operation has no license key, the CLI sends a paywall event to getreadystack.com with the slug, source and reason fields.
- Both telemetry paths have opt-outs, but the README does not disclose this runtime telemetry.
Evidence against
- License validation sends the package’s own license key to getreadystack.com and api.polar.sh for its stated validation purpose.
- The rules feed is fetched from getreadystack.com and its returned rules are appended to the linter’s rule list.
- The telemetry payloads shown contain event metadata rather than host, user, project, file or credential data.
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/kassenbeleg-tse-lint@1.0.4.
See all versions of @readystack/kassenbeleg-tse-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/kassenbeleg-tse-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.