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

contributin

v1.0.2

Published

Public GitHub contributing made easy

Readme

Contributing

Public GitHub contributing made easy

Mission

After trying out the Open Sourcing workflow provided by GitHub, I found it to be very one sided. While an individual might have an excellent improvement to make to an existing repository, it is at the initial creator(s) (or current maintainer(s)) discretion as to whether or not that change will make it to the repo. Open Source should be driven by the community, and as such Contributin allows anyone to be added as a collaborator to a repository, given them the ability to merge.

What you get

  • A landing page you can point users to fill in their GitHub username and receive an invite through the GitHub Api (https://contribute.yourdomain.com)
  • A SVG badge that works well from static mediums (like GitHub README pages) [https://contribute.yourdomain.com/badge.svg]

Setup

Deploy to Heroku

Deploy

Deploy yourself

$ npm install -g contributin
$ REPO_NAME="<repo_owner>/<repo_name>" GITHUB_API_TOKEN=<github token> contributin

Contributing

Join the repo at: Contributin

Running Locally

Once you've cloned the repo, you can run contributin locally through

$ gulp
$ REPO_NAME="<repo_owner>/<repo_name>" GITHUB_API_TOKEN=<github token> bin/contributin

Credits

  • @rauchg for the idea to use a heroku deployable service to grant access using a single click. Checkout slackin for more information.

License

MIT