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 🙏

© 2024 – Pkg Stats / Ryan Hefner




Greater Goods Style Guide




This is a fork of Happiness, which in turn is a fork of Standard.


Install globally:

$ npm install ggstyle -g

After you've done that you should be able to use the ggstyle program. The simplest use case would be checking the style of all TypeScript or JavaScript files in the current working directory:

$ ggstyle
Error: Use Greater Goods Style
  lib/torrent.js:950:11: Expected '===' and instead saw '=='.

You can optionally pass in a directory (or directories) using the glob pattern. Be sure to quote paths containing glob patterns so that they are expanded by standard instead of your shell:

$ ggstyle "src/util/**/*.js" "test/**/*.js"

To disable the linter on a certain file or line, or disable a specific rule, refer to this guide

Making Changes

Clone down the project and install packages:

$ git clone
$ cd gg_styleGuide
$ npm install

Make changes and commit, then update the version and publish:

$ npm adduser
Username: <dev_gg>
Password: < >
Email: (this IS public) <[email protected]>
Logged in as dev_gg on
$ npm version <patch> <minor> <major>
$ npm publish

Some changes may require you to alter gg-standard-engine instead, such as what file types the linter checks.