RegistryCompare › Cline vs Qwen Code

Cline vs Qwen Code

An independent, evidence-based trust comparison of Cline 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 89.5/100 (Grade A), a 1.3-point gap. Full breakdown below.
Signal Clinecline/cline Qwen CodeQwenLM/qwen-code
HVTrust score 89.5 90.8
Evidence grade A A
Coverage grade A A
Overall rank #8 #6
Rank in Coding Agents #3 #2
GitHub stars 64.5k 25.9k
Last updated today today
Build provenance Yes Yes
OSSF Scorecard 6.0 / 10 6.4 / 10
License Apache-2.0 Apache-2.0
Downloads 4.4M/wk 93k/wk
Trust dimensions (points earned)
Safety / integrity / 25 19.1 20.5
Identity & provenance / 20 18.0 18.0
Transparency / 17 13.6 13.9
Maintenance / 20 20.0 20.0
Adoption / 20 20.0 17.2
Runtime capability surface (full matrix)
MCP server Declared Implemented
External providers 4 — Amazon Bedrock, Anthropic, Google Gemini, … 3 — Anthropic, Google Gemini, OpenAI
Requires API keys No No
Plugin surface marketplace plugins
Provenance drift Match Match
Open in the live compare tool → Cline profile Qwen Code profile More Coding Agents →

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 →