@readystack/rechnung-pflichtangaben-lint-de
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.
Prüft PHP-Rechnungstemplates von WooCommerce- und WordPress-Shops gegen alle zehn Pflichtangaben des § 14 Abs. 4 UStG — 17 Regeln, Befunde mit Zeilennummer.
This report shows the evidence for @readystack/rechnung-pflichtangaben-lint-de@1.0.6. 0 of 5 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends undisclosed runtime usage telemetry to its own service after interactive free scans. The event is limited to package and usage details, so this is suspicious telemetry rather than credential or project data exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
After a free CLI scan in an interactive terminal; paywall events also occur when a license is missing or rejected.
Impact
The vendor can track interactive usage and paywall outcomes; the inspected events do not send project contents or credentials.
Mechanism
HTTPS POST events report the package slug, invocation source, and event reason to the vendor’s event endpoint.
AI rationale
The package sends undisclosed runtime usage telemetry to its own service after interactive free scans. The event is limited to package and usage details, so this is suspicious telemetry rather than credential or project data exfiltration.
Evidence
cli.jslicense.js
Network endpoints1
getreadystack.com/api/ev
Decision evidence
public snapshotAI called this Suspicious at 92.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- After a non-paid CLI scan, the CLI calls `pingUse()` and sends a runtime usage event.
- The event contains the package slug, CLI source, and `free` reason, and is sent to `getreadystack.com/api/ev`.
- The event is limited to interactive sessions and can be disabled with `DO_NOT_TRACK=1` or `READYSTACK_NO_TELEMETRY`; the README does not disclose it.
Evidence against
- The event does not include file contents, paths, credentials, or other project data.
- License validation sends the package’s own license key to the vendor’s licensing service as part of paid-feature checks.
- The rules feed is fetched from the vendor’s domain and appended as rule data; the engine processes rules as matching patterns rather than executing downloaded code.
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/rechnung-pflichtangaben-lint-de@1.0.6.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/rechnung-pflichtangaben-lint-de@1.0.6 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.