npm package trust score

bytes

npm · 100M/week · 13.9 years old

71/ 100

WARNING

npm publishers2

Weekly downloads100M

Package age13.9 years

Last published1567d ago

GitHub contributors18

ProvenanceNo

OpenSSF Scorecard2.8/10

GradeB

Risk flags

WARN: no release in 12+ months

Score breakdown

Five behavioral dimensions. Each measured from public registry data, not self-reported.

Longevity

25/25

Download momentum

22/25

Release consistency

9/20

Publisher depth

7/15

GitHub backing

8/15

What this score measures

The Commit trust score measures behavioral commitment — signals that are hard to fake. Unlike stars, READMEs, or download counts, these signals capture how a package is actually maintained.

Longevity — how long the package has been published and actively maintained
Publisher depth — number of people with npm publish access (distinct from GitHub contributors)
Release consistency — regular releases signal active oversight
Download trend — growing, stable, or declining adoption
GitHub backing — contributor depth and OpenSSF Scorecard process security

Use this data

Audit your full dependency tree Add to your CI pipeline

CLI

npx proof-of-commitment bytes

MCP (Claude, Cursor, Windsurf)

{ "mcpServers": { "commit": { "type": "streamable-http", "url": "https://poc-backend.amdal-dev.workers.dev/mcp" } } }

README badge

![Commit Trust](https://poc-backend.amdal-dev.workers.dev/badge/npm/bytes)

REST API

curl -X POST https://poc-backend.amdal-dev.workers.dev/api/audit -H "Content-Type: application/json" -d '{"packages":["bytes"]}'