01
“The fork already fixedit.”
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
What’s living in the forks?
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.
forksplorer.com/jqlang/jqlive scan · 2026-09-14
▲ scanned jqlang/jq — 1,841 forks · 39 inspected · 6 features surfaced $
51cd8da Update AOSP file to include '.render' — MichaelBiegluk 0dcb5d3 Create Render.yml — MichaelBiegluk df6eab5 Create webpack.js — MichaelBiegluk b4e2a61 Create Setup-Java-JDK.jdk — MichaelBiegluk 541755a Update AUTHORS — MichaelBiegluk $ git cherry-pick 541755a^..51cd8da → view fork on GitHub
three moments
02
“Your dependency is dead — here’s the living successor.”
Upstream went quiet. The fork graph knows which fork became the real successor. Supply-chain intelligence your security team can act on.
03
“Someone improved yourproject and never told you.”
Maintainers: there are unmerged gems sitting in your own fork graph right now. Pull-based discovery — nobody has to spam you with PRs.
Built for agents as much as humans.
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 commandsEvery repo gets a page.
forksplorer.com/repo/{owner}/{repo} — cached forever, free to browse. First wave is live — see jqlang/jq. Want yours in it, or early API/MCP access?
Join the waitlist →One email when we launch. No spam, no newsletter.