Discofork
Repository brief

microsoft/graphrag

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:48:36.739Z
1mo ago

microsoft/graphrag

GraphRAG is a large, active Microsoft open source Python repository for a modular graph-based Retrieval-Augmented Generation system. It is aimed at turning unstructured text into structured data for LLM workflows, with strong documentation and a release-driven project history. With 31,865 stars and 3,356 forks, it is a well-established upstream to compare forks against.

GitHub
Loading tags...
Stars31,865
Forks3,356
Default branchmain
Last pushed2026-03-30T13:47:27Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer this fork if your goal is a server-first GraphRAG deployment with API compatibility and local-model support. Prefer upstream if you want active maintenance, broad documentation, and the least risky path for long-term adoption.

Choose this fork if your priority is broader LLM-provider compatibility and more pragmatic example workflows, especially for Chinese ecosystem models. Choose upstream if you want the fastest-moving, better-maintained base with newer fixes and release cadence.

Choose this fork if you want a .NET-native GraphRAG variant and can tolerate losing some upstream Python workflow compatibility. Stick with upstream if you need the original Python CLI, notebooks, and fastest access to Microsoft’s latest fixes.

Prefer upstream unless you specifically need the fork's custom parsing, local search tuning, or visualization/demo additions. This fork looks useful as an experiment or reference implementation, but it is too stale and diverged for low-risk adoption.

Prefer upstream unless you specifically need this mirror. This fork does not show meaningful product additions, and it is already slightly behind upstream, so it offers little adoption advantage beyond being a close copy.

Choose this fork only if its Tongyi Qianwen/provider-specific changes are the reason you need it. For most adopters, upstream microsoft/graphrag is the better base because it is far more current, actively maintained, and likely to be easier to support.

Choose this fork only if its local test, workflow, or data customizations are specifically valuable to you. If you want current GraphRAG features, fixes, and documentation, upstream is the better default because this fork is materially stale and diverged.

Prefer this fork only if its specific tuning choices match your use case and you are comfortable owning an aging, highly divergent codebase. For most adopters, upstream GraphRAG is the safer choice because this fork is stale and materially behind on fixes and releases.

Prefer upstream unless you specifically need this fork's prompt-tuning/autotemplating changes or want to build on an older snapshot. For most adopters, the fork is too stale and too far behind current GraphRAG maintenance to be the safer default.

This fork looks like an inactive mirror rather than a differentiated downstream product. Prefer upstream unless you specifically need a frozen 2025-era snapshot to build from or reproduce against.