Item detail
github.com

run-llama/llama_index

run-llama/llama_index is a framework in RepoRadar's Radar section, holding Gold tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Score8.9
Popularity84.0
Riskconditional
TierGold
Score breakdown
Usefulness9.0
Novelty7.0
Momentum8.0
Maturity8.6
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for developers building document workflows, RAG systems, and agentic knowledge tools who need more than a raw vector database or one-off parser.

Who should use it

RAG developers document workflow builders AI product teams developers shipping knowledge-heavy apps

Who should skip it

Move on from run-llama/llama_index if the licensing terms, language support, or platform requirements do not fit your project.

About this signal

run-llama/llama_index is tracked by RepoRadar as a framework in the Radar section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for run-llama/llama_index are workflow potential (10.0) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The run-llama/llama_index record combines a 8.9/10 composite score with separate popularity (84.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

LlamaIndex workflows often process private documents and may call managed parsing or extraction services, so audit exactly which files leave your environment before using cloud components.

Evidence links
Closest alternatives / related signals
rag documents ocr agents developer-tools
Verification record

What RepoRadar actually verified

Tested in a bounded workflow

Bounded representative workflow retained by RepoRadar verification harness. Last checked 2026-07-13T10:35:52.922007Z.

passed · cohort-20260712-llama-index-document

Tester
RepoRadar automated local verification harness
Started
2026-07-13T03:22:04.493916Z
Completed
2026-07-13T03:22:09.502844Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
0 minute(s)
Evidence scope
Bounded setup or capability check
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Executed bounded check: Create and read a local LlamaIndex Document.
  • Captured the complete sanitized stdout, stderr, exit status, and 5.01-second wall time.
Observed results
  • Command exited 0 after 5.01 seconds.
  • Expected marker 'CHECK_OK' was observed in retained output.
Observed strengths
  • LlamaIndex created a local Document and returned the exact 21-character fixture text without an index, embedding model, or LLM.
Friction
  • The command emitted stderr; warnings or errors are preserved in the retained log for review.
Limitations
  • No index, embedding model, retrieval, persistence backend, or LLM was exercised.
  • This bounded cohort check is not a production benchmark or a claim of real user-workflow adoption.

Pricing assessment: No paid plan or metered provider usage was exercised; package or licensing, hosting, and provider costs remain workflow-dependent.

Privacy assessment: No repository content, user data, or provider prompt was transmitted; broader product data handling was not assessed by this bounded run.

Open retained test log →

passed · cohort-20260712-llama-index-document-store-workflow

Tester
RepoRadar automated local verification harness
Started
2026-07-13T10:35:47.509215Z
Completed
2026-07-13T10:35:52.922007Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded representative workflow
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Created 1 synthetic fixture file(s) inside the disposable work directory; retained hashes prove the exact inputs.
  • Created two metadata-bearing LlamaIndex Documents and converted them into nodes with a bounded SentenceSplitter configuration.
  • Added the nodes to SimpleDocumentStore, persisted the store, and validated both teams and document counts in the retained artifact.
  • Executed bounded check: Split two synthetic runbooks into LlamaIndex nodes, store them, and persist the document store.
  • Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 5.41-second wall time.
Observed results
  • Command exited 0 after 5.41 seconds.
  • LlamaIndex produced two nodes with metadata intact and serialized both into a reloadable document-store JSON artifact.
  • Expected marker 'CHECK_OK documents=2 nodes=2 persisted=2' was observed in retained output.
  • Validated docstore.json: 4 required marker(s) present and 0 excluded marker(s) absent; size and SHA-256 are retained.
Observed strengths
  • The core ingestion, node, metadata, document-store, and persistence APIs worked together locally without an embedding or language model.
Friction
  • Chunk size must account for metadata tokens; this fixture intentionally uses a size large enough to keep one node per short runbook.
  • Setup or runtime emitted 9 stderr line(s); the complete warnings/errors are preserved in the retained log.
Limitations
  • This ingestion and persistence path does not exercise embeddings, vector retrieval, an LLM, readers for external formats, or production corpus scale.
  • This credential-free disposable workflow does not establish production scale, model quality, reliability under sustained use, or team adoption.

Pricing assessment: The workflow used only llama-index-core locally and incurred no parser, embedding, model, or managed-index charge.

Privacy assessment: Both synthetic runbooks were processed and persisted only inside the disposable work directory, which the harness removed.

Open retained test log →

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

46 dated snapshots retained from 2026-06-19 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.9 current · +0.0 net
Repository momentum9.6 current · +1.6 net
GitHub stars (observed)51,623 current · +795 net
GitHub stars51,623 exact observation
Versionv0.14.23
Last release2026-06-24T19:36:43Z
Maintenanceactive
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.99.651,623conditionaltry nowactive
2026-08-128.99.651,594conditionaltry nowactive
2026-08-118.99.651,556conditionaltry nowactive
2026-08-108.99.651,528conditionaltry nowactive
2026-08-098.99.651,488conditionaltry nowactive
2026-08-088.99.651,454conditionaltry nowactive
2026-08-078.99.651,335conditionaltry nowactive
2026-08-068.98.0Not recordedconditionaltry nownot recorded
2026-08-058.98.0Not recordedconditionaltry nownot recorded
2026-08-048.99.651,335conditionaltry nowactive
2026-08-038.99.651,335conditionaltry nowactive
2026-08-028.99.651,295conditionaltry nowactive

Why the record changed

stars changed

Stars changed: 51594 → 51623.

stars changed

Stars changed: 51556 → 51594.

stars changed

Stars changed: 51528 → 51556.

stars changed

Stars changed: 51488 → 51528.

stars changed

Stars changed: 51454 → 51488.

stars changed

Stars changed: 51335 → 51454.

stars changed

Stars changed: 51295 → 51335.

stars changed

Stars changed: 51268 → 51295.

stars changed

Source-observed stars changed: 51262 → 51268. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 51155 → 51192.

stars changed

Source-observed stars changed: 51153 → 51155. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 50905 → 51153.