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 🙏

© 2021 – Pkg Stats / Ryan Hefner









CircleCI Coverage Status semantic-release Commitizen friendly npm version

semantic-release-monorepo determines which commits apply to a given packages by seeing if they touched files in that package.

This fork instead uses only the commit messages to determine which packages are affected. In accordance with cz-lerna-changelog, the fork in this folder looks for a line in the commit message like

affects: @jcoreio/license-api, @jcoreio/license-api-backend

This is for special cases where the packages to publish are built by scripts in such a way that looking at which files were affected by a commit can't always determine which packages were actually affected.


Run semantic-release in the root of a monorepo package and apply @jcoreio/semantic-release-monorepo via the extends option.

On the command line:

$ npm run semantic-release -e @jcoreio/semantic-release-monorepo

Or in the release config:

  "extends": "@jcoreio/semantic-release-monorepo"