RepoPilot

greenrobot/greendao vs lmax-exchange/disruptor

lmax-exchange/disruptor shows stronger signals overall

As of June 2026, disruptor shows healthier maintenance signals than greendao. disruptor rates Healthy overall while greendao rates Concerns. greendao last saw a commit 2 years ago with 3+ active contributors, while disruptor last saw a commit 1 year ago with 14+ 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.

greenrobot/greendao

Concerns

Stale and unlicensed — last commit 2y ago

ConcernsDependency

no license — legally unclear; last commit was 2y ago

ConcernsFork & modify

no license — can't legally use code; last commit was 2y ago

HealthyLearn from

Documented and popular — useful reference codebase to read through.

ConcernsDeploy as-is

no license — can't legally use code; last commit was 2y ago

  • Stale — last commit 2y ago
  • Small team — 3 contributors active in recent commits
  • Concentrated ownership — top contributor handles 64% of recent commits
  • No license — legally unclear to depend on
  • 3 active contributors
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: publish a permissive license (MIT, Apache-2.0, etc.)
  • Fork & modify ConcernsMixed if: add a LICENSE file
  • Deploy as-is ConcernsMixed if: add a LICENSE file

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

lmax-exchange/disruptor

Healthy

Healthy across all four use cases

HealthyDependency

Permissive license, no critical CVEs, actively maintained — safe to depend on.

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

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

Signal-by-signal breakdown

greendaodisruptor
Stars12,60218,326
Last commit2y ago1y ago
LicenseApache-2.0
Open issues23717
Has tests
Has CI
Test coverage100%41%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineConcerns signalsHealthy signals

Want the full analysis? greenrobot/greendao · lmax-exchange/disruptor

Ask AI about greenrobot/greendao vs lmax-exchange/disruptor

Open the chat with a comparison question pre-filled.