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

gittrition

v1.3.0

Published

Gittrition: Developer Attrition Statistics from Git History

Downloads

11

Readme

Gittrition: Developer Attrition Statistics from Git History

How to use:

  1. cd to the root of the repo for which you'd like to run attrition statistics
  2. run npx gittrition
  3. You will be prompted to answer y/n for whether each developer is still at the company. The list of developers will be in descending order of number commits to the repo. In other words, the biggest contributors will be earlier in the list.
  4. answer the y/n prompts asking about each contributor to the project
  5. at any time, you can type 'exit' to get stats based on just the answers you've given so far. This can be good when you have a few key people who've made most of the commits, and many people with a small number of commits.

If you type 'exit' at any time, the output will show results, separately for:

  1. just the developers you answered for
  2. the whole list of developers