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. Full methodology →
Signals refreshed2026-06-04 00:07 UTC·Repo last pushed yesterday
Rank Trend
2026-06-022026-06-03
Activity & Reach
Stars
36.1k
Forks
5.1k
Last Push
2026-06-03
yesterday
Commits (4 wk)
815
Downloads (7d)
59,611
pypi
HN mentions (30d)
14
Open Issues
224
Rank Change
▼2
was #52
Analysis
HVTrust Dimensions
72.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
8.7 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
17.3 / 20
Activity Inputs
94.5 / 100
StarsRepository reach
27.3 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.2 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
24%
of last 100 commits verified
Is LightRAG safe?
LightRAG 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 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?
No OpenSSF Scorecard data is currently published for LightRAG. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is LightRAG actively maintained?
Actively maintained. The repository was pushed to within the last 1 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?
24% 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain LightRAG?
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.
