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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@ivangrynenko/npm-validator-cli

v2.0.14

Published

Local CLI wrapper for the npm validator workflow

Readme

npm-validator CLI

This workspace packages the local npm-validator command-line interface. It mirrors the GitHub Action so you can scan repositories from your workstation before committing workflows.

Prerequisites

  • Node.js 20 LTS (minimum 18.x)
  • Python 3.11 on your PATH (the Python zipapp runs under the hood)

Install dependencies once from the repository root:

npm install

Running the scanner locally

Build the CLI bundle (required whenever you pull new changes):

npm --workspace cli run build

Invoke the executable against your project directory (replace ~/projects/my-app with the directory you want to scan):

npm --workspace cli exec npm-validator --root ~/projects/my-app

Using the published package

Install the CLI globally (or use npx) and run it directly:

npm install -g @ivangrynenko/npm-validator-cli
npm-validator --root ~/projects/my-app

# or without a global install
npx @ivangrynenko/npm-validator-cli --root ~/projects/my-app

Key options:

  • --list <path-or-url> – override the bundled compromised package list.
  • --warn-only – always return exit code 0, even if findings are detected.
  • --summary <path> / --json <path> / --inventory <path> – control where outputs are written.
  • --version / -v / -V – print the CLI version without running a scan.

You can also execute the binary directly for quick checks:

node cli/bin/npm-validator.js --root .

The CLI prints a table summarising findings, paths to the generated artifacts, and the compromised list source used during the scan.