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

npm-unused

v1.0.1

Published

Detect unused dependencies in JavaScript/TypeScript projects

Readme

npm-unused

Find unused dependencies in JS/TS projects.

Why Remove Unused Dependencies?

  • Faster installs — fewer packages to download and resolve
  • Smaller node_modules — saves disk space and speeds up CI builds
  • Reduced attack surface — every dependency is a potential security risk
  • Cleaner codebase — easier for new contributors to understand what the project actually uses

Install

npm install -g npm-unused
# or
npx npm-unused

Usage

npm-unused                          # scan current directory
npm-unused --dir /path/to/project   # scan a specific project
npm-unused --ignore jest eslint     # skip specific packages
npm-unused --json                   # machine-readable output
npm-unused --ci                     # exit code 1 if unused deps found

| Flag | Description | | ------------------- | ------------------------------------ | | --dir <path> | Project directory (default: cwd) | | --ignore <pkg...> | Packages to exclude from the report | | --json | Output as JSON | | --ci | Non-zero exit when unused deps exist | | -V, --version | Print version | | -h, --help | Show help |

Example

ℹ Scanned project at /home/user/my-app
ℹ Found 12 deps and 8 devDeps
ℹ Detected 15 imported packages in source files

❌ Unused dependencies:
  • axios
  • lodash

❌ Unused devDependencies:
  • eslint

Suggested fix:
  npm uninstall axios lodash eslint

How It Works

  1. Reads dependencies / devDependencies from package.json
  2. Discovers .js .jsx .ts .tsx files via fast-glob
  3. Parses each file with @babel/parser + @babel/traverse to collect import, require, and dynamic import() calls
  4. Reports any declared dependency not found in source

License

MIT