Which has better activity and maintenance signals?

Based on RepoPilot's analysis, lmax-exchange/disruptor has clearer positive signals:

lmax-exchange/disruptor:

• RepoPilot verdict: GO — Healthy across all four use cases
• This is a deterministic signal covering dependency fit, risk profile, architecture, and software assurance
• The repo shows 18,326 stars and 3,971 forks, indicating broad adoption
• Active CI/CD: Java CI with Gradle and CodeQL workflows are running (visible in the README badges)

netflix/hystrix:

• No RepoPilot analysis signals are provided in the data
• The CHANGELOG shows recent activity through version 1.5.10, including merged PRs (e.g., Pull 1489, 1481, 1482 for CodaHale metrics and Javanica improvements)
• However, without explicit maintenance verdicts from RepoPilot, I cannot make a direct comparative claim about health across use cases

Summary: Disruptor has an explicit "GO" health verdict from RepoPilot across all four assessment categories. Hystrix shows evidence of maintenance activity in the changelog but lacks the same authoritative health signals in the provided data. For risk assessment and production readiness, disruptor's verdict is more conclusive.

FOLLOW_UPS:

• What specific use case are you evaluating disruptor for?
• Does hystrix's deprecation status affect your project?
• How does latency sensitivity factor into your choice?