Is OpenUI safe to use?

OpenUI has an HVTrust score of 86.7/100 (Grade A), ranked #27 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for OpenUI?

OpenUI scores 86.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 8.3k GitHub stars and is categorized under UI & App Builders.

OpenUI

thesysdev/openui

The Open Standard for Generative UI

UI & App Builders TypeScript Grade A Listed MIT

86.7/100

Rank #27 of 1204

Compare OpenUI

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 B · 3/5 signals

Last push

2026-08-08 · 1d ago

Recent change

Tool Surface Changed

Is OpenUI safe? OpenUI scores 86.7/100 (Grade A), ranked #27 of 1204 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; last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

#1 Neo — 88.1 (A) → #3 Tambo — 83.6 (A) → #4 Open WebUI — 83.4 (A) → #5 LibreChat — 74.2 (B) →

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

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

86.3

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 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 →

Activity & Reach

Stars

8.3k

Forks

607

Last Push

2026-08-08

yesterday

Commits (4 wk)

136

Downloads (7d)

11,350

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #29

Analysis

HVTrust Dimensions vs UI & App Builders

86.7 / 100 · 100.0% confidence

OpenUI UI & App Builders average (17 agents)

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

19.0 / 25

8.9 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

12.9 / 17

1.0 above avg 11.9

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

4.0 above avg 15.9

AdoptionLog-scaled stars · package downloads

14.8 / 20

2.4 above avg 12.4

Activity Inputs

86.3 / 100

StarsRepository reach

23.5 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

12.9 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.2 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

100%

of last 100 commits verified

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

Is OpenUI safe?

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 1 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 Tambo → OpenUI vs Open WebUI →

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

1 detected

Public provider/service dependencies detected.

OpenAI

Credential signal: API keys or service config markers documented.

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

How this surface has changed

Detected changes to OpenUI'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-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

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

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-06-10

Scorecard Added

OSSF Scorecard: 5.4/10

2026-06-10

Grade Changed

Trust grade B → A

2026-06-10

Rank Moved

Rank rose 31 spots (#63 → #32)

2026-06-10

HVTrust Changed

HVTrust up 11.5pts (72.1 → 83.6)

2026-06-08

Newly Listed

First tracked at rank #63

GitHub → npm: @openuidev/react-ui

Embed Badge Badge guide for maintainers →

For maintainers

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.2 · Raw JSON