AI Comparisons Includes our measurements

Which RAG Frameworks and Vector Databases Are Still Maintained? We Checked 14 GitHub Repos (October 2026)

Server racks and network cables, representing the infrastructure behind RAG retrieval

Most “best RAG framework” lists still rank tools by features and GitHub stars. When I compared a year of commit history instead, three things stood out that those lists miss: LlamaIndex’s open-source framework is now a side project for its company, Microsoft’s GraphRAG is in maintenance mode, and Weaviate has started putting some new features under a separate enterprise licence. None of that makes them bad choices, but it should change how you pick a tool you’ll depend on for years.

Live tracker: the numbers in this article are a snapshot from 15 October 2026. For the current status of these projects, and more than 100 open-source AI tools in total, each with a 0 to 100 health score, see the AI Tool Health Index, which refreshes from GitHub automatically. Four of these are also compared side by side: LangChain vs LlamaIndex and Qdrant vs Milvus. Two differences to expect: the tracker counts every commit, including merge commits, so projects that merge pull requests that way (Weaviate and LightRAG, for example) show higher numbers there than in the table below; and for Qdrant the tracker follows the dev branch, where day-to-day work happens, while this article counted the default master branch.

I haven’t built a RAG system with any of these tools. My own “chat with my documents” setup is just files uploaded to Claude Projects. So instead of ranking them by my taste, I looked at who is still working on each one.

Retrieval-augmented generation (RAG) stacks usually have two parts: a framework that handles loading, chunking, retrieval and prompting, and a vector database that stores embeddings. Both are long-term dependencies. So instead of repeating feature lists, I looked at the evidence of who’s still investing in each project.

How This Was Measured

Method: on 15 October 2026 we cloned the public GitHub repositories of 14 RAG frameworks and vector databases and compared two identical 91-day windows: 17 July to 15 October 2025, and 17 July to 15 October 2026. For each window we counted commits on the default branch (excluding merge commits), distinct commit-author email addresses (excluding bots such as dependabot and project release bots), and, for 2026, commits that credit an AI coding tool as co-author. We also read each repository’s licence file and README. The counting scripts were written and run with AI assistance in a cloud sandbox and the key findings were checked by hand. We did not install or benchmark any of these tools.

Commit counts are a rough signal. Projects that squash pull requests into one commit look smaller than projects that keep every commit, and a busy repository can still be the wrong tool for you. Treat big changes in direction, and what a project says about itself, as the useful part.

The Results

ProjectTypeCommits 2025 → 2026Authors 2025 → 2026Last commitLicence
LlamaIndexFramework362 → 105141 → 5714 Oct 2026MIT
LangChainFramework739 → 552141 → 5715 Oct 2026MIT
HaystackFramework135 → 74424 → 13115 Oct 2026Apache 2.0
RAGFlowRAG engine669 → 2,70993 → 24415 Oct 2026Apache 2.0
LightRAGGraph RAG828 → 1,47635 → 6414 Oct 2026MIT
GraphRAG (Microsoft)Graph RAG22 → 235 → 38 Oct 2026MIT
DSPyFramework160 → 18541 → 4515 Oct 2026MIT
txtaiFramework49 → 2241 → 6115 Oct 2026Apache 2.0
ChromaVector DB318 → 12022 → 1013 Oct 2026Apache 2.0
QdrantVector DB284 → 97021 → 555 Oct 2026*Apache 2.0
MilvusVector DB544 → 64456 → 6115 Oct 2026Apache 2.0
WeaviateVector DB832 → 2,53335 → 3415 Oct 2026BSD-3 plus Weaviate License (see below)
LanceDBVector DB150 → 46829 → 5815 Oct 2026Apache 2.0
pgvectorPostgres extension32 → 1183 → 41 Oct 2026PostgreSQL License

* Qdrant’s default branch, master, is updated at releases; day-to-day work happens on a dev branch, whose latest commit was on 15 October 2026. Haystack’s 2026 figure includes 339 commits from its release bot and dependabot; counting only human-authored commits, it went from 121 to 405.

Commits, a year apart

Non-merge commits on each default branch, 17 Jul to 15 Oct, 2025 vs 2026 (log scale)

20252026Right: change
Haystack135 → 744+451%
txtai49 → 224+357%
RAGFlow669 → 2,709+305%
pgvector32 → 118+269%
Qdrant284 → 970+242%
LanceDB150 → 468+212%
Weaviate832 → 2,533+204%
LightRAG828 → 1,476+78%
Milvus544 → 644+18%
DSPy160 → 185+16%
GraphRAG22 → 23+5%
LangChain739 → 552−25%
Chroma318 → 120−62%
LlamaIndex362 → 105−71%
1101001k10k

Source: EvalAITools analysis of public GitHub history, cloned 15 October 2026.

Three Projects That Changed Course

LlamaIndex: the company’s focus has moved

