@readystack/tfstate-secret-leak-lint@1.0.4
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 runtime usage and paywall telemetry to the vendor during interactive use, without disclosing it in the README. The events contain limited package metadata and have opt-outs, so this is suspicious telemetry rather than credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A free CLI run in an interactive terminal, or an interactive paywall check; telemetry can be suppressed with the documented environment opt-outs in code.
Impact
The vendor receives usage and paywall event data; no user, project or credential data was identified in those event payloads.
Mechanism
The CLI posts package slug, source and reason fields to getreadystack.com/api/ev.
AI rationale
The package sends runtime usage and paywall telemetry to the vendor during interactive use, without disclosing it in the README. The events contain limited package metadata and have opt-outs, so this is suspicious telemetry rather than credential exfiltration.
Evidence
cli.jslicense.js
Network endpoints1
getreadystack.com/api/ev
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run sends a usage event containing the package slug, CLI source and a fixed reason to getreadystack.com/api/ev when run in a TTY, unless telemetry opt-outs or CI are set.
- The CLI calls the usage event after free runs; README.md does not disclose this telemetry.
- Interactive paywall checks also send a limited event with the package slug, source and reason to the vendor endpoint.
Evidence against
- The telemetry payloads contain package usage and reason fields, not hostnames, usernames, project data, file contents or credentials.
- Paywall telemetry is gated to a TTY or MCP session and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY; CLI usage telemetry also checks CI.
- The license key is used for Polar validation and the vendor's rules feed, consistent with the package's licensing feature.
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 = '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 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.4.
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.4 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.