@readystack/rechnung-pflichtangaben-lint-de@1.0.3
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 CLI sends undisclosed runtime telemetry on free scans, though the event contains only package-use metadata and has TTY and opt-out checks. License validation and the rules feed use the package's own paid-service flow, and no credential exfiltration or other attack was identified.
Decision evidence
public snapshot- The package's CLI entrypoint is cli.js.
- After a free CLI run, the program calls pingUse automatically.
- pingUse sends an event containing only the package slug, CLI source, and free-use reason to getreadystack.com/api/ev; it runs in a TTY and can be disabled with the documented-in-code environment flags.
- The event contains no hostname, username, file contents, credentials, or project details.
- License validation sends the user's license key to Polar's license-validation endpoint.
- The package describes its paid folder scan and license key in the README, and no install lifecycle script is present.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @readystack/rechnung-pflichtangaben-lint-de@1.0.3.
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.3 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.