Neo vs Odysseus
An independent, evidence-based trust comparison of Neo and Odysseus, 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 — 90.0/100 (Grade A) vs 67.0/100 (Grade B), a 23.0-point gap. Full breakdown below.
| Signal | Neoneomjs/neo | Odysseuspewdiepie-archdaemon/odysseus |
|---|---|---|
| HVTrust score | 90.0 | 67.0 |
| Evidence grade | A | B |
| Coverage grade | B | B |
| Overall rank | #16 | #395 |
| Rank in UI & App Builders | #1 | #8 |
| GitHub stars | 3.3k | 87.4k |
| Last updated | today | 1d ago |
| Build provenance | Yes | No |
| OSSF Scorecard | 6.5 / 10 | 7.8 / 10 |
| License | MIT | AGPL-3.0 |
| Downloads | 6k/wk | — |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 20.6 | 13.8 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 14.0 | 15.1 |
| Maintenance / 20 | 20.0 | 17.0 |
| Adoption / 20 | 13.5 | 11.9 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Declared |
| External providers | — | 1 — Postgres |
| Requires API keys | No | Yes |
| 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 →