lmax-exchange/disruptor vs meituan-dianping/walle
lmax-exchange/disruptor shows stronger signals overall
As of June 2026, disruptor shows healthier maintenance signals than walle. disruptor rates Healthy overall while walle rates Mixed. disruptor last saw a commit 1 year ago with 14+ active contributors, while walle last saw a commit 2 years ago with 6+ active contributors. Both use the Apache-2.0 license. 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
meituan-dianping/walle →
Stale — last commit 2y ago
last commit was 2y ago; no tests detected…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; Scorecard "Branch-Protection" is 0/10…
- ⚠Stale — last commit 2y ago
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓6 active contributors
- ✓Distributed ownership (top contributor 46% of recent commits)
- ✓Apache-2.0 licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: 1 commit in the last 365 days; add a test suite
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days; 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 OpenSSF Scorecard
Signal-by-signal breakdown
| disruptor | walle | |
|---|---|---|
| Stars | 18,326 | 6,858 |
| Last commit | 1y ago | 2y ago |
| License | Apache-2.0 | Apache-2.0 |
| Open issues | 17 | 108 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 41% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? lmax-exchange/disruptor · meituan-dianping/walle
Ask AI about lmax-exchange/disruptor vs meituan-dianping/walle
Open the chat with a comparison question pre-filled.