@readystack/payroll-rate-expiry-lint@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.
The day your rate table stopped being correct, with the line number
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package performs runtime telemetry to its vendor that is not disclosed in the README, which meets the review criteria for suspicious telemetry. The flagged licence-key traffic is consistent with validating the package’s own licence, and the telemetry payloads do not include scanned files or credentials.
Decision evidence
public snapshot- A free CLI run sends a `use` event containing the package slug, source and reason to `getreadystack.com/api/ev`.
- The free-run event is called after scanning when the command is not in paid mode; it can be disabled with environment flags, but the README does not disclose it.
- A failed or missing licence can also send a `paywall` event with the product slug, source and reason to the same endpoint.
- The package’s licence key is sent to the vendor’s licence endpoint for validation, consistent with its paid licence feature.
- The event payloads contain usage and paywall fields, not scanned file contents or credentials.
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/payroll-rate-expiry-lint@1.0.5.
See all versions of @readystack/payroll-rate-expiry-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/payroll-rate-expiry-lint@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.