@readystack/container-hardening-800-190
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.
This report shows the evidence for @readystack/container-hardening-800-190@1.0.3. 0 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package performs undisclosed runtime telemetry after interactive free CLI runs, so this merits a warning. The event is limited to package-use metadata and does not expose project data or credentials.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
After a non-paid CLI run completes in an interactive terminal.
Impact
The vendor can count interactive free uses; the inspected payload contains no project or credential data.
Mechanism
Posts a small usage event to the vendor endpoint unless telemetry is disabled by environment variables or CI.
AI rationale
The package performs undisclosed runtime telemetry after interactive free CLI runs, so this merits a warning. The event is limited to package-use metadata and does not expose project data or credentials.
Evidence
cli.js
Network endpoints1
getreadystack.com/api/ev (POST)
Decision evidence
public snapshotAI called this Suspicious at 96.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A successful non-paid CLI run calls pingUse; that function sends a usage event to getreadystack.com/api/ev containing only the event type, package slug, CLI source and a fixed reason.
- The usage ping is skipped when DO_NOT_TRACK=1, READYSTACK_NO_TELEMETRY is set, or CI is set, and runs only when stdin or stdout is a TTY.
- The README describes free scans and licensed features but does not disclose the runtime usage ping.
Evidence against
- The ping payload contains no project files, paths, credentials, hostnames or usernames.
- The ping goes to the package vendor and can be disabled with environment variables.
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
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.3.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/container-hardening-800-190@1.0.3 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.