@readystack/aks-eks-support-cliff-lint@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.
Terraform EKS and AKS version check: sample clusters.tf on 2026-09-27 — $2,256 extra on EKS 1.32 since 2026-03-23, $3,660 on 1.31 since 2025-11-26, $5,916 total; 9 rules
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends default runtime usage telemetry to the vendor, with an environment-variable opt-out; the README does not disclose that telemetry. The inspected payloads contain no credentials or project data, so this warrants a warning rather than a publish block.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the CLI interactively; a paywall ping can also occur when a paid feature lacks a valid license.
Impact
The vendor can observe package usage and paywall outcomes. The inspected payloads do not include credentials or project contents.
Mechanism
HTTPS POST requests send package and usage fields to getreadystack.com. The pings can be disabled with documented environment-variable checks in source.
AI rationale
The CLI sends default runtime usage telemetry to the vendor, with an environment-variable opt-out; the README does not disclose that telemetry. The inspected payloads contain no credentials or project data, so this warrants a warning rather than a publish block.
Evidence
cli.jslicense.js~/.config/readystack/aks-eks-support-cliff-lint.jsonREADYSTACK_HOME/aks-eks-support-cliff-lint.json
Network endpoints3
getreadystack.com/api/evapi.polar.sh/v1/customer-portal/license-keys/validategetreadystack.com/api/rules/
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Free CLI runs call a usage ping that sends the package slug, CLI source, and the reason "free" to getreadystack.com.
- The usage ping is enabled by default for interactive terminal runs, though DO_NOT_TRACK, READYSTACK_NO_TELEMETRY, and CI disable it.
- A separate paywall ping sends the package slug, source, and a no-key or invalid-key reason to the same endpoint.
- License keys are sent to Polar for validation; the subscription feed also uses a supplied package license key to fetch rules.
Evidence against
- The telemetry payloads shown contain package and usage fields, not discovered credentials, file contents, or project data.
- Network activity is tied to CLI use and paid feature checks; no install lifecycle scripts are declared.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
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 = 'a5cdf664-d8e7-4f87-8895-056717aaba17';
...
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:
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 = 'a5cdf664-d8e7-4f87-8895-056717aaba17';
...
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
Findings
2 Critical2 High4 Medium4 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
MediumAi Review Evidencecli.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @readystack/aks-eks-support-cliff-lint@1.0.1.
See all versions of @readystack/aks-eks-support-cliff-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/aks-eks-support-cliff-lint@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.