infiniflow/ragflow vs patrickmn/go-cache
infiniflow/ragflow shows stronger signals overall
As of June 2026, ragflow shows healthier maintenance signals than go-cache. ragflow rates Healthy overall while go-cache rates Mixed. ragflow was committed to 1 day ago with 32+ active contributors, while go-cache last saw a commit 2 years ago with 6+ active contributors. ragflow is Apache-2.0-licensed while go-cache 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.
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
patrickmn/go-cache →
Stale — last commit 2y ago
last commit was 2y ago; top contributor handles 95% of recent commits…
no tests detected; no CI workflows detected…
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; no CI workflows detected
- ⚠Stale — last commit 2y ago
- ⚠Single-maintainer risk — top contributor 95% of recent commits
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓6 active contributors
- ✓MIT licensed
What would improve this?
- →Use as dependency Concerns → Mixed if: 1 commit in the last 365 days
- →Fork & modify Mixed → Healthy if: add a test suite
- →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 | go-cache | |
|---|---|---|
| Stars | 83,693 | 8,816 |
| Last commit | 1d ago | 2y ago |
| License | Apache-2.0 | MIT |
| Open issues | 2,822 | 76 |
| 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 · patrickmn/go-cache
Ask AI about infiniflow/ragflow vs patrickmn/go-cache
Open the chat with a comparison question pre-filled.