ehang-io/nps vs infiniflow/ragflow
infiniflow/ragflow shows stronger signals overall
As of June 2026, ragflow shows healthier maintenance signals than nps. ragflow rates Healthy overall while nps rates Mixed. nps last saw a commit 2 years ago with 16+ active contributors, while ragflow was committed to 1 day ago with 32+ active contributors. nps is GPL-3.0-licensed while ragflow is Apache-2.0-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.
ehang-io/nps →
Stale — last commit 2y ago
copyleft license (GPL-3.0) — review compatibility; last commit was 2y ago
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Stale — last commit 2y ago
- ⚠Concentrated ownership — top contributor handles 70% of recent commits
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ✓16 active contributors
- ✓GPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
infiniflow/ragflow →
Healthy across the board
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 today
- ✓32+ active contributors
- ✓Distributed ownership (top contributor 16% of recent commits)
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Deploy as-is Mixed → 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
| nps | ragflow | |
|---|---|---|
| Stars | 34,053 | 83,693 |
| Last commit | 2y ago | 1d ago |
| License | GPL-3.0 | Apache-2.0 |
| Open issues | 525 | 2,822 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 3% | 7% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | C |
| Cycles | — | 8 |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? ehang-io/nps · infiniflow/ragflow
Ask AI about ehang-io/nps vs infiniflow/ragflow
Open the chat with a comparison question pre-filled.