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




The CLI you need to work with Stellate from your CLI. See for the complete documentation.




Stellate CLI

The CLI you need to work with Stellate from your CLI. See for the complete documentation.


login    Authenticate the CLI
init     Setup a new Stellate service
pull     Pull the latest gateway config to the local stellate config file
ls       List all apps
push     Push the latest changes from stellate config file
check    Check for breaking changes to your schema (BETA)
serve    Use your local backend with Stellate’s GraphQL Edge Cache (BETA)
subset   Prints the subset of your schema according to the configured schema view (BETA)

every one of these can be suffixed with --help for additional information.


The CLI will handle authentication automatically when necessary by opening a browser tab to create a API token. This token will be stored in the ~/.stellate folder.


To install our dependencies



To build the output

yarn build

Use the CLI locally

Building the CLI will create a file in build/index.js, you can run that file in Node.js to use the CLI:

node ./build/index.js

For a more convenient usage you can also link the package by running npm link. This should make the stellate command available in your shell.


By default the CLI will interact with the production API. You can set an environment variable to point the CLI at different endpoints:

  • STELLATE_ENDPOINT=staging will point the CLI at the staging API
  • STELLATE_ENDPOINT=local will point the CLI at the local API running at http://localhost:3001

The CLI will create different tokens for different environments. The files in the ~/.stellate folder are prefixed with the value of STELLATE_ENDPOINT in order to persist multiple tokens at the same time.