Which has better activity and maintenance signals?

Based on the RepoPilot analysis provided in the repository data, greenrobot/eventbus has clearer maintenance signals:

greenrobot/eventbus:

• RepoPilot verdict: "GO — Healthy across all four use cases" — This is an explicit, authoritative health assessment covering reliability, dependency fit, software assurance, and whether to depend on it.
• High community adoption: 24,728 stars and 4,651 forks indicate substantial ongoing use and trust.
• Active CI/CD: The README references GitHub Actions workflows for build status.
• Contribution guidelines present: [CONTRIBUTING.md] shows the project has established processes for issues, support channels, and pull request management.

hongyangandroid/baseadapter:

• No RepoPilot verdict provided in the analysis block — this means computed health signals are absent or unknown for this repository.
• Repository data shows sample code and test files, but no equivalent maintenance health summary.

Conclusion: greenrobot/eventbus has better activity and maintenance signals based on the available evidence. The explicit RepoPilot "GO" verdict and documented contribution processes indicate active stewardship, whereas hongyangandroid/baseadapter lacks comparable health signals in the retrieved data.

FOLLOW_UPS:

• What features does EventBus prioritize over Otto?
• How does baseadapter handle multiple item view types?
• When was EventBus last released or updated?