Which of My npm Dependencies Have Only One Maintainer? A Free Way to Check
One command per package with npm, or one command per lockfile with a free CLI.
To find which of your npm dependencies have only one maintainer, you can run npm view <pkg> maintainers on each package, or run a free scanner over the whole lockfile in one go: npx proof-of-commitment --file package-lock.json (Commit, which we build) prints the number of publishers for every package and flags widely used packages that depend on a single account.
The manual way
npm view chalk maintainers This is fine for five packages. A real project has hundreds of transitive dependencies, and the risky ones are usually the ones you never installed on purpose.
The whole-lockfile way
npx proof-of-commitment <package> [<package> ...]
npx proof-of-commitment --file package-lock.json It also reads pnpm-lock.yaml, yarn.lock and plain package.json. Each row shows the publisher count, weekly downloads, age and whether the package ships npm provenance. Packages with heavy downloads and concentrated publish access are marked CRITICAL.
Why one maintainer matters, and why it is not the whole story
One account with publish rights means one password, one token, one person who can be phished. That is the path behind most account-takeover attacks on npm. But a count of npm maintainers is not the same as the number of people who actually publish, and a package with three listed maintainers can still have one person doing every release. Commit reads who actually published each version (the _npmUser field in the registry metadata) and separates active publishers from dormant ones, so its count can differ from npm view.
Other free places to look: deps.dev shows OpenSSF Scorecard results, including contributor and maintenance checks, and the LFX Insights health score covers larger projects. Neither works off your lockfile directly.
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.