RepoPilot

google-gemini/gemini-cli vs honojs/hono

Both showing Healthy signals — pick on fit, not health

As of September 2026, gemini-cli and hono both show healthy maintenance signals. gemini-cli was committed to today with 17+ active contributors, while hono was committed to 1 week ago with 27+ active contributors. gemini-cli is Apache-2.0-licensed while hono is MIT-licensed. Neither has known critical or high-severity CVEs in its dependency tree.

Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.

google-gemini/gemini-cli

Healthy

Strong maintenance signals

MixedDependency

dependency CVE scan unavailable

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; dependency CVE scan unavailable

  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 17 active contributors
  • Distributed ownership (top contributor 20% of recent commits)
  • Apache-2.0 licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

honojs/hono

Healthy

Strong maintenance signals

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; 8 cyclic import chains — pervasive coupling

  • Scorecard: default branch unprotected (0/10)
  • In RepoPilot's curated trusted-corpus (29 projects)
  • Last commit 1d ago
  • 27+ active contributors
  • Distributed ownership (top contributor 36% of recent commits)
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

gemini-clihono
Stars106,96932,112
Last committoday8d ago
LicenseApache-2.0MIT
Open issues828390
Has tests
Has CI
Test coverage76%61%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeCC
Cycles08
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? google-gemini/gemini-cli · honojs/hono

Ask AI about google-gemini/gemini-cli vs honojs/hono

Open the chat with a comparison question pre-filled.