ECC vs Qwen Code
An independent, evidence-based trust comparison of ECC and Qwen Code, two Coding Agents projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Qwen Code leads on trust — 90.8/100 (Grade A) vs 87.1/100 (Grade A), a 3.7-point gap. Full breakdown below.
| Signal | ECCaffaan-m/ECC | Qwen CodeQwenLM/qwen-code |
|---|---|---|
| HVTrust score | 87.1 | 90.8 |
| Evidence grade | A | A |
| Coverage grade | B | A |
| Overall rank | #23 | #6 |
| Rank in Coding Agents | #4 | #2 |
| GitHub stars | 237.7k | 26.7k |
| Last updated | today | today |
| Build provenance | Yes | Yes |
| OSSF Scorecard | 5.4 / 10 | 6.4 / 10 |
| License | MIT | Apache-2.0 |
| Downloads | 4k/wk | 93k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 18.4 | 20.5 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 13.1 | 13.9 |
| Maintenance / 20 | 19.8 | 20.0 |
| Adoption / 20 | 17.7 | 17.2 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 4 — Anthropic, OpenAI, Postgres, … | 3 — Anthropic, Google Gemini, OpenAI |
| Requires API keys | Yes | No |
| Plugin surface | marketplace | plugins |
| 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.2 →