@readystack/rechnung-pflichtangaben-lint-de@1.0.1
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’s licensing and rule-feed traffic appears purpose-related, and the scanner’s credential-exfiltration claim is not supported by the source. However, paid-use failures trigger undisclosed runtime telemetry to the vendor, so this warrants a warning.
Decision evidence
public snapshot- When a license key is missing or rejected, the code calls a paywall event sender; it sends only from an interactive terminal or MCP session unless a telemetry opt-out is set.
- The event includes the package slug, CLI/MCP source and a reason, and is POSTed to getreadystack.com/api/ev.
- The README describes the paid features and license setup but does not disclose this runtime event.
- The event does not include paths, file contents, environment values or other user credentials.
- Telemetry is limited to interactive terminal or MCP sessions and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY.
- License keys are sent to Polar for validation and to getreadystack.com for the package’s license feed, which are license-related uses.
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.1.
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.1 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.