01
“The fork already fixed it.”
You’re hitting a bug in a dependency. Someone solved it in a fork eight months ago and never got it merged. forksplorer surfaces the fix — diff, context, cherry-pick command.
fork intelligence · humans + ai agents
GitHub shows you that forks exist. forksplorer shows you what’s in them — a ranked list of real unmerged features from any repo’s fork graph, with AI summaries, diffs, and cherry-pick instructions.
three moments
01
You’re hitting a bug in a dependency. Someone solved it in a fork eight months ago and never got it merged. forksplorer surfaces the fix — diff, context, cherry-pick command.
02
Upstream went quiet. The fork graph knows which fork became the real successor. Supply-chain intelligence your security team can act on.
03
Maintainers: there are unmerged gems sitting in your own fork graph right now. Pull-based discovery — nobody has to spam you with PRs.
Copilot and friends structurally can’t see across the fork trust boundary. forksplorer ships an MCP server from day one, so any AI agent can ask the fork graph directly:
get_fork_features — ranked unmerged features for a repoget_feature_diff — the actual diff, attributed + linkedget_apply_instructions — cherry-pick / patch commandsforksplorer.com/{owner}/{repo} — cached forever, free to browse. We’re scanning the first wave of repos now. Want yours in it, or early API/MCP access?
Join the waitlist →One email when we launch. No spam, no newsletter.