RepoPilot

getzep/graphiti vs run-llama/llama_index

getzep/graphiti shows stronger signals overall

As of July 2026, graphiti shows healthier maintenance signals than llama_index. graphiti rates Healthy overall while llama_index rates Mixed. graphiti was committed to 1 day ago with 24+ active contributors, while llama_index was committed to today with 49+ active contributors. graphiti is Apache-2.0-licensed while llama_index is MIT-licensed. Neither has known critical or high-severity CVEs in its dependency tree.

Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.

getzep/graphiti

Healthy

Strong maintenance signals

HealthyDependency

Permissive license, no critical CVEs, actively maintained — safe to depend on.

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; 8 cyclic import chains — pervasive coupling

  • Scorecard: default branch unprotected (0/10)
  • Last commit 1d ago
  • 24+ active contributors
  • Distributed ownership (top contributor 35% of recent commits)
  • Apache-2.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

run-llama/llama_index

Mixed

Mixed signals — read the receipts

MixedDependency

no tests detected; no CI workflows detected

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; no CI workflows detected

  • No CI workflows detected
  • No test directory detected
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 49+ active contributors
  • Distributed ownership (top contributor 20% of recent commits)
  • MIT licensed

What would improve this?

  • Use as dependency Mixed to Healthy if: add a test suite
  • Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

graphitillama_index
Stars29,32251,180
Last commit1d agotoday
LicenseApache-2.0MIT
Open issues432588
Has tests
Has CI
Test coverage43%0%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeC
Cycles8
Bottom-lineHealthy signalsMixed signals

Want the full analysis? getzep/graphiti · run-llama/llama_index

Ask AI about getzep/graphiti vs run-llama/llama_index

Open the chat with a comparison question pre-filled.