updated 2026-10-09 08:15 UTC

Open WebUI

Repository Website by open-webui

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

UI & App Builders Python Listed NOASSERTION

Is Open WebUI safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.9 / 10
Provenance Attested
Signed commits 74%
Last push today
Compare Open WebUI

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

Pick any agent to compare →
Suggest a correction

In detail: Open WebUI scores 84.9/100 (Grade A), ranked #92 of 1371 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.9/10; 74% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Open WebUI could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Open WebUI and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/open-webui/open-webui, NOASSERTION, last pushed 2026-10-09. 74% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.9/10 (scanned Sep 20, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review7
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 9
    Branch-Protection 3
    CI-Tests 5
    CII-Best-Practices 0
    Code-Review 7
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 9
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 5
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Partly attested

    • npm open-webui No source link declared No build attestation
    • PyPI open-webui Source link isn't a GitHub repo Build provenance attested

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Open WebUI.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues Open WebUI’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Open WebUI compares in UI & App Builders

  1. #1 Neo 89.5 +4.6
  2. #2 OpenUI 87.7 +2.8
  3. #3 Open WebUI 84.9 this agent
  4. #4 Tambo 80.8 −4.1
  5. #5 CopilotKit 80.8 −4.1

Bars show each HVTrust score; the tick marks Open WebUI’s 84.9.

Where the 84.9 comes from

HVTrust dimensions vs the UI & App Builders average

84.9 / 100 · 100.0% confidence

Open WebUI UI & App Builders average (18 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.6 / 25
8.0 above avg 10.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.2 above avg 12.8
Transparency50% declared license · 50% OSSF Scorecard
13.5 / 17
1.9 above avg 11.6
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.7 above avg 14.3
AdoptionLog-scaled stars · package downloads
19.4 / 20
7.5 above avg 11.9

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-10-03
Rank Moved
Rank rose 63 spots (#145 → #82)
2026-10-03
HVTrust Changed
HVTrust up 4.9pts (80.3 → 85.2)
2026-10-02
Rank Moved
Rank dropped 64 spots (#81 → #145)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.9/10. Tighten the weakest checks to improve public safety evidence.
Compare with Neo Get email alerts for Open WebUI View UI & App Builders Report missing data
100.0
Activity sub-score · out of 100
#3
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 →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
154.1k
Forks
22.5k
Last Push
2026-10-09
today
Commits (4 wk)
208
Downloads (7d)
159,317
npm+pypi
HN mentions (30d)
1
Open Issues
218
Rank Change
=
was #92

Analysis

Activity Inputs

100.0 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20

Common questions about Open WebUI

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.9/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?
74% 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
8 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
How this surface has changed

Detected changes to Open WebUI's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini

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
Rank 12HVTrust 10Grade 4Surface 1
2026-10-03
Rank Moved
Rank rose 63 spots (#145 → #82)
2026-10-03
HVTrust Changed
HVTrust up 4.9pts (80.3 → 85.2)
2026-10-02
Rank Moved
Rank dropped 64 spots (#81 → #145)
2026-10-02
HVTrust Changed
HVTrust down 5.0pts (85.3 → 80.3)
2026-10-01
Rank Moved
Rank rose 64 spots (#145 → #81)
2026-10-01
HVTrust Changed
HVTrust up 5.1pts (80.2 → 85.3)
2026-09-30
Rank Moved
Rank dropped 63 spots (#82 → #145)
2026-09-30
HVTrust Changed
HVTrust down 5.1pts (85.3 → 80.2)
2026-09-24
Rank Moved
Rank rose 63 spots (#141 → #78)
2026-09-24
HVTrust Changed
HVTrust up 5.3pts (80.0 → 85.3)
2026-09-23
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini
2026-09-23
Rank Moved
Rank dropped 82 spots (#59 → #141)
2026-09-23
HVTrust Changed
HVTrust down 3.5pts (83.5 → 80.0)
2026-09-21
Rank Moved
Rank rose 42 spots (#101 → #59)
2026-09-11
Grade Changed
Trust grade B → A
2026-09-11
Rank Moved
Rank rose 72 spots (#163 → #91)
2026-09-11
HVTrust Changed
HVTrust up 5.3pts (78.2 → 83.5)
2026-09-10
Grade Changed
Trust grade A → B
2026-09-10
Rank Moved
Rank dropped 73 spots (#90 → #163)
2026-09-10
HVTrust Changed
HVTrust down 5.4pts (83.6 → 78.2)
2026-09-09
Grade Changed
Trust grade B → A
2026-09-09
Rank Moved
Rank rose 64 spots (#154 → #90)
2026-09-09
HVTrust Changed
HVTrust up 5.2pts (78.4 → 83.6)
2026-09-08
Grade Changed
Trust grade A → B
2026-09-08
Rank Moved
Rank dropped 65 spots (#89 → #154)
2026-09-08
HVTrust Changed
HVTrust down 5.2pts (83.6 → 78.4)
2026-09-05
Rank Moved
Rank dropped 19 spots (#66 → #85)
GitHub → Website → PyPI: open-webui npm: open-webui

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 84.9 Grade A
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.4 · Raw JSON