@readystack/container-hardening-800-190@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.
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 undisclosed runtime usage telemetry to the vendor on ordinary free runs. Its payload is limited and has opt-outs, and the reviewed sources show no credential theft or project-data exfiltration.
Decision evidence
public snapshot- A normal free CLI run calls pingUse(), which sends an event to getreadystack.com when telemetry opt-outs are absent.
- The event contains the package slug, CLI source and a fixed reason; the source provides opt-out environment variables, but the README does not disclose this usage telemetry.
- The telemetry payload does not include credentials, file contents, project paths or other identifying details.
- License keys are used for validation and rule-feed requests to the package’s licensing service.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @readystack/container-hardening-800-190@1.0.2.
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.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.