@readystack/tfstate-secret-leak-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.
Names the attributes, outputs and backends that copy a cleartext secret into terraform.tfstate
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends undisclosed, default-on runtime telemetry for some interactive license checks, though the payload contains only a package slug, source and reason. License key traffic goes to the license provider or package vendor for validation and rules, consistent with the package's licensing function.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A paid CLI operation or MCP check_dir invokes license checking; a missing or invalid key can trigger the event in an interactive terminal or MCP session.
Impact
The event does not expose credentials or scanned content, but runtime telemetry is enabled by default and is not documented for users.
Mechanism
license.js posts the package slug, CLI/MCP source and reason to getreadystack.com/api/ev unless DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY is set.
AI rationale
The package sends undisclosed, default-on runtime telemetry for some interactive license checks, though the payload contains only a package slug, source and reason. License key traffic goes to the license provider or package vendor for validation and rules, consistent with the package's licensing function.
Evidence
license.jscli.js~/.config/readystack/tfstate-secret-leak-lint.json (or READYSTACK_HOME override)~/.config/readystack/tfstate-secret-leak-lint.trial.json
Network endpoints3
getreadystack.com/api/evapi.polar.sh/v1/customer-portal/license-keys/validategetreadystack.com/api/rules/<slug>?key=<license>
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- On paid CLI or MCP checks, missing or invalid license keys can trigger a paywall event to getreadystack.com when running interactively; it is enabled by default but has opt-out environment variables.
- The event payload contains only the package slug, CLI/MCP source and reason, with no credential or file contents.
Evidence against
- License validation sends the package's own license key to Polar's license validation endpoint.
- The rules feed sends that same license key to the package vendor to retrieve rules, and accepts only a JSON rules array.
- The package is described as a Terraform state linter, and its CLI scans only files requested by the user or directory-scan command.
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
3 Critical1 High4 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
CriticalPrevious Version Dangerous Deltalicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencelicense.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @readystack/tfstate-secret-leak-lint@1.0.2.
See all versions of @readystack/tfstate-secret-leak-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/tfstate-secret-leak-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.