Dyad vs Neo
An independent, evidence-based trust comparison of Dyad 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 — 85.9/100 (Grade A) vs 61.4/100 (Grade C), a 24.5-point gap. Full breakdown below.
| Signal | Dyaddyad-sh/dyad | Neoneomjs/neo |
|---|---|---|
| HVTrust score | 61.4 | 85.9 |
| Evidence grade | C | A |
| Coverage grade | C | B |
| Overall rank | #202 | #34 |
| Rank in UI & App Builders | #8 | #2 |
| GitHub stars | 21.1k | 3.2k |
| Last updated | today | today |
| Build provenance | No | Yes |
| OSSF Scorecard | 3.9 / 10 | 6.0 / 10 |
| License | NOASSERTION | MIT |
| Downloads | — | 5k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 9.9 | 18.9 |
| Identity & provenance / 18 | 10.8 | 18.0 |
| Transparency / 17 | 11.8 | 13.6 |
| Maintenance / 20 | 20.0 | 20.0 |
| Adoption / 20 | 10.4 | 13.4 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 5 — Amazon Bedrock, Anthropic, OpenAI, … | 3 — Anthropic, Google Gemini, OpenAI |
| Requires API keys | No | No |
| Plugin surface | — | 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.2 →