Which has better activity and maintenance signals?

Based on the RepoPilot analysis signals provided:

realm/realm-java shows a "GO — Healthy across all four use cases" verdict, which indicates positive signals across reliability, dependency fit, software assurance, and maintenance quality. However, the README also includes a significant caveat: the project announced deprecation of Atlas Device Sync + Realm SDKs in September 2024, with guidance to use Realm Kotlin instead for new projects.

yunaiv/ruoyi-vue-pro has no RepoPilot analysis signals included in the repository data provided, so I cannot make a direct comparison of its computed health metrics.

What we can observe:

For realm/realm-java: The codebase shows active contribution signals—there are recent changelog entries [CHANGELOG.md:L125-L127] documenting bug fixes, Kotlin extensions [realm/kotlin-extensions/src/main/kotlin/io/realm/kotlin/RealmModelExtensions.kt], and documented contribution guidelines [CONTRIBUTING.md]. However, the SDK deprecation notice is a material maintenance signal suggesting reduced future investment.

For yunaiv/ruoyi-vue-pro: The repository data shows SQL schemas and database patches with recent timestamps (e.g., dates in 2025, 2026 in the seed data), but without RepoPilot signals, I cannot assess broader maintenance health.

Recommendation: If you need current best-practice support, realm/realm-java's guidance to adopt Realm Kotlin for new projects suggests Java version maintenance may decline. For yunaiv/ruoyi-vue-pro, I'd need additional signals (dependency advisories, issue velocity, contributor count) to assess maintenance quality.

FOLLOW_UPS:

• Does realm-java deprecation affect your use case?
• What's your deployment target—Android or backend?
• Is yunaiv/ruoyi-vue-pro's activity sufficient for your needs?