registry / @readystack/eu-data-residency-lint / 1.0.2
@readystack/eu-data-residency-lint@1.0.2
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 startup network request carries the package's own license key to its service for its rules feed, while license validation uses Polar's validation endpoint. The inspected telemetry contains package-use metadata, and no project data or unrelated credentials are sent.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
CLI startup; licensed scanning may also validate the license key.
Impact
No project content, unrelated credentials or account actions were identified.
Mechanism
Fetches the package's rules feed and performs license validation; telemetry contains package-use metadata.
AI rationale
The startup network request carries the package's own license key to its service for its rules feed, while license validation uses Polar's validation endpoint. The inspected telemetry contains package-use metadata, and no project data or unrelated credentials are sent.
Evidence
~/.config/readystack/eu-data-residency-lint.json
Network endpoints2
getreadystack.comapi.polar.sh
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The CLI is a Terraform and infrastructure residency linter; paid repository scans and licensing are described as package features.
- The CLI fetches an updated rules feed from getreadystack.com using its READYSTACK_LICENSE key; the code sends no project files or environment-variable values in that request.
- License validation sends the license key to Polar's license-validation endpoint.
- Paywall telemetry sends only the event type, package slug, source and reason, and is gated by opt-out and CI checks.
Evidence against
- The rules feed request includes the license key in its query string and runs at CLI startup, including before argument handling.
- The static routing hints allege credential exfiltration and sandbox-gated behavior in license.js, but the inspected source did not confirm those behaviors.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedlicense.jsView file
2'use strict';
L3: const https = require('https'), fs = require('fs'), path = require('path'), os = require('os');
L4: const ORG_ID = '';
...
L9: const RECHECK_MS = 7 * 24 * 3600 * 1000; // re-ask Polar every 7 days (refunds / cancellations)
L10: function storePath() { return path.join(process.env.READYSTACK_HOME || path.join(os.homedir(), '.config', 'readystack'), SLUG + '.json'); }
L11: function load() { try { return JSON.parse(fs.readFileSync(storePath(), 'utf8')); } catch (e) { return {}; } }
L12: function save(o) { try { fs.mkdirSync(path.dirname(storePath()), { recursive: true }); fs.writeFileSync(storePath(), JSON.stringify(o)); } catch (e) { /* read-only home: still work...
...
L31: req.on('error', function () { resolve({ ok: false, offline: true }); });
L32: req.write(body); r
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L22Trigger-reachable chain: manifest.bin -> cli.js -> license.js
L2: 'use strict';
L3: const https = require('https'), fs = require('fs'), path = require('path'), os = require('os');
L4: const ORG_ID = '';
...
L9: const RECHECK_MS = 7 * 24 * 3600 * 1000; // re-ask Polar every 7 days (refunds / cancellations)
L10: function storePath() { return path.join(process.env.READYSTACK_HOME || path.join(os.homedir(), '.config', 'readystack'), SLUG + '.json'); }
L11: function load() { try { return JSON.parse(fs.readFileSync(storePath(), 'utf8')); } catch (e) { return {}; } }
L12: function save(o) { try { fs.mkdirSync(path.dirname(storePath()), { recursive: true }); fs.writeFileSync(storePath(), JSON.stringify(o)); } catch (e) { /* read-only home: still work...
...
L31: req.on('error', function () { reso
Findings
2 Critical2 High3 Medium5 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
HighSandbox Evasion Gated Capabilitylicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowAi Review EvidenceREADME.md
Affected versions and remediation
This report applies to @readystack/eu-data-residency-lint@1.0.2.
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.2 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.