Free NPM Package Lookup

NPM Package Info is a free online tool that lets you look up information about any NPM package including versions, dependencies, and download stats.

Yes, it is completely free with no registration required.

NPM Package Info displays package description, latest version, all versions, dependencies, weekly downloads, repository links, and license information.

Absolutely. The NPM Package Lookup processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.

Yes, the NPM Package Lookup is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.

No account or registration is needed. Simply open the NPM Package Lookup in your browser and start using it immediately. There are no sign-up walls or usage restrictions.

The NPM Package Lookup supports a wide range of popular formats and languages. Check the tool interface for the full list of supported options.

Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.

The NPM Package Lookup works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.

A scoped package is published under an npm organization or user namespace, written as @scope/name, and you search for it the same way you search for any package: type the full name, including the leading @ and the slash, into the lookup. The tool queries the public npm registry directly, so @tanstack/react-query, @types/node, and @angular/core all resolve to their real metadata, versions, and dependencies. Scoped names matter because two packages can share a base name but live under different scopes, so dropping the prefix would return the wrong project or nothing at all. The install commands generated for npm, yarn, pnpm, and bun keep the scope intact, and the CDN links for unpkg and jsDelivr are URL-encoded correctly. Enter the complete scoped name above to inspect it before adding it to your package.json.

There are two ways a package ships TypeScript support, and the lookup distinguishes them with a badge. Built-in types mean the package itself declares a types or typings field in its package.json and bundles its own .d.ts definitions, so you get full IntelliSense the moment you install it with nothing extra. The other path is DefinitelyTyped, where the types live in a separate community package named @types/something that you install as a dev dependency. When a package lacks built-in types but a matching @types package exists, the tool surfaces a ready-to-copy npm install -D @types/... command so you do not have to hunt for it. Knowing which case you are in saves a frustrating round of red squiggles after installation. Search any package here to see its TypeScript status before you commit to the dependency.

These three groups in a package.json serve different roles, and the Dependencies tab separates them so you can read them at a glance. Runtime dependencies are the packages a project needs to actually run and that get installed automatically when someone installs it. devDependencies are tools needed only during development or building, such as test runners, bundlers, and type definitions; they are skipped when the package is consumed as a dependency. peerDependencies declare a package the host project must already provide, like a plugin requiring a specific React or ESLint version, rather than bundling its own copy, which prevents duplicate or conflicting installs. Mismatched peers are a frequent source of install warnings and runtime bugs. Each dependency here is a clickable badge that re-runs the lookup, so you can walk the tree by hand and inspect every package before adding it.

npm uses dist-tags, which are named pointers to specific published versions, and the lookup lists them in the Versions tab alongside the full dated release history. The latest tag is the default: when you run npm install with no version, you get whatever latest points to, which is normally the newest stable release. The next tag conventionally points to a pre-release or beta build that maintainers want available for testing without making it the default install. Other custom tags such as canary, rc, or legacy may also appear depending on the project. This matters because installing next or another tag pulls code that may be unstable or change without notice. Browse the dated version history here to confirm exactly when a fix or feature landed, then pin the precise version you want in your package.json rather than trusting a moving tag.

The download figures come from npm's official downloads API, the same source other registry tools use, and the lookup shows total installs over the last 30 days plus a daily sparkline so you can see whether usage is rising or flat. It is important to read these as a popularity signal rather than a count of distinct human users. Every install counts, including automated CI pipelines, Docker image builds, mirror servers, and a developer running npm install repeatedly, all of which inflate the raw total. A package pulled in as a transitive dependency of something popular can show huge numbers without being directly chosen by anyone. Use the trend and relative scale to compare candidates and spot abandoned forks, not as an exact audience size. Search a package here to view its monthly downloads and trend before weighing it against alternatives.