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 🙏

© 2024 – Pkg Stats / Ryan Hefner

contributor-count

v1.0.2

Published

Count the number of people with write access to a package

Downloads

5

Readme

NPM Contributor Count

This is a tool that counts the number of people who have access to a project on npm, either directly or indirectly. Every single module you import, or any module that those modules import (and so on), can put your project at risk so it is important to understand the exposure you are receiving when you add an npm package as a dependency to your project. I've writte a bit about this here.

Usage

To test all of the dependencies for the package in your local directory:

> npx contributor-count
local package has 19 contributors with access to the project or its dependencies
>

To test all of the dependencies for a given package on npm:

> npx contributor-count express
express has 106 contributors with access to the project or its dependencies
>

You can also use it as a library:

const count = require('contributor-count')

const name = 'express'
const version = 'latest'
const target = { name, version }

count(target)
.then(count => console.log('The count is', count))
.catch(err => console.error('Failed to get count', err))

Technical Notes

This counter does not consider packages which reference off-npm sources, such as a direct git repository or a tar file since it's not clear how to quantify the number of people with access to these reliably.

This counter only considers the number of people with direct npm publish rights for the package or one of its dependencies. It does not consider the possibility of a vulnerability being introduced through a packages repository or CI system.

This counter only considers dependencies which are required for usage and does not include unlisted dependencies, peer dependencies, or developer dependencies.