blankj/androidutilcode vs water8394/flink-recommandsystem-demo
blankj/androidutilcode shows stronger signals overall
As of June 2026, androidutilcode shows healthier maintenance signals than flink-recommandsystem-demo. androidutilcode rates Healthy overall while flink-recommandsystem-demo rates Concerns. androidutilcode last saw a commit 1 year ago with 18+ active contributors, while flink-recommandsystem-demo last saw a commit 2 years ago with 2+ 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.
blankj/androidutilcode →
Healthy across all four use cases
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.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Stale — last commit 2y ago
- ⚠Concentrated ownership — top contributor handles 58% of recent commits
- ✓18 active contributors
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
water8394/flink-recommandsystem-demo →
Stale and unlicensed — last commit 2y ago
no license — legally unclear; last commit was 2y ago…
no license — can't legally use code; no CI workflows detected…
Documented and popular — useful reference codebase to read through.
no license — can't legally use code; last commit was 2y ago…
- ⚠Stale — last commit 2y ago
- ⚠Small team — 2 contributors active in recent commits
- ⚠Concentrated ownership — top contributor handles 73% of recent commits
- ⚠No license — legally unclear to depend on
- ⚠No CI workflows detected
- ✓2 active contributors
- ✓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
Signal-by-signal breakdown
| androidutilcode | flink-recommandsystem-demo | |
|---|---|---|
| Stars | 33,678 | 4,473 |
| Last commit | 1y ago | 2y ago |
| License | Apache-2.0 | — |
| Open issues | 328 | 18 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | — |
| Test coverage | 21% | 21% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Concerns signals |
Want the full analysis? blankj/androidutilcode · water8394/flink-recommandsystem-demo
Ask AI about blankj/androidutilcode vs water8394/flink-recommandsystem-demo
Open the chat with a comparison question pre-filled.