Which has better activity and maintenance signals?

Based on the RepoPilot analysis provided:

netflix/hystrix shows a WAIT — Slowing verdict with last commit 5 months ago. The README explicitly states that Hystrix is in maintenance mode and no longer in active development. Netflix made a final release (1.5.18) and will not actively review issues, merge pull requests, or release new versions going forward. The project has pivoted toward adaptive implementations and recommends that others use projects like resilience4j for new work.

netflix/ribbon is also in maintenance mode according to its README. However, the status description is more granular—it notes that different Ribbon components have different levels of attention. Specifically, ribbon-core, ribbon-eureka, and ribbon-loadbalancer are deployed at scale in production, while other components (like ribbon-evcache, ribbon-guice, ribbon-transport) are not used. The README indicates the team has shifted focus to building an RPC solution on top of gRPC instead.

Verdict: Neither repository shows strong maintenance signals. Both are in maintenance mode with no active development. However, netflix/ribbon maintains production usage of specific components (core, eureka, loadbalancer) and has a clearer roadmap (migration to gRPC), whereas netflix/hystrix is fully deprecated for new work. If you need production reliability, ribbon's core components may have better operational support, but for new development, both recommend alternatives.

FOLLOW_UPS:

• What specific Hystrix features does your codebase depend on?
• Are you considering migration to resilience4j or other alternatives?
• Which ribbon components does your infrastructure actually use?