npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2022 – Pkg Stats / Ryan Hefner




get health status from various sources like dbs, filesystems or upstream services






This npm module contains various healthchecks in order to retrieve the status from different sources like dbs, filesystems or upstream services.


  • read+write check by incrementing a counter within a document, if index or document does not exist yet it is created on first run


  • read+write check by creating a new document with a random testvalue in a capped collection of max 1 document on each run


  • read+write check by incrementing a counter stored within a sequence, if sequence does not exist yet it is created on first run


  • read+write check by incrementing a counter associated with a specific key, if key does not exist yet it is created on first run


  • dummy check for testing purposes which does not perform any tests and always returns true


  • performs a GET request to /alive endpoint and resolves check successfully if a http status code of 200 OK is returned


  • read+write check by creating and removing a file in a temporary directory


Before starting development

  • Install npm packages: make npm or npm install
  • Build service dependencies (docker images): make build-dev-images
  • Start service dependencies (docker container): make dev-inf-up
  • Watch for file changes: npm run watch
    • alternatively press ⇧⌘B to execute default task runner in vscode

During development

  • Run test suite: npm run test
  • Commit your changes into a separare feature branch using semantic commit messages
  • Regulary push your changes to remote origin

After finishing development

  • Stop service dependencies: make dev-inf-down
  • Push your changes to remote origin
  • Create a pull request from feature branch to branch Development via the Webinterface of git server
    • Add a reviwer to the pull request
  • Check CI/CD Pipeline result


  • Sign in to registry with npm adduser --registry=<registry> --always-auth
  • Update version number in package.json file
  • Make sure to update .npmignore file
  • Run npm publish --registry=<registry> to push latest version to private registry
  • Signin to the registry and verify result