OpenSSF Scorecard evaluates whether a project follows secure development practices — branch protection, CI/CD, signed releases, fuzzing. It's the best tool for measuring process security. It doesn't measure who controls the npm publish token or what happens if they're compromised.
Measures process security
Catches
Misses
Measures structural risk
Catches
Misses
esbuild is a model of disciplined open source: single author, rigorous engineering, excellent documentation. Scorecard gives it a middling 5.0, mostly because one author merges nearly every change without review. Commit flags it CRITICAL for a related reason it reads from npm.
The CRITICAL flag isn't a judgment on Evan Wallace's engineering discipline. It measures structure. Releases now ship from GitHub Actions with SLSA provenance, which proves where a build came from, not who approved it. One maintainer account on npm, and one person merging into the repo that publishes, sit behind 409 million weekly installs. Scorecard can see the review gap in the repo. It can't see who holds the registry account.
Sources, re-read Nov 6, 2026: Scorecard API for evanw/esbuild (scan dated Oct 19, 2026); npm registry metadata for esbuild@0.28.2; Commit audit API.
Scorecard runs against GitHub and GitLab repositories. Its --npm flag only looks up the repo; the checks are the same. If a package has no linked repo, there is nothing to score. Commit scores from registry metadata: publisher count, release history, download trends. Where Scorecard has a result, Commit's API returns it as scorecardScore next to its own score.
A package can have exemplary Scorecard results — branch protection, signed commits, SLSA Level 2 — and still have a single person controlling the npm publish token for 400M weekly downloads. Scorecard doesn't measure that. Commit does. It is a measure of exposure, not a forecast: we have not shown that it predicts which packages get attacked.
Five packages. Scorecard scores shown where available. Commit: live behavioral risk data.
Loading live Commit data…
Failed to load data.
No. Scorecard measures process. The Red Hat / Miasma attack (Jun 1, 2026) had valid SLSA provenance on every malicious version — Scorecard would have rated those packages highly throughout the attack. Process integrity is necessary but not sufficient. Structural concentration is a separate risk axis that Scorecard doesn't cover.
No. They measure orthogonal things. Scorecard tells you whether a project enforces code review, uses signed commits, and has CI configured. Commit tells you how many people control the publish credentials and whether that's proportionate to the download volume. A complete supply chain security posture needs both: Scorecard for process integrity, Commit for structural exposure.
It's not in scope. Scorecard was designed to measure repository security practices — things a project team controls. Publisher concentration is an ecosystem-level observation: how many people have the credentials to push to npm, and does that number make sense relative to the install volume? Scorecard answers "does this project have good security hygiene?" Commit answers "is this package's attack surface proportionate to its blast radius?"
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 →
Scorecard checks the repo. Commit checks who can publish to the registry. Run both.
npx proof-of-commitment --file package.json