npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

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.

About

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 🙏

© 2026 – Pkg Stats / Ryan Hefner

allnpm

v0.0.1

Published

Graph generator for entier npm registry

Readme

allnpm

Graph generator of entire npm registry. See actual visualization here: NPM Universe

npm march 2014

Use mouse wheel to zoom in/zoom out.

how to use it?

  1. Download npm metadata using downloadGraph.sh file. If you don't have wget simply save response to byField file. I do not list url directly here, since response is huge (~122MB).
  2. Convert response to graph: node convertToGraph.js byField > graph.out
  3. Run layouter: node layout.js graph.out. This will take you a while. Layouter saves each 60th iteration into a .pos file. NOTE Quad tree has a bug which makes it stuck in infinite loop. See referenced issue for a temporary workaround.
  4. Once you get 100-200 iterations saved (takes approximately 3-4 hours) you can cancel layouter (ctrl + c).
  5. Flatten the graph into data file: node flatten.js byField 100.pos > graph.js

Now graph.js contains information about graph nodes/positions. Each element in the array represents a node:

{"id":"pkgName","pos":{"x":-63,"y":681},"a":"Author","d":[dependency1, dependency2, ...]}

The format is targeted to miminize file size. It could be made even smaller via binary adjacency list. For now I keep it human readable.

license

MIT