Which has better activity and maintenance signals?

Based on the RepoPilot analysis provided:

greenrobot/eventbus shows a "GO" verdict — Healthy across all four use cases. This is the RepoPilot's deterministic assessment covering dependency health, architecture, risk, and software assurance signals.

Unfortunately, the repository_data block does not include explicit maintenance signals for mybatis/mybatis-3 (such as commit frequency, issue response time, release cadence, or maintainer activity). The data shows only that mybatis/mybatis-3 has annotation definitions like @ResultOrdered (since 3.6.0) and @Update with Apache License headers, but no comparative health verdict or maintenance metrics.

To fairly compare maintenance signals between the two repos, I would need:

• RepoPilot analysis for mybatis/mybatis-3 (activity grade, dependency advisor reports, OpenSSF signals)
• Recent commit history for both projects
• Issue/PR closure rates and response times
• Release frequency and versioning patterns

The greenrobot/eventbus "GO" verdict is strong, but I cannot definitively say which has better maintenance signals without equivalent data for MyBatis.

FOLLOW_UPS:

• What release frequency does mybatis-3 maintain?
• Does greenrobot/eventbus have security advisories?
• Which repo has more active maintainer participation?