Neo vs Open WebUI
An independent, evidence-based trust comparison of Neo and Open WebUI, 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 — 87.9/100 (Grade A) vs 83.3/100 (Grade A), a 4.6-point gap. Note: Neo's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types. Full breakdown below.
| Signal | Neoneomjs/neo | Open WebUIopen-webui/open-webui |
|---|---|---|
| HVTrust score | 87.9 | 83.3 |
| Evidence grade | A | A |
| Coverage grade | B | A |
| Overall rank | #24 | #61 |
| Rank in UI & App Builders | #1 | #4 |
| GitHub stars | 3.3k | 148.8k |
| Last updated | 1d ago | 1d ago |
| Build provenance | Yes | Yes |
| OSSF Scorecard | 5.7 / 10 | 5.6 / 10 |
| License | MIT | NOASSERTION |
| Downloads | 5k/wk | 350k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 18.5 | 16.9 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 13.3 | 13.3 |
| Maintenance / 20 | 19.9 | 19.9 |
| Adoption / 20 | 13.4 | 19.8 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | — |
| External providers | — | 9 — Amazon Bedrock, Anthropic, Google Gemini, … |
| Requires API keys | No | Yes |
| Plugin surface | plugins | — |
| Provenance drift | Match | Unknown |
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 →