NPM Package Inspector

// latest version · license · dependencies · downloads — straight from the npm registry

react express lodash axios typescript
npm install

License
Last publish
Direct dependencies
Total versions

What does this tool check?

It queries the public npm registry (registry.npmjs.org) directly from your browser and shows the latest version, license, publish date, direct dependencies, and repository/homepage links for any published package — no install required.

How to use this tool

  • Type the exact npm package name and press Inspect
  • Check the license before adding a new dependency to your project
  • See direct dependencies before installing, to spot bloated packages
  • Confirm a package is still maintained via its last publish date

Why check a package before installing it

Every npm install pulls in that package's entire dependency tree, not just the package itself. A package with a handful of direct dependencies can easily resolve to hundreds of transitive packages once everything downstream is counted. Checking the direct dependency count before installing gives you a quick sense of how much you're actually adding to your project.

Publish date matters too — a package that hasn't been updated in years may be abandoned, unpatched for known vulnerabilities, or incompatible with current Node/browser versions. License matters for anything shipped commercially: GPL-family licenses carry different obligations than MIT or Apache-2.0.

Frequently Asked Questions

Where does this data come from?+
Directly from npm's own public registry API at registry.npmjs.org — the same source the npm CLI itself reads from. Nothing is cached or modified; you're seeing the live registry metadata.
Does this show bundle size or install size?+
No — this tool focuses on version, license, dependencies, and publish history. For minified/gzipped bundle size specifically, pair this with a dedicated bundle-size tool like Bundlephobia.
Why does it only show direct dependencies, not the full tree?+
The npm registry's package metadata only lists a package's own declared dependencies. Resolving the full transitive tree requires walking every dependency recursively, which isn't practical from a single registry lookup — run npm ls --all locally for the complete tree.