chenhg5/cc-connect vs infiniflow/ragflow
infiniflow/ragflow shows stronger signals overall
As of June 2026, ragflow shows healthier maintenance signals than cc-connect. ragflow rates Healthy overall while cc-connect rates Mixed. cc-connect last saw a commit 1 month ago with 36+ active contributors, while ragflow was committed to 1 day ago with 32+ active contributors. 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.
chenhg5/cc-connect →
Missing license — unclear to depend on
no license — legally unclear
no license — can't legally use code
Documented and popular — useful reference codebase to read through.
no license — can't legally use code
- ⚠No license — legally unclear to depend on
- ✓Last commit 1d ago
- ✓36+ active contributors
- ✓Distributed ownership (top contributor 30% of recent commits)
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: publish a permissive license (MIT, Apache-2.0, etc.)
- →Fork & modify Concerns → Mixed if: add a LICENSE file
- →Deploy as-is Concerns → Mixed if: add a LICENSE file
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
| cc-connect | ragflow | |
|---|---|---|
| Stars | 7,789 | 83,693 |
| Last commit | 1mo ago | 1d ago |
| License | — | Apache-2.0 |
| Open issues | 313 | 2,822 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 6% | 7% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | C |
| Cycles | — | 8 |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? chenhg5/cc-connect · infiniflow/ragflow
Ask AI about chenhg5/cc-connect vs infiniflow/ragflow
Open the chat with a comparison question pre-filled.