How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-08 18:04 UTC·Repo last pushed today
Activity & Reach
Stars
6.8k
Forks
504
Last Push
2026-06-08
today
Commits (4 wk)
43
Downloads (7d)
10,758
npm
HN mentions (30d)
—
Open Issues
65
Rank Change
NEW
Analysis
HVTrust Dimensions
72.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.5 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
18.6 / 20
AdoptionStars and downloads
14.6 / 20
Activity Inputs
81.1 / 100
StarsRepository reach
23.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
20.5 / 25
CommunityFork signal
12.6 / 20
Supply Chain Trust
Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
100%
of last 100 commits verified
Is OpenUI safe?
OpenUI has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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?
No OpenSSF Scorecard data is currently published for OpenUI. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
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.
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
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
high confidence
Declared
Declared plugin/integration surface detected.
code
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?
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.2 · Raw JSON
