@readystack/tfstate-secret-leak-lint@1.0.6
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 CLI sends limited runtime usage events to the publisher without documenting them in the README, making this undisclosed telemetry a warning-level concern. The inspected events do not include credentials or project data, and license-key requests go to the package’s stated licensing services.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running the CLI interactively or using its MCP server; paywall events occur when a key is missing or invalid, and a usage event follows a free CLI run.
Impact
The publisher receives limited usage information. No credential or project-data exfiltration was identified.
Mechanism
HTTPS POST requests send a package slug, source mode, and event reason to getreadystack.com; CI and telemetry opt-out settings suppress these events.
AI rationale
The CLI sends limited runtime usage events to the publisher without documenting them in the README, making this undisclosed telemetry a warning-level concern. The inspected events do not include credentials or project data, and license-key requests go to the package’s stated licensing services.
Evidence
license.jscli.jsREADME.md~/.config/readystack/tfstate-secret-leak-lint.json (or READYSTACK_HOME/tfstate-secret-leak-lint.json)
Network endpoints4
getreadystack.com/api/evgetreadystack.com/api/licgetreadystack.com/api/rules/api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 92.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI sends a runtime event to getreadystack.com containing the package slug, CLI/MCP source, and a reason such as no_key or invalid.
- The event is sent only in an interactive terminal or MCP session and is suppressed by CI, DO_NOT_TRACK=1, or READYSTACK_NO_TELEMETRY.
- The README describes the CLI and paid features but does not disclose these usage events.
Evidence against
- License validation sends the user-provided license key to getreadystack.com and Polar, which are used for license checks.
- The usage event contains package and mode details rather than credentials, file contents, or project data.
- The manifest exposes cli.js as the executable; 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...
...
L33: 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...
...
L33
Findings
3 Critical2 High3 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
CriticalPrevious Version Dangerous Deltacli.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
Affected versions and remediation
This report applies to @readystack/tfstate-secret-leak-lint@1.0.6.
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.6 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.