npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@readystack/container-hardening-800-190

v1.0.2

Published

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.

Readme

Cybersecurity Container Audit — NIST SP 800-190

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

npx @readystack/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.
  • --rules lists 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.
@readystack/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": "npx", "args": ["-y", "@readystack/container-hardening-800-190", "--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: npx -y @readystack/container-hardening-800-190 --dir . --ci

(container: docker run --rm -v "$PWD:/work" getreadystack/container-hardening-800-190 --dir /work --ci)

The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.

Get a licence