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

@jspm/overrides

v1.0.0

Published

This repo contains the `package.json` overrides used for npm registry packages as processed by `jspm.dev`, `jspm.io` as well as in local package management.

Readme

jspm overrides

This repo contains the package.json overrides used for npm registry packages as processed by jspm.dev, jspm.io as well as in local package management.

Do not send PRs to this repo before reading the instructions below.

Criteria for merging an override

  1. The override should be fully backwards compatible with existing usage of the package.
  2. There should be a link to a PR that was made to the original package repo with the change.
  3. The primary repo PR must be stalled with no responsive discussion or activity.

If there are consensus issues on the primary PR, feel free to post an issue here to seek assistance resolving any conflicts. The override is only the last resort for packages that are either not maintained, or where maintainers are unresponsive or actively refusing to merge the feature.