Which has better activity and maintenance signals?

Based on RepoPilot analysis and repository signals, reactivex/rxandroid has stronger maintenance signals than freeok/so-novel.

Key Differences:

freeok/so-novel:

• RepoPilot verdict: WAIT — Single-maintainer risk (the primary risk signal)
• 7,798 stars, 701 forks
• This single-maintainer designation suggests dependency concentration and potential sustainability concerns

reactivex/rxandroid:

• No single-maintainer risk flagged
• Part of the ReactiveX organization (multi-org backing)
• Has formal release processes documented in [RELEASING.md:L1-L18], including version management, changelog tracking, tagging, and GitHub release steps
• Automated CI/CD: release workflow in [.github/workflows/release.yaml:L1-L32] with automated publishing to Maven Central
• Active dependency management via Dependabot [.github/dependabot.yaml:L1-L8]
• Structured changelog history (CHANGES.md shows version releases with dates)
• Comprehensive test coverage evidenced by [rxandroid/src/test/java/io/reactivex/rxjava3/android/plugins/RxAndroidPluginsTest.java]

Summary:

reactivex/rxandroid demonstrates better institutional maintenance through organizational backing, automated release infrastructure, and formal processes. freeok/so-novel's single-maintainer risk is the primary concern for long-term adoption and reliability.

If you're considering depending on either, freeok/so-novel warrants careful review of maintainer capacity and contingency planning.

FOLLOW_UPS:

• What are freeok/so-novel's main dependencies?
• How frequently does reactivex/rxandroid release updates?
• What's the scope of freeok/so-novel's functionality?