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




Content Atom JavaScript, automatically generated from the Thrift definition.




Content Atom Model Definition

This is the Thrift definition of the Content Atom model, and the published versions of this repository are built from the autogenerated code in various languages.

Maven Central


You need to have french-thrift 0.9.3 installed locally.

How to release

$ sbt 'release cross'

This will release 3 artifacts to Maven Central:

  • content-atom-model-thrift-$version.jar contains only the Thrift files
  • content-atom-model_2.11-$version.jar contains the Thrift files and Scrooge-generated Scala 2.11 classes
  • content-atom-model_2.12-$version.jar contains the Thrift files and Scrooge-generated Scala 2.12 classes

You will need a PGP key and Sonatype credentials. See here and here for some helpful guides.

To cross release locally use

$ sbt '+publishLocal'


The JS library should be published to npmjs, see:

and npm help publish.

If you're unfamiliar with publishing on npm the following commands can be useful:

  • npm whoami - to find out your username (if you have created one)
  • npm adduser - to create a user
  • npm owner ls - to check the owners of content-atom.
  • npm owner add <username> - to add a new owner allowing them to publish content-atom.

But in summary:

  1. Bump the version number in package.json

  2. Make sure you have built the latest version of the JS library with sbt compile

  3. If you've added another type, be sure to add it to js/main.js

  4. Then, npm publish in the same directory as package.json