@readystack/rechnung-pflichtangaben-lint-de@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.
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 flagged network and credential behavior is tied to this linter's licence validation and vendor rules feed; the configured product key is sent to the package vendor for that feed. The usage request contains only fixed package and source fields, and the inspected feed handling adds structured rules rather than executing downloaded code.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
CLI startup, when a licence key is configured, and CLI use for the usage count.
Impact
No credential theft, project-data collection, or unrelated account action was identified in the inspected source.
Mechanism
The CLI sends the product licence key to the vendor's rules endpoint to retrieve rules; it also validates keys with Polar. The usage count contains fixed package and command fields, not scanned file contents.
AI rationale
The flagged network and credential behavior is tied to this linter's licence validation and vendor rules feed; the configured product key is sent to the package vendor for that feed. The usage request contains only fixed package and source fields, and the inspected feed handling adds structured rules rather than executing downloaded code.
Evidence
${READYSTACK_HOME}/rechnung-pflichtangaben-lint-de.json~/.config/readystack/rechnung-pflichtangaben-lint-de.json
Network endpoints2
getreadystack.comapi.polar.sh
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package describes a CLI that checks PHP invoice templates against tax invoice requirements.
- At CLI startup, the program may fetch a rules feed and append the returned rules to its rule list.
- The feed request sends the configured product licence key to getreadystack.com; it runs only when a key is present and caches the response.
- The engine evaluates structured rule types against input text and returns findings; the inspected code does not execute feed content as code.
- Licence validation sends the key to api.polar.sh, the licence validation service.
- Usage telemetry sends fixed fields for the package slug, CLI source and usage reason, rather than scanned file contents.
Evidence against
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...
...
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 High3 Medium5 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
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowAi Review Evidencepackage.json
Affected versions and remediation
This report applies to @readystack/rechnung-pflichtangaben-lint-de@1.0.4.
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.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.