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

registry-contains

v1.3.2

Published

Verify whether semver requirements can be satisfied by a specific registry

Readme

Registry Contains

Registry Contains is a CLI tool that helps you identify which packages are missing in an npm-registry.

Aimed at assisting nodejs development within air-gapped / isolated networks using an inner npm mirror / registry.

Seems rather useless to me... What am I missing?

Let us imagine the following case:

You're a node developer happily working a nice cyber-security company that - for security measures - has it's own private network.

You just copied an example app you'd like to learn from into the network. It requires some dependencies so you hit an 'npm i' into a shell of your choice when... Oops! <some-package> is missing in your private npm registry. You take a deep breathe and ask the IT guys to get you that missing piece of data into the network (which can sometimes... be a little frustrating, to say the least).

Alright, after some testing and scanning they get your package inside the network, you upload it to your registry and hit 'npm i' once again.

...<some-other-package> is missing. Aahhhh...

Ever happened to you?

Probably not. But if you're one of a few - this package may be of assistance to you.

$ registry-contains package-json /path/to/app/package.json
Total of [4] packages are missing:
1) omg-what@^1.5.0
2) [email protected]
3) @types/[email protected]

Usage:

Using packages command:

Syntax: registry-contains packages [package@version package . . .]
$ registry-contains packages awesome-package [email protected] [email protected]

Using package-json command

Syntax: registry-contains package-json /path/to/app/package.json
$ registry-contains package-json ./package.json

Options

  • --registry <url>

    Use the specified registry instead of the configured one (default would be the same as 'npm get registry')
  • --no-ssl

    Disable CA verification

Run "registry-contains --help" for list of commands / options