microsoft/graphrag

A modular graph-based Retrieval-Augmented Generation (RAG) system

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 49 minutes ago
Added to GitGenius on August 31st, 2026
Created on March 27th, 2024
Open Issues & Pull Requests: 51 (+0)
GitHub issues: Enabled
Number of forks: 3,774
Total Stargazers: 35,875 (+0)
Total Subscribers: 207 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 days
Mean response time: 51.8 days
90th percentile: 223.6 days
Tracked items: 590

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Work labelled "community_support" is answered fastest, typically in about 9 hours, while "v3" waits about 3 weeks. Only 10% of issues opened in the past year have been closed. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 6
Closed in 7 days: 0
Avg open age: 36 days
Stale 30+ days: 2
Stale 90+ days: 1

Recent activity

Opened in 7 days: 5
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 4

Top labels

  • triage (286)
  • bug (211)
  • enhancement (105)
  • awaiting_response (81)
  • backlog (65)
  • stale (61)
  • autoresolved (55)
  • community_support (30)

Detailed Description

GraphRAG is a modular graph-based Retrieval-Augmented Generation system that extracts structured knowledge from unstructured text using large language models.

The system addresses the challenge of enabling LLMs to reason effectively over private, narrative data by constructing knowledge graph memory structures. It works as a data pipeline and transformation suite that uses LLMs to extract meaningful, structured information from unstructured text, then organizes this into graph-based representations that provide targeted context for question answering.

The tool suits teams working with private document collections who want to improve LLM reasoning over their data. It requires careful consideration of indexing costs, which the documentation emphasizes should be understood before starting. The project recommends prompt tuning to achieve optimal results with your specific data rather than relying on out-of-the-box performance.

The project is in maintenance mode and no longer accepts new pull requests or implements new features. Bug fixes and dependency updates are performed as needed, particularly to address security vulnerabilities. The team maintains active discussion channels for user feedback and conversation.