Cherry Studio vs Neo
An independent, evidence-based trust comparison of Cherry Studio and Neo, two UI & App Builders projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Neo leads on trust — 89.8/100 (Grade A) vs 67.9/100 (Grade B), a 21.9-point gap. Full breakdown below.
| Signal | Cherry StudioCherryHQ/cherry-studio | Neoneomjs/neo |
|---|---|---|
| HVTrust score | 67.9 | 89.8 |
| Evidence grade | B | A |
| Coverage grade | C | B |
| Overall rank | #142 | #15 |
| Rank in UI & App Builders | #7 | #1 |
| GitHub stars | 52.0k | 3.3k |
| Last updated | today | today |
| Build provenance | No | Yes |
| OSSF Scorecard | 6.2 / 10 | 6.6 / 10 |
| License | AGPL-3.0 | MIT |
| Downloads | — | 3k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 12.8 | 20.7 |
| Identity & provenance / 18 | 10.8 | 18.0 |
| Transparency / 17 | 13.8 | 14.1 |
| Maintenance / 20 | 20.0 | 20.0 |
| Adoption / 20 | 11.3 | 13.1 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 6 — Anthropic, DeepSeek, Firecrawl, … | — |
| Requires API keys | No | No |
| Plugin surface | plugins | plugins |
| Provenance drift | — | 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 →