LightRAG

[EMNLP2025] LightRAG: Simple and Fast Retrieval-Augmented Generation

Memory & Knowledge Python Listed MIT

Is LightRAG safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.5 / 10
Provenance Attested
Signed commits 53%
Last push 2d ago
Advisories None known
Compare LightRAG

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

Pick any agent to compare →
Suggest a correction

In detail: LightRAG scores 84.4/100 (Grade A), ranked #101 of 1378 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.5/10; 53% of recent commits are signed; no published advisory affects its latest release (lightrag-hku); last pushed 2026-10-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How LightRAG could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships LightRAG and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/HKUDS/LightRAG, MIT, last pushed 2026-10-15. 53% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.5/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 9
    CII-Best-Practices 0
    Code-Review 2
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages Linked and attested

    • PyPI lightrag-hku Source link points back to this repo Build provenance attested
  4. What you install today No known advisories

    Latest release checked: lightrag-hku 1.5.7. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of LightRAG.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues LightRAG’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How LightRAG compares in Memory & Knowledge

  1. #8 Hindsight 85.1 +0.7
  2. #9 Vespa 84.6 +0.2
  3. #10 LightRAG 84.4 this agent
  4. #11 agentmemory 76.3 −8.1
  5. #12 Qdrant 76.0 −8.4

Bars show each HVTrust score; the tick marks LightRAG’s 84.4.

Where the 84.4 comes from

HVTrust dimensions vs the Memory & Knowledge average

84.4 / 100 · 100.0% confidence

LightRAG Memory & Knowledge average (51 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.0 / 25
5.5 above avg 11.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.5 above avg 12.5
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
in line with avg 12.9
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
2.9 above avg 17.0
AdoptionLog-scaled stars · package downloads
17.2 / 20
4.1 above avg 13.1

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-10-10
Rank Moved
Rank dropped 10 spots (#86 → #96)
2026-09-23
Rank Moved
Rank dropped 28 spots (#51 → #79)
2026-09-21
Rank Moved
Rank rose 39 spots (#90 → #51)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
95.0
Activity sub-score · out of 100
#10

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

Signals refreshed 2026-10-17 08:08 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
40.2k
Forks
5.7k
Last Push
2026-10-15
2 days ago
Commits (4 wk)
109
Downloads (7d)
40,041
pypi
HN mentions (30d)
26
Open Issues
236
Rank Change
▼1
was #100

Analysis

Activity Inputs

95.0 / 100
StarsRepository reach
27.6 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.5 / 20

Common questions about LightRAG

Public supply-chain signals for LightRAG are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but LightRAG carries less obvious unverified-evidence risk than projects with thin signals.
Does LightRAG publish package provenance?
Yes. LightRAG's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does LightRAG have an OpenSSF Scorecard?
LightRAG has an OpenSSF Scorecard score of 5.5/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 LightRAG actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does LightRAG use?
LightRAG ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are LightRAG's commits signed?
53% of the last 100 commits to LightRAG 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
high confidence
6 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • database
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 LightRAG?

For maintainers

HVTrust scores LightRAG 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.

Reputation Timeline

Signal history
Rank 8
2026-10-10
Rank Moved
Rank dropped 10 spots (#86 → #96)
2026-09-23
Rank Moved
Rank dropped 28 spots (#51 → #79)
2026-09-21
Rank Moved
Rank rose 39 spots (#90 → #51)
2026-09-13
Rank Moved
Rank dropped 19 spots (#75 → #94)
2026-09-12
Rank Moved
Rank rose 11 spots (#86 → #75)
2026-09-06
Rank Moved
Rank dropped 11 spots (#75 → #86)
2026-09-05
Rank Moved
Rank dropped 16 spots (#59 → #75)
2026-09-02
Rank Moved
Rank rose 13 spots (#72 → #59)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 84.4 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/lightrag.svg)](https://hvtracker.net/agents/lightrag)
HTML:
<a href="https://hvtracker.net/agents/lightrag"><img src="https://hvtracker.net/badge/lightrag.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 · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON