Discofork
Repository brief

run-llama/llama_index

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-30T12:02:17.689Z
3mo ago

run-llama/llama_index

LlamaIndex is a large, actively maintained Python OSS repository for building document agents and OCR-related tooling. It has strong community adoption (48,139 stars, 7,119 forks) and very recent activity on the default `main` branch. The project is organized as a multi-package monorepo with a core library plus CLI, integrations, packs, finetuning, instrumentation, experimental, utils, datasets, and docs components.

GitHub
Loading tags...
Stars48,139
Forks7,119
Default branchmain
Last pushed2026-03-30T10:46:10Z
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

8 of 8 fork briefs
Selected

Choose this fork if its added integrations and workflows match your stack and you value those features more than staying close to upstream. Choose upstream if you want the most current maintenance stream, smallest integration risk, and easier long-term upgrades.

Prefer this fork only if you need its older tool-calling/doc-oriented snapshot or want a frozen experimental baseline. If you want current features, active maintenance, or low upgrade risk, upstream is the better choice.

Prefer this fork only if you need the older, simpler codebase or its early ingestion tweaks. For new work, upstream is the safer choice because this fork is stale and materially behind.

Prefer this fork if you need its added server, local-model, or backend-specific capabilities and are willing to own upgrade work. Prefer upstream if you want active maintenance, current fixes, and the broadest compatibility.

Choose this fork only if you need the older codebase or its legacy examples; choose upstream if you want an actively maintained, current LlamaIndex with newer integrations and ongoing fixes.

Prefer this fork only if you need its specific local fixes or a curated snapshot. If you want the full upstream integration surface and lower maintenance burden, upstream is the safer choice.

Prefer this fork only if you need a pinned, already-customized baseline and can accept missing newer upstream work. If you want current LlamaIndex capability or active maintenance, upstream is the better choice.

Prefer this fork only if you need its frozen, customized snapshot and are willing to own long-term maintenance. If you want current LlamaIndex capabilities or easier upgrades, upstream is the better default.

run-llama/llama_index · Discofork