Which has better activity and maintenance signals?

Based on the RepoPilot analysis signals provided:

greenrobot/eventbus shows a clear verdict: GO — Healthy across all four use cases. This is a deterministic computed signal covering reliability, dependency fit, software assurance, and architecture quality.

For yalantis/side-menu.android, no RepoPilot verdict or analysis signals are included in the data provided, so I cannot make a direct comparison on those metrics.

What I can observe from the repository metadata:

• greenrobot/eventbus: 24,728 stars, 4,651 forks — high adoption and long-term maintenance evident from the README's note about apps with "1,000,000,000+ installs" using it in production. The CONTRIBUTING.md [CONTRIBUTING.md:L1-L40] actively guides issue reporting and pull request workflows, suggesting ongoing project governance.

• yalantis/side-menu.android: The README [README.md:L4] references a Dribbble design project and includes a note "God bless Ukraine!" but lacks explicit maintenance signals in the provided data. The sample code uses older Android support libraries (e.g., android.support.v4.widget.DrawerLayout, android.support.v7.widget.Toolbar) rather than AndroidX, which may indicate the project is less actively maintained.

Verdict: greenrobot/eventbus has stronger documented signals of active maintenance and reliability. For yalantis/side-menu.android, I'd recommend checking the GitHub issues, pull request response times, and last commit date directly to assess current maintenance status.

FOLLOW_UPS:

• When was the last commit to each repository?
• Does EventBus require AndroidX or support legacy libraries?
• What are the current test coverage metrics for EventBus?