Our take
Inactiveno commits in over a year- Activity
- 20
- Community
- 41
- Issues
- 21
- Pull requests
- 21
+3 stars in the last 15 days
RAGChecker offers useful, component-level RAG diagnostics, but its inactive maintenance status is a meaningful adoption risk.
Good fit if
- You need claim-level metrics to investigate retriever and generator behavior in an existing RAG pipeline.
- Your team can configure the extractor and checker models and is comfortable with a Python evaluation workflow.
- You can assess the Apache-2.0 license for your intended use.
Look elsewhere if
- You require a project with recent commits, releases, or visible ongoing issue handling.
- You need a turnkey evaluator that does not require setting up extractor and checker models.
- Your workflow depends on a documented test suite, which the repository metadata does not indicate.
All health signals
| Last commit | 2024-12-13 (1.8 years ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 0 (latest v0.1.9, 2024-09-25) |
| Contributors | 6 (top contributor: 63% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 2 years |
Checked on 2026-10-17 with the GitHub API.
Overview
RAGChecker is a Python framework for assessing and diagnosing Retrieval-Augmented Generation (RAG) systems. It uses claim-level entailment to evaluate generated answers against retrieved context and ground-truth answers, helping teams identify whether weaknesses come from retrieval or generation rather than relying on a single overall score.
The project is aimed at developers and researchers who already have RAG outputs to evaluate. It accepts queries, ground-truth answers, generated responses, and retrieved context, then runs configurable extractor and checker models to produce diagnostic metrics. It also integrates with LlamaIndex.
Key Features
- Reports overall precision, recall, and F1 metrics for a RAG pipeline.
- Provides retriever metrics, including claim recall and context precision.
- Provides generator metrics such as faithfulness, hallucination, context utilization, and noise sensitivity.
- Uses claim-level entailment checks for more granular evaluation.
- Supports evaluation through a command-line interface or Python API.
- Includes a benchmark dataset and meta-evaluation resources in the repository.
- Integrates with LlamaIndex for evaluating RAG applications built with that library.
Use Cases
- A RAG application team can compare pipeline results and determine whether retrieval or generation is the main source of poor answers.
- An engineer can inspect context precision and claim recall when tuning a retriever or changing its retrieved chunks.
- Researchers can evaluate answer faithfulness and hallucination across a collection of RAG results.
- LlamaIndex developers can apply RAGChecker metrics to applications built with that framework.
What you need
Detected in the repository
- Python (from pyproject.toml)
- Automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install the package and download the spaCy English model:
pip install ragchecker
python -m spacy download en_core_web_sm
For input format, model configuration, and CLI or Python usage, see the README and English tutorial.
Alternatives
- opik: Opik combines RAG evaluation with tracing and production monitoring, while RAGChecker focuses on claim-level diagnosis of retriever and generator performance.
- giskard-oss: Giskard emphasizes repeatable agent checks and adversarial safety testing, while RAGChecker measures RAG performance through claim-level entailment.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| RAGChecker | Python | Apache-2.0 | 1.1k | Inactive |
| opik | Python | Apache-2.0 | 22.8k | Active |
| giskard-oss | Python | Apache-2.0 | 5.9k | Active |
Considerations
The repository has had no commits in over a year and no releases in the past year; its measured status is inactive. The project has multiple contributors and is not flagged as concentrated around one contributor, but there has been no recent issue or pull-request activity. The README's example uses AWS Bedrock's Meta Llama 3 70B model for extraction and checking, so teams need to choose and configure suitable models and providers for their own setup. The README describes the benchmark as released in December 2024, while its initial feature list calls it upcoming. The project is licensed under Apache-2.0.
Found this useful?
Share it with someone who would like RAGChecker.