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

@kaitlynbassford/depwhy

v1.0.0

Published

Explains why a package is in your dependency tree, from the lockfile. npm, pnpm, yarn, bun, uv, poetry, cargo, and go.

Readme

depwhy

Why is this package in my dependency tree? depwhy reads your lockfile (package-lock.json, pnpm-lock.yaml, uv.lock, Cargo.lock) and tells you, offline by default, which direct dependencies pull a package in, what removing a direct dependency would free, and which packages are installed at more than one version.

npm install -g @kaitlynbassford/depwhy      # installs the `depwhy` command
npx @kaitlynbassford/depwhy lodash          # or run it once
depwhy lodash
depwhy --remove express
depwhy --dupes

This npm package is a thin launcher. On install it downloads the matching native binary for your platform from the GitHub release of the same version, checks its SHA-256 against the release's checksums.txt, and runs it. If your npm skips install scripts (--ignore-scripts, or npm 12's default), the binary is downloaded the first time you run depwhy instead.

The package is scoped because npm refused the plain name depwhy as too similar to the existing package dep-why. The installed command is still depwhy.

Supported: Linux, macOS and Windows on x64 and arm64, Node.js 18 or newer.

Full documentation, flags, and the JSON format: https://github.com/dpologdvinity/depwhy