npm package trust score

to-regex-range

npm · 98M/week · 10.8 years old

70/ 100

WARNING

npm publishers2

Weekly downloads98M

Package age10.8 years

Last published2622d ago

GitHub contributors5

SLSA provenanceNo

Trusted PublishingNo

OpenSSF Scorecard3.0/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

7/15

Trusted Publishing

0/2

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
Trusted Publishing — whether the package uses npm OIDC provenance to publish from CI, eliminating stolen-credential attacks

Track this package

Monitor to-regex-range in CI. Catch risk changes before they reach production.

Track to-regex-range → Compare plans →

Free: 200 audits/day · Paid from Developer ($15/mo): monitoring, batch API, email alerts

Use this data

Audit your full dependency tree Add to your CI pipeline

CLI

npx proof-of-commitment to-regex-range

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/to-regex-range)

REST API

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