Is Open WebUI safe to use?

Open WebUI has an HVTrust score of 83.4/100 (Grade A), ranked #60 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Open WebUI?

Open WebUI scores 83.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 149.8k GitHub stars and is categorized under UI & App Builders.

Open WebUI

open-webui/open-webui

User-friendly AI Interface (Supports Ollama, OpenAI API, ...)

UI & App Builders Python Grade A Listed NOASSERTION

83.4/100

Rank #60 of 1308

Compare Open WebUI

How does it stack up against its UI & App Builders neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-25 · 0d ago

Recent change

No recent signal change

Is Open WebUI safe? Open WebUI scores 83.4/100 (Grade A), ranked #60 of 1308 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.6/10; 48% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

#1 Neo — 88.3 (A) → #2 OpenUI — 86.7 (A) → #4 Tambo — 83.2 (A) → #5 LibreChat — 74.4 (B) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with Neo Get email alerts for Open WebUI View UI & App Builders Report missing data

100.0

Activity sub-score · out of 100

In UI & App Builders

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

149.8k

Forks

21.9k

Last Push

2026-08-25

today

Commits (4 wk)

215

Downloads (7d)

349,921

npm+pypi

HN mentions (30d)

Open Issues

156

Rank Change

was #60

Analysis

HVTrust Dimensions vs UI & App Builders

83.4 / 100 · 100.0% confidence

Open WebUI UI & App Builders average (17 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

16.9 / 25

6.8 above avg 10.1

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.5 above avg 12.5

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.4 above avg 11.9

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

4.2 above avg 15.8

AdoptionLog-scaled stars · package downloads

19.8 / 20

7.4 above avg 12.4

Activity Inputs

100.0 / 100

StarsRepository reach

30 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

20 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

5.6 / 10

OpenSSF Scorecard · scanned Aug 24, 2026

Signed Commits

48%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 3

CI-Tests 7

CII-Best-Practices 0

Code-Review 5

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 9

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Open WebUI safe?

Public supply-chain signals for Open WebUI are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Open WebUI carries less obvious unverified-evidence risk than projects with thin signals.

Does Open WebUI publish package provenance?

Yes. Open WebUI's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Open WebUI have an OpenSSF Scorecard?

Open WebUI has an OpenSSF Scorecard score of 5.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Open WebUI actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Open WebUI use?

Open WebUI ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Open WebUI's commits signed?

48% of the last 100 commits to Open WebUI are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Open WebUI head-to-head

Open WebUI vs Neo → Open WebUI vs OpenUI → Open WebUI vs Tambo →

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

9 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

2 tags

Broad capability areas detected.

browser
database

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Open WebUI?

For maintainers

HVTrust scores Open WebUI from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-06-02

Activity Score Changed

Activity score up 6pts (94 → 100)

2026-05-31

Activity Score Changed

Activity score down 6pts (100 → 94)

2026-05-29

HVTrust Changed

HVTrust up 9.9pts (76.1 → 86.0)

GitHub → PyPI: open-webui npm: open-webui

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/open-webui.svg)](https://hvtracker.net/agents/open-webui)
            
HTML:
            <a href="https://hvtracker.net/agents/open-webui"><img src="https://hvtracker.net/badge/open-webui.svg" alt="HVTrust"></a>

Other agents in UI & App Builders

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON