Which has better activity and maintenance signals?

Based on the RepoPilot analysis signals provided, ice-cube-ruby/ice_cube shows better maintenance signals:

ice-cube-ruby/ice_cube demonstrates active maintenance:

• The CHANGELOG shows recent additions, including support for BYSETPOS with all rule frequencies ([CHANGELOG.md:L8-L10]), indicating ongoing feature development
• The repository has a comprehensive CI/CD pipeline with automated testing, linting (using standardrb), and changelog enforcement ([.github/workflows/tests.yaml:L1-L40])
• The project maintains a dev container configuration for development consistency ([.devcontainer/devcontainer.json:L1-L27])
• The codebase is well-organized with multiple rule types, validations, parsers, and builders ([lib/ice_cube.rb:L4-L100])

Rails/rails is a much larger, more established project but the snippets shown here are from infrastructure components (ActionCable helpers, periodic timers, connection management, testing patterns) rather than core feature activity. These are more mature, stable components.

Key comparison:

• ice-cube-ruby/ice_cube (2,468 stars): Shows signs of active development with recent feature additions
• rails/rails: The snippets provided don't reveal recent activity signals—they appear to be stable, mature infrastructure code

However, the RepoPilot analysis for ice-cube-ruby/ice_cube explicitly states "Verdict: GO — Healthy across all four use cases", which is a strong positive signal for maintenance quality and reliability. Rails is too large to fully assess from these snippets alone.

For practical purposes: ice-cube-ruby/ice_cube appears to be actively maintained with clear governance (changelog enforcement, CI checks). Rails is a larger ecosystem with different maintenance patterns.

FOLLOW_UPS:

• What are ice-cube's recent version releases?
• How does ice-cube handle timezone considerations?
• What recurrence patterns does ice-cube support?