Cybersecurity Container Audit — NIST SP 800-190
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
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.
Install
container-hardening-800-190 file
Node 18+. The same 19 rules as the VS Code extension, from a terminal or CI.
Free
- Audits the Dockerfile or compose file you have open against all 19 NIST SP 800-190 checks and prints every failing line with its fix and the requirement it restores.
--ruleslists every rule
With a licence ($29 once)
- Audits every container file in the workspace at once and exports the dated evidence report (Markdown and CSV) an assessor asks for, for commercial and team use.
container-hardening-800-190 --dir ./templates --report html --out report.html
A consultancy NIST SP 800-171 gap assessment runs $3,500 to $20,000 and takes 2 to 6 weeks.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "container-hardening-800-190": { "command": "container-hardening-800-190", "args": ["--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: Cybersecurity Container Audit — NIST SP 800-190
run: pip install rulestamp-container-hardening-800-190 && container-hardening-800-190 --dir . --ci
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install rulestamp-container-hardening-800-190
container-hardening-800-190 --help
Metadata
Release files for rulestamp-container-hardening-800-190 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rulestamp_container_hardening_800_190-1.0.3.tar.gz | 17.4 kB | Without provenance | Details for rulestamp_container_hardening_800_190-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_container_hardening_800_190-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_container_hardening_800_190-1.0.3-py3-none-any.whl |
Total release size: 37.1 kB
Release files / rulestamp_container_hardening_800_190-1.0.3.tar.gz
| Download URL | rulestamp_container_hardening_800_190-1.0.3.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
50ffdb9e3decdb79890914209892e15050fc1125695fbe935772060e07e32997
|
|
BLAKE2b-256 checksum How to use checksums |
f5ae7250ba4ae19c08b446e5e97d6ceb3320aad3bdbbd2a64d5a268ec238a04a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_container_hardening_800_190-1.0.3-py3-none-any.whl
| Download URL | rulestamp_container_hardening_800_190-1.0.3-py3-none-any.whl |
|---|---|
| Size | 19.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a84e4ded17706f174464d32442cfc915590dcdb3cac4e5bb4b30fe36405238fe
|
|
BLAKE2b-256 checksum How to use checksums |
48eb45d9f16e0f4bccdd9eb6c91180f83c4d19dd07f047d3330ae950f1207912
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-container-hardening-800-190 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.