Which has better activity and maintenance signals?

Based on the RepoPilot analysis and README data:

netflix/ribbon shows clear maintenance signals:

• Status: Explicitly in maintenance mode [netflix/ribbon README.md:L31-L62]. The project states: "Recognizing these realities and deficiencies, we are placing Ribbon in maintenance mode."
• Production use: Limited — only ribbon-core, ribbon-eureka, and ribbon-loadbalancer are deployed at scale in production. Most other components (ribbon, ribbon-transport, ribbon-evcache, ribbon-guice) are not used [netflix/ribbon README.md:L31-L62].
• Direction: Netflix has moved to gRPC-based solutions internally and is not prioritizing new feature requests [netflix/ribbon README.md:L31-L62].

scwang90/smartrefreshlayout shows stronger activity signals:

• Engagement: Maintains paid QQ support groups and free discussion communities for users [scwang90/smartrefreshlayout README.md:L314-L322], indicating active user base and ongoing support.
• No explicit "maintenance only" status declared.

Verdict: scwang90/smartrefreshlayout appears more actively maintained with direct user engagement, while netflix/ribbon is in stable maintenance mode with limited new development.

However, the RepoPilot verdict for netflix/ribbon is "GO — Healthy across all four use cases", so both are suitable depending on your needs—ribbon for stable, battle-tested load balancing, and smartrefreshlayout for an actively maintained refresh UI component.

FOLLOW_UPS:

• What components of ribbon are production-ready?
• How old is smartrefreshlayout's last release?
• Does smartrefreshlayout have dependency vulnerabilities?