getzep/graphiti vs langchain-ai/langchain
Both showing Healthy signals — pick on fit, not health
As of July 2026, graphiti and langchain both show healthy maintenance signals. graphiti was committed to 1 day ago with 24+ active contributors, while langchain was committed to today with 14+ active contributors. graphiti is Apache-2.0-licensed while langchain 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
Strong maintenance signals
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
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
langchain-ai/langchain
Strong maintenance signals
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
Scorecard "Token-Permissions" is 0/10; no CI workflows detected
- ⚠No CI workflows detected
- ✓Last commit today
- ✓14 active contributors
- ✓Distributed ownership (top contributor 32% of recent commits)
- ✓MIT licensed
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: bring "Token-Permissions" 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
| graphiti | langchain | |
|---|---|---|
| Stars | 29,322 | 142,837 |
| Last commit | 1d ago | today |
| License | Apache-2.0 | MIT |
| Open issues | 432 | 446 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | — |
| Test coverage | 43% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | — |
| Cycles | 8 | — |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? getzep/graphiti · langchain-ai/langchain
Ask AI about getzep/graphiti vs langchain-ai/langchain
Open the chat with a comparison question pre-filled.