oss-popularityscopedweight 0.7adapter 6 of 17

Open-Source Traction.

The OSS Popularity adapter reads public repository and package metrics for open-source subjects. Popularity is not proof of quality, so it carries a below-standard weight — but sustained traction from independent developers is meaningful corroboration that a project is real and maintained.

Counts only inside its own registry or ecosystem.

What it measures.

Stars and forks

GitHub stars and forks over the trailing window.

Contributors

Count of independent contributors to the repository.

Package downloads

Downloads of published packages.

Component keys.

oss-popularity.*

Component family covering repository and package traction.

When it counts.

Scoped — counts for subjects with public repositories or published packages.

When signals are missing.

Closed-source subjects simply omit this component.

How it contributes.

{
  "component": "oss-popularity.*",
  "scale": "0-100",
  "mode": "scoped",
  "weight": 0.7,
  "contribution": "component x 0.7 / total weight"
}

The adapter’s components are averaged into the composite as a weighted mean: every contributing adapter’s component is multiplied by its weight, summed, and divided by the total weight of contributing adapters. The result is published as trustScores.total with a config version and timestamp so anyone can recompute it.

Questions about Open-Source Traction.

Why does open-source popularity have weight 0.7?

Stars and downloads are popularity, not proven trust, so the informative catalog weights this adapter below the standard to keep it corroboration rather than a headline driver.

Which metrics does the OSS Popularity adapter use?

GitHub stars, forks, contributor count, and package downloads over a trailing window, normalized into the oss-popularity.* component family.

← Browse all 17 adapters