Snyk's Package Health Score evaluates maintenance, community and security. On its chalk page it shows 83/100, maintenance "Sustainable", and a maintainer count of 1. So Snyk does show the number; its score does not move on it. chalk has one npm publisher behind 631 million downloads a week, and that account was phished in September 2025. (Snyk and npm figures read Nov 5, 2026.)
Catches what's broken
Catches
Misses
Catches what's exposed
Catches
Misses
Chalk is excellent software. The CRITICAL flag isn't about code quality — it's about credential concentration. One stolen npm token, one compromised laptop, one phishing email reaches every project that depends on chalk. That is 631 million installs per week (npm, Nov 5, 2026) behind a single set of credentials.
Five packages. Live Commit data. Snyk scores copied from security.snyk.io on Nov 5, 2026.
Loading live data…
Failed to load data.
No. They measure different things. Snyk tracks known CVEs and gives you fix paths — that's irreplaceable. Commit measures structural exposure: credential concentration, publisher count vs download volume, release patterns. A dependency can have zero CVEs and still be CRITICAL on Commit because one person controls 400M weekly installs. Use both.
Community engagement, maintenance activity, code quality signals, and known CVEs. Snyk's model answers "is this package well-maintained and free of known vulnerabilities?" That's a completely different question from "is this package's publish access concentrated in a way that makes it a high-value target?"
Snyk does list the maintainer count (1) on its chalk page. Its maintenance label is based, in its own words, on "released npm versions cadence, the repository activity, and other data points", and chalk passes that. What it does not do is treat one account behind 631M weekly installs as a risk on its own. That's a difference in scope, not a flaw.
The CLI, web audit, and API are free. Paid plans from $15–$29/mo add batch scanning, continuous monitoring, Slack/webhook alerts, and GitHub Action integration. See pricing →
Paste your dependencies. See which ones are structurally exposed.
npx proof-of-commitment --file package.json