Which has better activity and maintenance signals?

Based on the RepoPilot analysis provided, I can only assess blankj/androidutilcode clearly:

blankj/androidutilcode:

• Verdict: GO — Healthy across all four use cases (per RepoPilot analysis)
• This signals robust maintenance, reliability, and active stewardship
• 33,678 stars and 10,658 forks indicate substantial community adoption and trust
• The README documents structured modules (utilcode and subutil) with change logs and CI/CD integration (GitHub Actions badge visible)

freeok/so-novel:

• No RepoPilot verdict is provided in the repository data
• The CHANGELOG shows recent activity (refactoring, performance optimization) [CHANGELOG.md:L24-L41], indicating ongoing maintenance
• However, without quantitative signals (stars, forks, issue/PR activity), I cannot make a direct comparison

Summary: blankj/androidutilcode has explicit health signals ("GO" verdict across all use cases) and significantly higher community engagement metrics. freeok/so-novel shows code activity but lacks published health signals in the data provided. If you need a definitive maintenance comparison, you'd want to check freeok/so-novel's advisory data, dependency status, and project-practice signals on its full profile.

FOLLOW_UPS:

• Does blankj/androidutilcode have reported security advisories?
• What modules does utilcode expose for Android development?
• How does freeok/so-novel handle concurrent downloads currently?