How Fork Finder Ranks GitHub Forks

Fork Finder uses a multi-signal scoring algorithm to rank every public fork of a GitHub repository by its health and activity level. Here's exactly how it works.

Data Source

Fork Finder fetches fork data via the GitHub public REST API. No authentication is required for public repositories. Fork data is cached to reduce API usage and improve response times.

Fork Collection Strategy

When you search for a repository, Fork Finder retrieves all public forks. For repositories with thousands of forks, it fetches the most recently pushed forks first, ensuring the most active ones always appear in results.

Scoring Rules

Each fork receives a composite health score based on the following signals:

• Recent push date — forks pushed more recently score higher
• Star count — community interest adds to the score
• Not archived — archived forks receive a penalty
• Open issues — moderate issue activity is a positive signal
• Forks of the fork — if others are forking the fork, it's significant
• Divergence from original — forks with meaningful changes rank higher
• README presence — maintained forks typically have updated documentation

Cache and Refresh Policy

Fork results are cached to provide fast responses. Cache states:

• Fresh — data fetched within the last hour
• Warm — data is 1–24 hours old; still reliable
• Stale — data is older than 24 hours; a background refresh has been triggered

Limitations

Fork Finder cannot access private repositories. Score rankings are based on public signals only and do not guarantee code quality or security. A high score means active maintenance, not necessarily production readiness.