Which has better activity and maintenance signals?

Based on the repository data provided, honojs/hono shows stronger activity and maintenance signals:

honojs/hono:

• 31,527 stars, 1,196 forks — significantly larger community
• GitHub commit activity badge — explicitly tracked in CI/CD workflow
• GitHub last commit badge — recent activity monitored
• codecov badge — active code coverage tracking
• CI/CD pipeline — GitHub Actions workflow status badge indicates continuous integration
• Active npm/JSR publishing — dual distribution channels (npm + JSR)

ruvnet/ruflo: The repository data provided is much more limited, but shows:

• ADR-based (Architecture Decision Records) development — indicates deliberate design processes
• Plugin architecture with multiple skill modules — organized structure
• No star/fork/activity metrics included in the data block

The honojs/hono data explicitly includes multiple GitHub workflow badges and metrics (last commit, commit activity, codecov, CI status) that signal continuous maintenance. The ruvnet/ruflo data focuses on internal documentation (ADRs, skills, agents) rather than public-facing activity metrics.

However, the repository_data block for ruflo is limited — a full assessment would require checking its GitHub page directly for stats like star count, recent commits, and CI/CD status, which aren't included here.

FOLLOW_UPS:

• What's the architecture grade or import complexity of each repo?
• Does honojs/hono have any open CVEs in dependencies?
• What's ruvnet/ruflo's primary use case compared to Hono?