Which has better activity and maintenance signals?

Based on the RepoPilot analysis provided:

freeok/so-novel shows concerning maintenance signals:

• Verdict: WAIT — Single-maintainer risk — the project is flagged for review before adoption due to reliance on a single maintainer
• OpenSSF Scorecard: 4.0/10 — notably weak, with 0/10 scores on critical checks: Dependency-Update-Tool, Security-Policy, and SAST
• Code scanning (SAST): 0/0 open alerts — no automated scanning results reported
• Architecture grade C (50/100) — indicates moderate structural quality concerns

reactivex/rxjava appears more mature but specific maintenance signals aren't provided in the analysis block. However, the repository data shows:

• Established benchmark infrastructure (JMH performance tests across multiple areas: ReducePerf, StrictPerf, RangePerf, BlockingPerf)
• Comprehensive API documentation (e.g., CompletableEmitter interface with detailed javadoc)
• Professional error handling patterns and architectural depth visible in source

Summary: freeok/so-novel has explicit maintenance risk flags and low OpenSSF scores. reactivex/rxjava shows signs of active, professional development through its testing infrastructure and documentation, though the analysis block doesn't provide its specific scorecard. If maintenance and reliability are priorities, RxJava appears significantly stronger.

FOLLOW_UPS:

• What is so-novel's release cadence and latest version?
• Does RxJava have published CVE or dependency advisories?
• How do the two repos' contribution patterns differ?