@readystack/eu-data-residency-lint@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.
Every cloud region in your infrastructure code, mapped to a country and the transfer basis it needs.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe source sends undisclosed runtime usage and paywall telemetry to the vendor, which warrants a warning under the telemetry rules. The reviewed flows do not show credentials or project data being sent to an unrelated host.
Decision evidence
public snapshot- After a free CLI run, interactive terminal use sends a usage event containing the tool slug and source to getreadystack.com/api/ev.
- When a paid feature has no valid key, the CLI or MCP path can send a paywall event with the tool slug, source and reason to the same endpoint.
- The telemetry is gated by interactive use and has opt-out checks for DO_NOT_TRACK, READYSTACK_NO_TELEMETRY and CI.
- The event payload contains package-use and paywall fields, not discovered credentials, file contents or project data.
- License validation sends the user-supplied READYSTACK license key to the vendor's own getreadystack.com licensing endpoint.
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/eu-data-residency-lint@1.0.3.
See all versions of @readystack/eu-data-residency-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/eu-data-residency-lint@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.