conductor-oss/conductor vs hotbitmapgg/bilibili-android-client
conductor-oss/conductor shows stronger signals overall
As of June 2026, conductor shows healthier maintenance signals than bilibili-android-client. conductor rates Healthy overall while bilibili-android-client rates Mixed. conductor last saw a commit 1 month ago with 18+ active contributors, while bilibili-android-client last saw a commit 5 years ago with 2+ active contributors. conductor is Apache-2.0-licensed while bilibili-android-client is WTFPL-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.
conductor-oss/conductor →
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.
No critical CVEs, sane security posture — runnable as-is.
- ✓Last commit today
- ✓18 active contributors
- ✓Distributed ownership (top contributor 14% of recent commits)
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
hotbitmapgg/bilibili-android-client →
Stale — last commit 5y ago
non-standard license (WTFPL); last commit was 5y ago…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 5y ago; no CI workflows detected
- ⚠Stale — last commit 5y ago
- ⚠Small team — 2 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 99% of recent commits
- ⚠Non-standard license (WTFPL) — review terms
- ⚠No CI workflows detected
- ✓2 active contributors
- ✓WTFPL licensed
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
- →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
| conductor | bilibili-android-client | |
|---|---|---|
| Stars | 31,781 | 4,478 |
| Last commit | 1mo ago | 5y ago |
| License | Apache-2.0 | WTFPL |
| Open issues | 164 | 9 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | — |
| Test coverage | 65% | 2% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? conductor-oss/conductor · hotbitmapgg/bilibili-android-client
Ask AI about conductor-oss/conductor vs hotbitmapgg/bilibili-android-client
Open the chat with a comparison question pre-filled.