LibreChat vs Neo
An independent, evidence-based trust comparison of LibreChat 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 — 88.3/100 (Grade A) vs 74.4/100 (Grade B), a 13.9-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 | LibreChatdanny-avila/LibreChat | Neoneomjs/neo |
|---|---|---|
| HVTrust score | 74.4 | 88.3 |
| Evidence grade | B | A |
| Coverage grade | A | B |
| Overall rank | #91 | #23 |
| Rank in UI & App Builders | #5 | #1 |
| GitHub stars | 42.1k | 3.3k |
| Last updated | today | today |
| Build provenance | No | Yes |
| OSSF Scorecard | 5.8 / 10 | 5.9 / 10 |
| License | MIT | MIT |
| Downloads | 182k/wk | 5k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 12.2 | 18.8 |
| Identity & provenance / 18 | 10.8 | 18.0 |
| Transparency / 17 | 13.4 | 13.5 |
| Maintenance / 20 | 20.0 | 20.0 |
| Adoption / 20 | 18.1 | 13.4 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 4 — Anthropic, Google Gemini, OpenAI, … | — |
| 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 →