Open data

The health formula (v1)

Health is an integer from 0 to 100, the sum of five terms. Changing it is a versioned event and will be noted on this page, because a ranking you cannot audit is not worth trusting.

health = 35 × min(1, commits_90d / 30)
       + 25 × releaseRecency
       + 20 × min(1, log10(stars + 1) / 5)
       + 10 × (archived ? 0 : 1)
       + 10 × (has_docker ? 1 : 0)

releaseRecency = 1                      if latest release ≤ 180 days old
                 (720 − days) / 540     if 180 < days < 720
                 0                      if ≥ 720 days or no release

• 35 Commit activity

  35 × min(1, commits in last 90 days / 30). A project with 30 or more commits in 90 days scores the full 35 points.

• 25 Release recency

  25 × release recency: full marks if the latest release is 180 days old or newer, falling linearly to zero at 720 days. No tagged release scores zero.

• 20 Stars

  20 × min(1, log₁₀(stars + 1) / 5). Logarithmic, so 100,000 stars is worth roughly twice 300 stars, not 300 times as much.

• 10 Not archived

  10 points if the repository is not archived, 0 if it is.

• 10 Docker support

  10 points if the project publishes a Docker image or Compose file, the clearest signal that self-hosting is supported.

Labels

Good is 70 or above (754 tools), Slowing is 40 to 69 (302), and Stale is below 40 (290). The mean score across the catalogue is 66.4.

What the score does not mean

• It is not a quality or security judgement. A finished, stable tool can score low simply because it needs few commits.
• It favours projects that develop on GitHub. A mature project hosted on a self-run Forgejo instance has no measurable counters here, so it may be unscored.
• Stars measure attention, not merit, which is why they are capped at 20 points and logarithmic.
• Docker support is a proxy for "self-hosting is a supported path", not for code quality.

Sources and licences

Coverage