updated 2026-10-21 20:07 UTC

OpenUI

Repository Website

The Open Standard for Generative UI

UI & App Builders TypeScript Listed MIT

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

OSSF Scorecard 5.2 / 10
Provenance Attested
Signed commits 100%
Last push 2d ago
Advisories None known
Compare OpenUI

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

Pick any agent to compare →
Suggest a correction

In detail: OpenUI scores 88.7/100 (Grade A), ranked #44 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.2/10; 100% of recent commits are signed; no published advisory affects its latest release (@openuidev/react-ui); last pushed 2026-10-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenUI 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 OpenUI 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 Signed

    github.com/thesysdev/openui, MIT, last pushed 2026-10-19. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.2/10 (scanned Oct 17, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @openuidev/react-ui 0.18.1. No published advisory affects it (OSV, checked 2026-10-21).

Changes to this chain

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

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues OpenUI’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 OpenUI compares in UI & App Builders

  1. #1 OpenUI 88.7 this agent
  2. #2 Neo 87.6 −1.1
  3. #3 Open WebUI 83.5 −5.2
  4. #4 CopilotKit 80.2 −8.5
  5. #5 Tambo 79.8 −8.9

Bars show each HVTrust score; the tick marks OpenUI’s 88.7.

Where the 88.7 comes from

HVTrust dimensions vs the UI & App Builders average

88.7 / 100 · 100.0% confidence

OpenUI UI & App Builders average (18 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.0 / 25
7.9 above avg 11.1
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.2 above avg 12.8
Transparency50% declared license · 50% OSSF Scorecard
12.9 / 17
0.7 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
4.3 above avg 15.6
AdoptionLog-scaled stars · package downloads
16.1 / 20
3.8 above avg 12.3

Quick Trust Read

What Would Improve It
Improve transparency to lift the weakest part of the trust profile.
Recent Changes
2026-10-15
Rank Moved
Rank rose 11 spots (#51 → #40)
2026-09-23
Rank Moved
Rank dropped 12 spots (#35 → #47)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.2/10. Tighten the weakest checks to improve public safety evidence.
Compare with Neo Get email alerts for OpenUI View UI & App Builders Report missing data
88.1
Activity sub-score · out of 100
#1
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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-21 20:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-21

Activity & Reach

Stars
12.9k
Forks
867
Last Push
2026-10-19
2 days ago
Commits (4 wk)
117
Downloads (7d)
44,275
npm
HN mentions (30d)
—
Open Issues
66
Rank Change
▼2
was #42

Analysis

Activity Inputs

88.1 / 100
StarsRepository reach
24.7 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.7 / 20

Common questions about OpenUI

Public supply-chain signals for OpenUI are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but OpenUI carries less obvious unverified-evidence risk than projects with thin signals.
Does OpenUI publish package provenance?
Yes. OpenUI's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does OpenUI have an OpenSSF Scorecard?
OpenUI has an OpenSSF Scorecard score of 5.2/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 OpenUI actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does OpenUI use?
OpenUI ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenUI's commits signed?
100% of the last 100 commits to OpenUI 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 OpenUI head-to-head

OpenUI vs Neo → OpenUI vs Open WebUI → OpenUI vs CopilotKit →

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
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain OpenUI?

For maintainers

HVTrust scores OpenUI 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 2
2026-10-15
Rank Moved
Rank rose 11 spots (#51 → #40)
2026-09-23
Rank Moved
Rank dropped 12 spots (#35 → #47)
GitHub → Website → npm: @openuidev/react-ui

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 88.7 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/openui.svg)](https://hvtracker.net/agents/openui)
HTML:
<a href="https://hvtracker.net/agents/openui"><img src="https://hvtracker.net/badge/openui.svg" alt="HVTrust"></a>

Other agents in UI & App Builders

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