@readystack/vergabe-schwellenwerte-check-2026
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.
Veraltete EU-Schwellenwerte in Vorlagen und Konfig-Dateien finden — Werte seit 2026-01-01
This report shows the evidence for @readystack/vergabe-schwellenwerte-check-2026@1.0.3. 0 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package’s scanner and license checks match its stated purpose, and the flagged credential flow is license validation. However, free CLI use triggers runtime telemetry that is not disclosed in the README, so this merits a warning rather than a clean verdict.
Decision evidence
public snapshot- A completed free CLI scan automatically calls pingUse unless the run is paid.
- The runtime event sends the tool slug, CLI source and a fixed reason to getreadystack.com/api/ev; it contains no file contents or credential values.
- The README describes free and licensed features but does not disclose this runtime telemetry.
- The reported event contains limited usage metadata rather than credentials, project data or file contents.
- License keys are validated with the package vendor as part of the documented paid workflow.
- No install lifecycle scripts are declared in the manifest.
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/vergabe-schwellenwerte-check-2026@1.0.3.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/vergabe-schwellenwerte-check-2026@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.