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

ipvl

v0.0.3

Published

ipfs-versioned-file-log cli

Readme

ipvl cli

You can use this command-line-interface to publish different versions of a folder to IPFS and store these versions to a hypercore feed.

A package.json with the fields name, description and author is required.

You can use an .ipvlignore file to ignore files (following the same rules, as .gitignore files). Otherwise ipvl will look for a .gitignore file and use that if one exists. If there is neither an .ipvlignore or .gitignore all data will be copied.

commands

ipvl publish [options] <path> <version>

This will create a .ipvl folder in your given path. All files not specified in a .ipvlignore or .gitignore file will be copied to .ipvl/data/<version> and published to IPFS. The version, together with metadata from package.json and the IPFS-CID will be written to the hypercore feed located at .ipvl/data/log.

You can use --force to overwrite an existing .ipvl folder.

ipvl update <path> <version>

Use publish for your initial push to IPFS, and update for all further versions.

feed

A feed entry will look like this:

{
  "type":"update",
  "value":{
    "name":"my data name",
    "description":"my description",
    "author":"what people call me",
    "version":"0.0.1",
    "location": {
      "locationIdentifier":"an IPFS CID",
      "storageType":"ipfs"
      }
  }
}