Commits fell 71% year on year and the number of authors fell 60%. The README explains why, in the company’s own words: its “primary focus has shifted towards LlamaParse”, its document-parsing platform, and the open-source framework is still available “as an open toolkit that you’re welcome to use”. Recent commits are mostly upkeep, such as adding support for new models like Claude Haiku 5.5 and GPT-6.1 Sol. The repository also has a stale-package policy: integrations that score poorly on tests, downloads and commit activity are moved to a separate stale_packages branch, though they stay on PyPI.

What I’d do: existing LlamaIndex apps don’t need to panic. For a new project, check that every integration you plan to use is still on the main branch, and expect slower feature work.

Microsoft GraphRAG: maintenance mode

The README now says the project “is largely in maintenance mode, and won’t be accepting new PRs or implementing new features”, with bug fixes and dependency updates, especially for security issues, as needed. Activity matches: 23 commits from 3 authors in the 2026 window.

What I’d do: GraphRAG is still useful for studying graph-based retrieval, but I wouldn’t start a new production system on it. LightRAG, a graph RAG project that nearly doubled its commits, is the obvious open-source alternative to evaluate.

Weaviate: a new enterprise-licensed folder

On 26 August 2026 Weaviate added a wl directory to its repository under a separate licence. The LICENSE file now says code outside that directory is BSD-3-Clause, while code inside it is “only available under a separate enterprise license”, with the features “enabled via license key”. When we checked, the folder held 21 files covering backup deduplication, database-user expiry, namespaces and a self-recovery system. The core database is still open source, but some newer operational features are not.

What I’d do: if you self-host Weaviate, check whether any feature you need lives under wl/ before you upgrade or plan around it.

Projects That Grew

  • RAGFlow quadrupled its commits and went from 93 to 244 authors, the busiest project in this group.
  • Haystack more than tripled its human-authored commits and went from 24 to 131 authors.
  • txtai went from a single author to 61, as outside contributors joined its long-time maintainer.
  • Qdrant and LanceDB both more than tripled their commits and roughly doubled their authors.
  • pgvector nearly quadrupled its commits, but it’s still a very small team (4 authors), which is worth knowing if your whole stack sits on it.

Chroma is the one I’d watch: still active, with a commit on 13 October, but its commits fell 62% and its authors halved.

How Much Is AI-Assisted?

We also counted 2026 commits that credit an AI coding tool, usually through a “Co-authored-by” line, or are authored directly by one.

ProjectAI-credited commits (2026 window)Share
LightRAG875 of 1,47659%
DSPy96 of 18552%
Qdrant387 of 97040%
Milvus247 of 64438%
GraphRAG6 of 2326%
Chroma26 of 12022%
Weaviate487 of 2,53319%
LanceDB72 of 46815%
Haystack112 of 74415%
RAGFlow47 of 2,7092%
LangChain2 of 552under 1%
LlamaIndex1 of 1051%
txtai, pgvector00%

Claude was the most commonly credited tool, followed by Cursor (mostly in Qdrant), Amp (mostly in DSPy) and OpenAI’s Codex (mostly in Milvus). Disclosure: Anthropic makes Claude, which also helped with this analysis. A low number doesn’t prove a project avoids AI tools; many developers use them without adding a trailer. It mainly tells you about each project’s conventions.

What I’d Choose for a New RAG Project

If you need…ConsiderCheck first
A general RAG frameworkHaystack, LangChain, DSPyLangChain’s author count fell sharply; read its current docs before relying on older tutorials
A full RAG app with a UIRAGFlowIts pace of change means frequent upgrades
Graph-based retrievalLightRAGAvoid starting new work on GraphRAG
Vectors inside an existing PostgrespgvectorSmall team; keep an upgrade plan
A dedicated vector databaseQdrant, Milvus, LanceDBWeaviate: whether your features sit in the enterprise-licensed folder
An existing LlamaIndex appKeep itThat your integrations haven’t moved to the stale branch

Whatever you pick, test retrieval quality on your own documents. My small hybrid search experiment found that the retriever choice mattered less than how documents were cleaned and split.

FAQ

Is LlamaIndex dead?

No. It had 105 commits from 57 authors in the 91 days to 15 October 2026 and still adds support for new models. But commits fell 71% year on year, and the README says the company’s main focus is now LlamaParse.

Is Microsoft GraphRAG still maintained?

Only for bug fixes and dependency or security updates. Its README says it’s largely in maintenance mode and won’t accept new pull requests or features.

Is Weaviate still open source?

Mostly. Code outside the wl directory is BSD-3-Clause; code inside it, added from 26 August 2026, needs a separate enterprise licence and a licence key.

Which vector database is the most active?

By raw commits in our window, Weaviate, then Qdrant and Milvus. By number of contributors, Milvus, LanceDB and Qdrant were close, at 55 to 61 authors each.

Related: Which AI agent frameworks are still maintained · Does hybrid search help RAG? Our test · System 1 vs System 2 AI agents

Sources

Published October 15, 2026. Last updated October 17, 2026. How we work

Leave a comment

Your email address will not be published. Required fields are marked *