infiniflow/ragflow vs snail007/goproxy
infiniflow/ragflow shows stronger signals overall
As of June 2026, ragflow shows healthier maintenance signals than goproxy. ragflow rates Healthy overall while goproxy rates Mixed. ragflow was committed to 1 day ago with 32+ active contributors, while goproxy last saw a commit 9 months ago with 1+ active contributor. ragflow is Apache-2.0-licensed while goproxy is GPL-3.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.
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
snail007/goproxy →
Slowing — last commit 8mo ago
copyleft license (GPL-3.0) — review compatibility; single-maintainer (no co-maintainers visible)…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 8mo ago; no CI workflows detected
- ⚠Slowing — last commit 8mo ago
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓Last commit 8mo ago
- ✓GPL-3.0 licensed
What would improve this?
- →Use as dependency Concerns → Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| ragflow | goproxy | |
|---|---|---|
| Stars | 83,693 | 16,955 |
| Last commit | 1d ago | 9mo ago |
| License | Apache-2.0 | GPL-3.0 |
| Open issues | 2,822 | 144 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 7% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | — |
| Cycles | 8 | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? infiniflow/ragflow · snail007/goproxy
Ask AI about infiniflow/ragflow vs snail007/goproxy
Open the chat with a comparison question pre-filled.