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

npm-to-hypercore

v3.0.2

Published

Stream all of npm metadata into hypercore

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

watsonwatson

Keywords

Readme

npm-to-hypercore

A simple data fetcher that streams all changes made to npm and stores them in Hypercore. The changes are stored such that each version of a package that's released is one block in Hypercore.

Build status js-standard-style

Installation

npm install npm-to-hypercore -g

Usage

npm-to-hypercore [db]

Just run the npm-to-hypercore command. Takes an optional db argument to use as the path to the database.

Try it out

We have an instance of this running already. You can replicate data from it by using this hypercore key

f5d045813912dadbff4bdc8a43bb78da6685f965f1a88e430db49c793a5a1a01

To test it out you can use hypertail

hypertail /tmp/npm-to-hypercore f5d045813912dadbff4bdc8a43bb78da6685f965f1a88e430db49c793a5a1a01

License

MIT