// trust meter v1 · v2

Trust Meter methodology

The Trust Meter measures, from 0 to 10, the risk of using a project. Each component is scored out of 10; the details of each score are shown on the profile.

Components and weights

ComponentWeightComputation
Security35%10 minus a penalty per open vulnerability on the latest release (minimum 0).
Supply chain20%10 minus 1 per dependency with an open vulnerability (minimum 0). Absent without a dependency graph.
Maintenance20%Share of signals present: push within 90 days, release within 180 days, at least 2 people make 80% of commits, CVEs fixed within 30 days (when known).
Provenance15%OpenSSF Scorecard when available; otherwise share of signals: older than a year, not archived, owned by an organization, license detected.
Quality and performance10%Build, tests and performance measurements in our isolated environment (coming soon).

A component without data is not counted: the other weights are scaled back to 100%. The score is rounded to a tenth.

Security penalties

Method v2 (after our scan)

Once a scan of the repository is done, method v2 applies: same components and weights, plus the results of our tools. A project never scanned keeps method v1.

Sources

GitHub API (metadata, releases, contributors, dependency graph), OpenSSF Scorecard, and our local copy of the OSV, CVE List V5, NVD, CISA KEV and FIRST EPSS databases, updated daily.