@readystack/container-hardening-800-190@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.
Reads a Dockerfile or compose file and names the hardening controls it fails, with the NIST SP 800-171 requirement each one puts at risk.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends limited runtime usage telemetry to the vendor by default, and the README does not disclose it. The event has opt-outs and contains no file or project data, so this warrants a warning rather than a malicious verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the CLI interactively triggers a usage event after a free run; a saved license key also triggers a rules-feed request at CLI startup.
Impact
The vendor can observe interactive usage and paywall status. The reviewed flows do not send file contents or third-party credentials.
Mechanism
HTTPS requests send limited usage metadata to getreadystack.com. A license key is included in the rules-feed query; license validation uses api.polar.sh.
AI rationale
The CLI sends limited runtime usage telemetry to the vendor by default, and the README does not disclose it. The event has opt-outs and contains no file or project data, so this warrants a warning rather than a malicious verdict.
Evidence
cli.jslicense.jsREADME.md~/.config/readystack/container-hardening-800-190.json (or the READYSTACK_HOME override)the path supplied with --out
Network endpoints2
getreadystack.comapi.polar.sh
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free interactive CLI run sends a use event with the package slug, CLI source, and reason to getreadystack.com.
- That telemetry is sent by default for TTY use, with DO_NOT_TRACK=1 and READYSTACK_NO_TELEMETRY opt-outs; the README describes the tool but does not disclose telemetry.
- When a saved or supplied license key exists, startup fetches the package's rules feed from getreadystack.com using the key in the query string.
Evidence against
- The use event contains package-use metadata, not file contents, project data, or third-party credentials.
- The license key is sent to the package's own service for its rules feed; validation goes to Polar's license endpoint.
- The package's documented purpose is to audit Dockerfiles and Compose files, and the reviewed source contains no install lifecycle script.
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
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/container-hardening-800-190@1.0.1.
See all versions of @readystack/container-hardening-800-190 for other recorded verdicts.
- Review the evidence and your use of @readystack/container-hardening-800-190@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.