ECC vs Gemini CLI
An independent, evidence-based trust comparison of ECC and Gemini CLI, two Coding Agents projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
ECC leads on trust — 88.1/100 (Grade A) vs 76.7/100 (Grade B), a 11.4-point gap. Note: ECC's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types. Full breakdown below.
| Signal | ECCaffaan-m/ECC | Gemini CLIgoogle-gemini/gemini-cli |
|---|---|---|
| HVTrust score | 88.1 | 76.7 |
| Evidence grade | A | B |
| Coverage grade | B | A |
| Overall rank | #22 | #79 |
| Rank in Coding Agents | #4 | #9 |
| GitHub stars | 239.5k | 106.5k |
| Last updated | today | today |
| Build provenance | Yes | No |
| OSSF Scorecard | 5.9 / 10 | 4.7 / 10 |
| License | MIT | Apache-2.0 |
| Downloads | 5k/wk | 595k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 19.2 | 10.9 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 13.5 | 12.5 |
| Maintenance / 20 | 20.0 | 19.2 |
| Adoption / 20 | 17.8 | 19.8 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 4 — Anthropic, OpenAI, Postgres, … | 1 — Google Gemini |
| Requires API keys | Yes | Yes |
| Plugin surface | marketplace | extensions |
| Provenance drift | Match | Match |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.3 →