RepoPilot

lmax-exchange/disruptor vs reactive-streams/reactive-streams-jvm

lmax-exchange/disruptor shows stronger signals overall

As of June 2026, disruptor shows healthier maintenance signals than reactive-streams-jvm. disruptor rates Healthy overall while reactive-streams-jvm rates Mixed. disruptor last saw a commit 1 year ago with 14+ active contributors, while reactive-streams-jvm last saw a commit 2 years ago with 31+ active contributors. disruptor is Apache-2.0-licensed while reactive-streams-jvm is MIT-0-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.

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

reactive-streams/reactive-streams-jvm

Mixed

Stale — last commit 2y ago

ConcernsDependency

non-standard license (MIT-0); last commit was 2y ago

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 2y ago
  • Non-standard license (MIT-0) — review terms
  • 31+ active contributors
  • Distributed ownership (top contributor 47% of recent commits)
  • MIT-0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: clarify license terms

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

Signal-by-signal breakdown

disruptorreactive-streams-jvm
Stars18,3264,877
Last commit1y ago2y ago
LicenseApache-2.0MIT-0
Open issues1735
Has tests
Has CI
Test coverage41%100%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsMixed signals

Want the full analysis? lmax-exchange/disruptor · reactive-streams/reactive-streams-jvm

Ask AI about lmax-exchange/disruptor vs reactive-streams/reactive-streams-jvm

Open the chat with a comparison question pre-filled.