Finding an active, maintained fork of a GitHub repository used to require manually browsing through hundreds of forks sorted by creation date. Fork Finder automates this by fetching all public forks and ranking them by real activity signals.
Why GitHub's Default Fork List Is Not Enough
GitHub sorts forks by creation date or star count, not by recent activity. A fork created 5 years ago with the most stars may have been abandoned for 3 years. Fork Finder ranks forks by commit recency, push activity, star trajectory, open issues, and health signals.
Paste a GitHub repository URL (e.g., https://github.com/owner/repo) or type an owner/repo slug
Fork Finder fetches all public forks via the GitHub API
Forks are ranked by a composite health score: recent pushes, star count, open/closed issue ratio, and archival status
Review the ranked list and click through to the most active forks
What Signals Indicate an Active Fork?
Recent commits — forks with pushes in the last 30–90 days
Stars and watchers — community interest signals
Open issues being resolved — maintainer responsiveness
Not archived — the fork owner has not abandoned it
Divergence from original — meaningful changes beyond the source
When Should You Look for a Fork?
Consider searching for active forks when: the original repo hasn't had commits in 6+ months, security vulnerabilities are unpatched, your issues go unanswered, or the project is explicitly archived.