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

@npm-breach/check

v1.0.7

Published

Security-focused CLI tool to detect potentially vulnerable packages in your Node.js applications

Readme

NPM Breach Check

Security-focused CLI tool to detect potentially vulnerable packages in your Node.js applications

A lightweight command-line scanner that checks for known vulnerable packages in your dependency tree. Help protect your applications by identifying packages that may pose security risks.

Quick Start

# Install globally
npm install -g @npm-breach/check

# Check your project for vulnerable packages
npm-breach-check

Usage

# Scan all packages in your project (default)
npm-breach-check

# Check a specific package and version
npm-breach-check check-package lodash "^4.17.20"

# List all monitored packages  
npm-breach-check list

# Show help
npm-breach-check help

Example Output

Summary:
  Total checked: 60
  Found: 12
  Affected versions: 1
  Used but not affected: 11
  Not used in the project: 48

Affected versions:
==================
  ✓ [email protected] (affected: 2.2.1)

Used but not affected:
======================
  ⚠ [email protected] (affected: 4.4.2)
  ⚠ [email protected] (affected: 5.6.1)
  ⚠ [email protected] (affected: 10.2.1)
  ⚠ [email protected] (affected: 7.1.1)
  ⚠ [email protected] (affected: 6.2.1)
  ⚠ [email protected] (affected: 9.0.1)
  ⚠ [email protected] (affected: 3.1.1)
  ⚠ [email protected] (affected: 2.0.1)
  ⚠ [email protected] (affected: 0.3.3)
  ⚠ [email protected] (affected: 6.0.1)
  ⚠ [email protected] (affected: 1.3.3)
  • Affected versions - Vulnerable packages found (need immediate attention)
  • Used but not affected - Packages installed but in safe versions
  • Not used in project - Packages not installed (you're safe)

Features

  • Zero Configuration - Works out of the box
  • Lightweight - Only one dependency (semver)
  • Fast Scanning - Native Node.js performance
  • Semantic Versioning - Supports version ranges (^, ~, >=, etc.)
  • Dependency Tree Analysis - Deep scanning with npm ls

What It Checks

This tool monitors a curated list of packages known to have security considerations, including:

  • Color manipulation packages (chalk, ansi-styles)
  • Angular/React form utilities
  • File processing libraries
  • Template engines
  • And many more...

Run npm-breach-check list to see the complete monitored package list.

Contributing

We welcome contributions to improve package security monitoring!

Adding New Packages

To add a potentially vulnerable package to the monitoring list:

  1. Fork this repository
  2. Edit affected-packages.json
  3. Add your package with version constraints:
    {
      "name": "package-name",
      "versions": ["^1.0.0", ">=2.1.0"]
    }
  4. Submit a pull request with details about the security concern

Development Setup

git clone https://github.com/your-username/npm-breach-check.git
cd npm-breach-check
npm install
npm link

License

MIT © Contributors


Help keep the Node.js ecosystem secure - contribute to the monitored package list!