pm2 npm Security Score: 76/100

npm publisher

Single point of failure

downloads/week

Blast radius if compromised

13.0y

package age

Established package

50 days ago

last release

Active maintenance

GitHub contributors

Many contributors, single publisher

— Provenance Not enabled

— Staged Publishing Not enabled

Risk analysis

pm2 is flagged HIGH risk due to rapid adoption with limited publisher depth. New packages with fast growth are higher-risk targets.

Publisher depth — How many people can push to npm? Single-publisher packages are the #1 structural risk.
Longevity — Older packages have track records. New packages with high adoption are higher risk.
Release consistency — Regular releases signal active oversight. Long gaps mean unpatched vulnerabilities.
Download trend — Growing packages attract more scrutiny (and more attacks).
OpenSSF Scorecard — Process security: branch protection, code review, CI/CD safety.
Build provenance — Published versions linked to specific CI runs via SLSA attestation.
Staged publishing — Human approval gate between npm publish and going live.

You came looking for pm2. Your node_modules has hundreds more. Run one command to score every dependency you ship:

npx proof-of-commitment

Auto-detects your lockfile. Scores every dependency. Zero install.