@readystack/rechnung-pflichtangaben-lint-de@1.0.5
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.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends undisclosed runtime usage telemetry to its vendor after free interactive CLI runs. The event contains only package and event fields, and the credential-related requests serve license validation and the vendor’s own rules feed, so the evidence supports a warning rather than a malicious verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Automatically after a free CLI run, when the process is interactive and telemetry is not disabled or running in CI.
Impact
The vendor can count package use and event types; no project contents or credentials are included in this event.
Mechanism
POSTs a small event containing the package slug, CLI source and reason to getreadystack.com/api/ev.
AI rationale
The package sends undisclosed runtime usage telemetry to its vendor after free interactive CLI runs. The event contains only package and event fields, and the credential-related requests serve license validation and the vendor’s own rules feed, so the evidence supports a warning rather than a malicious verdict.
Evidence
cli.jslicense.js~/.config/readystack/rechnung-pflichtangaben-lint-de.json
Network endpoints3
getreadystack.com/api/evgetreadystack.com/api/rules/api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 95.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI sends a runtime usage event to getreadystack.com containing the package slug, source and event reason; it runs unless telemetry opt-out or CI conditions apply.
- The event is triggered automatically after a free CLI run, including when a user runs the package on named files.
- The license key is sent to Polar for validation, while the vendor rules feed uses that key to retrieve the package’s rules.
Evidence against
- The usage event contains limited package and event fields, not project files, credentials or environment values.
- Telemetry can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY; it is also suppressed in CI and non-interactive runs.
- License checks and rules-feed requests go to the named license provider and the package vendor’s own service. No credential theft or unrelated collector was identified.
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/rechnung-pflichtangaben-lint-de@1.0.5.
See all versions of @readystack/rechnung-pflichtangaben-lint-de for other recorded verdicts.
- Review the evidence and your use of @readystack/rechnung-pflichtangaben-lint-de@1.0.5 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.