lmax-exchange/disruptor vs saiwu-bigkoo/android-convenientbanner
lmax-exchange/disruptor shows stronger signals overall
As of June 2026, disruptor shows healthier maintenance signals than android-convenientbanner. disruptor rates Healthy overall while android-convenientbanner rates Concerns. disruptor last saw a commit 1 year ago with 14+ active contributors, while android-convenientbanner last saw a commit 2 years ago with 6+ 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.
lmax-exchange/disruptor →
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 1y ago
- ⚠Concentrated ownership — top contributor handles 61% of recent commits
- ✓14 active contributors
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
saiwu-bigkoo/android-convenientbanner →
Stale and unlicensed — last commit 3y ago
no license — legally unclear; last commit was 3y ago…
no license — can't legally use code; no tests detected…
Documented and popular — useful reference codebase to read through.
no license — can't legally use code; last commit was 3y ago…
- ⚠Stale — last commit 3y ago
- ⚠Single-maintainer risk — top contributor 90% of recent commits
- ⚠No license — legally unclear to depend on
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓6 active contributors
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
| disruptor | android-convenientbanner | |
|---|---|---|
| Stars | 18,326 | 4,752 |
| Last commit | 1y ago | 2y ago |
| License | Apache-2.0 | — |
| Open issues | 17 | 93 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 41% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Concerns signals |
Want the full analysis? lmax-exchange/disruptor · saiwu-bigkoo/android-convenientbanner
Ask AI about lmax-exchange/disruptor vs saiwu-bigkoo/android-convenientbanner
Open the chat with a comparison question pre-filled.