Which has better activity and maintenance signals?

Based on the repository data provided, I can compare the two repos on quantifiable signals:

google-gemini/gemini-cli shows stronger activity metrics:

• 106,280 stars and 14,360 forks — significantly higher community adoption
• Multiple active CI/CD workflows (CI, E2E chained tests) referenced in the README badges
• Active npm package distribution (@google/gemini-cli on npm)
• Multiple installation methods (npm, Homebrew, MacPorts, Anaconda) suggesting ongoing maintenance

honojs/hono signals:

• No star/fork counts provided in the repository_data block, so I cannot make a direct comparison on those metrics
• The code chunks show mature test suites [src/compose.test.ts, src/client/client.test.ts] with comprehensive coverage
• Active test infrastructure with mock server setups

Verdict: google-gemini/gemini-cli demonstrates stronger visible maintenance signals based on the explicit metrics available — 106k+ stars, active CI/CD, and multi-platform distribution. However, the repository_data block doesn't include corresponding stats for honojs/hono, so this is a partial comparison. For a complete assessment, I'd need honojs/hono's star count, contributor activity, and release frequency.

The gemini-cli README also emphasizes ongoing development (Gemini 3 models, recent feature additions like MCP support) and points to active documentation at geminicli.com.

FOLLOW_UPS:

• What's the release cadence for gemini-cli?
• Does honojs/hono have security advisories or CVEs?
• Which has more recent commits to main?