Is GraphRAG safe to use?

GraphRAG has an HVTrust score of 72.5/100 (Grade B), ranked #111 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for GraphRAG?

GraphRAG scores 72.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 35.4k GitHub stars and is categorized under Memory & Knowledge.

GraphRAG

microsoft/graphrag

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

Memory & Knowledge Python Grade B Listed MIT

72.5/100

Rank #111 of 1283

Compare GraphRAG

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-11 · 0d ago

Recent change

No recent signal change

Is GraphRAG safe? GraphRAG scores 72.5/100 (Grade B), ranked #111 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.6/10; 100% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#9 Chroma — 74.4 (B) → #10 ReMe — 74.3 (B) → #12 Milvus — 72.4 (B) → #13 RAGFlow — 72.2 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-07-17

Activity Score Changed

Activity score up 5pts (76 → 81)

2026-07-13

Newly Listed

First tracked at rank #82

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.6/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for GraphRAG View Memory & Knowledge Report missing data

80.2

Activity sub-score · out of 100

#11

In Memory & Knowledge

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

35.4k

Forks

3.7k

Last Push

2026-08-11

today

Commits (4 wk)

Downloads (7d)

18,516

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #110

Analysis

HVTrust Dimensions vs Memory & Knowledge

72.5 / 100 · 100.0% confidence

GraphRAG Memory & Knowledge average (42 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

13.2 / 25

3.1 above avg 10.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.4 below avg 12.2

Transparency50% declared license · 50% OSSF Scorecard

14.1 / 17

1.6 above avg 12.5

Maintenance60% last-push freshness · 40% commit activity

13.8 / 20

3.9 below avg 17.7

AdoptionLog-scaled stars · package downloads

16.6 / 20

3.1 above avg 13.6

Activity Inputs

80.2 / 100

StarsRepository reach

27.3 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

11.3 / 25

CommunityFork signal

16.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.6 / 10

OpenSSF Scorecard · scanned Aug 10, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is GraphRAG safe?

GraphRAG has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does GraphRAG publish package provenance?

No published build provenance is currently detected for GraphRAG. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does GraphRAG have an OpenSSF Scorecard?

GraphRAG has an OpenSSF Scorecard score of 6.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is GraphRAG actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does GraphRAG use?

GraphRAG ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are GraphRAG's commits signed?

100% of the last 100 commits to GraphRAG are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Multi-provider (LiteLLM)

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain GraphRAG?

For maintainers

HVTrust scores GraphRAG from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-07-17

Activity Score Changed

Activity score up 5pts (76 → 81)

2026-07-13

Newly Listed

First tracked at rank #82

GitHub → PyPI: graphrag

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/graphrag.svg)](https://hvtracker.net/agents/graphrag)
            
HTML:
            <a href="https://hvtracker.net/agents/graphrag"><img src="https://hvtracker.net/badge/graphrag.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON