Is LlamaIndex safe to use?

LlamaIndex has an HVTrust score of 45.2/100 (Grade D), ranked #507 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for LlamaIndex?

LlamaIndex scores 45.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 51.5k GitHub stars and is categorized under Agent Frameworks.

LlamaIndex

run-llama/llama_index

LlamaIndex is the leading document agent and OCR platform

Agent Frameworks Python Grade D Listed MIT

45.2/100

Rank #507 of 1204

Compare LlamaIndex

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-07 · 2d ago

Recent change

Rank +1

Is LlamaIndex safe? LlamaIndex scores 45.2/100 (Grade D), ranked #507 of 1204 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#74 YoMo — 45.3 (D) → #75 Upsonic — 45.3 (D) → #77 Parlant — 44.1 (D) → #78 OpenSSA — 42.0 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 140 spots (#367 → #507)

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Amazon Bedrock, Redis

2026-07-29

Rank Moved

Rank dropped 11 spots (#347 → #358)

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for LlamaIndex View Agent Frameworks Report missing data

89.7

Activity sub-score · out of 100

#76

In Agent Frameworks

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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

51.5k

Forks

7.9k

Last Push

2026-08-07

2 days ago

Commits (4 wk)

Downloads (7d)

1,798,567

pypi

HN mentions (30d)

Open Issues

183

Rank Change

was #507

Analysis

HVTrust Dimensions vs Agent Frameworks

45.2 / 100 · 75.0% confidence

LlamaIndex Agent Frameworks average (117 agents)

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

0 / 25

8.2 below avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.1 below avg 11.6

Maintenance60% last-push freshness · 40% commit activity

17.8 / 20

3.5 above avg 14.3

AdoptionLog-scaled stars · package downloads

19.6 / 20

8.2 above avg 11.4

Activity Inputs

89.7 / 100

StarsRepository reach

28.3 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

18.4 / 25

CommunityFork signal

18.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

—

Unable to query

Is LlamaIndex safe?

Public trust evidence for LlamaIndex is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does LlamaIndex publish package provenance?

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

Does LlamaIndex have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for LlamaIndex. 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 LlamaIndex actively maintained?

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

What license does LlamaIndex use?

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

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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

OpenAI

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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

How this surface has changed

Detected changes to LlamaIndex's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Amazon Bedrock, Redis

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, OpenAI, Redis

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain LlamaIndex?

For maintainers

HVTrust scores LlamaIndex 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-08-08

Rank Moved

Rank dropped 140 spots (#367 → #507)

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Amazon Bedrock, Redis

2026-07-29

Rank Moved

Rank dropped 11 spots (#347 → #358)

2026-07-15

Rank Moved

Rank dropped 23 spots (#321 → #344)

2026-07-14

Rank Moved

Rank dropped 18 spots (#303 → #321)

2026-07-13

Rank Moved

Rank dropped 34 spots (#269 → #303)

2026-06-24

Rank Moved

Rank dropped 29 spots (#240 → #269)

2026-06-23

Rank Moved

Rank dropped 19 spots (#221 → #240)

2026-06-22

Rank Moved

Rank dropped 11 spots (#210 → #221)

2026-06-21

Rank Moved

Rank dropped 14 spots (#196 → #210)

2026-06-20

HVTrust Changed

HVTrust down 3.6pts (46.0 → 42.4)

2026-06-18

Rank Moved

Rank dropped 13 spots (#169 → #182)

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, OpenAI, Redis

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-06-01

Rank Moved

Rank dropped 17 spots (#117 → #134)

2026-05-29

HVTrust Changed

HVTrust up 7.6pts (35.2 → 42.8)

2026-05-28

Activity Score Changed

Activity score up 22pts (71 → 93)

2026-05-25

Newly Listed

First tracked at rank #35

GitHub → PyPI: llama-index

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

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