Which has better activity and maintenance signals?

Based on the RepoPilot analysis provided:

lmax-exchange/disruptor has a clear verdict: GO — Healthy across all four use cases. This is an authoritative computed signal indicating the repository is well-maintained and reliable across dependency, architecture, and software assurance dimensions.

For realm/realm-java, no RepoPilot verdict is included in the data provided, so I cannot make a direct comparison using those signals.

However, from the repository stats alone:

• lmax-exchange/disruptor: 18,434 stars, 3,966 forks — a mature, widely-adopted library with established community engagement. The README references active CI/CD workflows (Java CI with Gradle, CodeQL), a Google Group for support, and comprehensive documentation.
• realm/realm-java: The repository data shows active documentation updates (CHANGELOG.md entries, SUPPORT.md with troubleshooting notes) and a structured contribution process (CONTRIBUTING.md references), suggesting ongoing maintenance.

Summary: lmax-exchange/disruptor has explicit health signals (RepoPilot verdict) confirming active, reliable maintenance. realm/realm-java shows signs of maintenance activity, but without equivalent health signals in the data, a direct comparison is limited. If maintenance health is critical for your decision, lmax-exchange/disruptor's GO verdict provides stronger assurance.

FOLLOW_UPS:

• What are the recent commit frequencies for both repos?
• Does realm-java have published security advisories or vulnerabilities?
• Which repository is more suitable for production latency-sensitive systems?