RegistryCompare › oh-my-pi vs Qwen Code

oh-my-pi vs Qwen Code

An independent, evidence-based trust comparison of oh-my-pi 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 82.5/100 (Grade A), a 8.3-point gap. Full breakdown below.
Signal oh-my-pican1357/oh-my-pi Qwen CodeQwenLM/qwen-code
HVTrust score 82.5 90.8
Evidence grade A A
Coverage grade B A
Overall rank #52 #6
Rank in Coding Agents #6 #2
GitHub stars 21.8k 26.7k
Last updated today today
Build provenance Yes Yes
OSSF Scorecard 4.5 / 10 6.4 / 10
License MIT Apache-2.0
Downloads 84k/wk 93k/wk
Trust dimensions (points earned)
Safety / integrity / 25 16.8 20.5
Identity & provenance / 18 18.0 18.0
Transparency / 17 12.3 13.9
Maintenance / 20 20.0 20.0
Adoption / 20 17.0 17.2
Runtime capability surface (full matrix)
MCP server Declared Implemented
External providers 6 — Anthropic, Firecrawl, OpenAI, … 3 — Anthropic, Google Gemini, OpenAI
Requires API keys Yes No
Plugin surface marketplace plugins
Provenance drift Match Match
Open in the live compare tool → oh-my-pi 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 →