What Is the Bus Factor of an npm Package, and How Do You Check It?
Two numbers: who writes the code, and who can ship it to npm.
The bus factor of an npm package is the number of people who would have to disappear before nobody can maintain or release it. You check it with two numbers: how many people actively commit to the source repository (GitHub contributors over the last year), and how many accounts can publish to npm (npm view <pkg> maintainers). For supply chain risk the second number matters more, because that is who can push code to your machine.
Check the code side
Open the repository’s contributor graph, or look up the package on deps.dev, which shows OpenSSF Scorecard results. The Scorecard checks include Maintained and Contributors.
Check the publish side
npm view is-number maintainers Many packages with dozens of contributors are released by one or two people. A large community does not spread the publish risk if the npm token sits with one account.
Both at once
Commit (our tool) puts the two side by side for every package in a lockfile and says when they diverge:
npx proof-of-commitment <package> [<package> ...]
npx proof-of-commitment --file package-lock.json On chalk today it printed “30+ GitHub contributors — publish-access concentration risk despite active community”. That gap, many writers and few publishers, is the bus factor that matters for security.
What a low bus factor does not mean
A package with one maintainer is not unsafe by default. Plenty of small, stable utilities are written and released by one careful person. The number tells you where to look, and whether to pin versions or watch for new releases.
Commit is our tool, so weigh what this page says about it accordingly. The commands and behaviour here were run on November 4, 2026; registry data changes, so re-run them rather than trusting a number on this page.