Yao has an HVTrust score of 53.5/100 (Grade C), ranked #290 of 468 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Yao?

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

Yao

YaoApp/yao

✨ Build AI agents and web apps — with a single binary.

UI & App Builders Go Grade C Listed NOASSERTION

53.5/100

Rank #290 of 468

Compare Yao

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-03 · 3d ago

Recent change

No recent signal change

Is Yao safe? Yao scores 53.5/100 (Grade C), ranked #290 of 468 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.4/10; 15% of recent commits are signed; last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

#9 ToolJet — 60.5 (C) → #10 Eigent — 57.8 (C) → #12 Srcbook — 51.2 (C) → #13 CopilotKit — 49.9 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-07-29

Rank Moved

Rank dropped 10 spots (#284 → #294)

2026-07-15

Rank Moved

Rank dropped 14 spots (#253 → #267)

2026-07-14

Rank Moved

Rank dropped 14 spots (#239 → #253)

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

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

Compare with another agent Get email alerts for Yao View UI & App Builders Report missing data

80.7

Activity sub-score · out of 100

#11

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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars

7.6k

Forks

685

Last Push

2026-08-03

3 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #293

Analysis

HVTrust Dimensions vs UI & App Builders

53.5 / 100 · 100.0% confidence

Yao UI & App Builders average (15 agents)

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

5.0 / 25

6.3 below avg 11.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.9 below avg 12.7

Transparency50% declared license · 50% OSSF Scorecard

11.4 / 17

0.9 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

18.1 / 20

1.1 above avg 17.0

AdoptionLog-scaled stars · package downloads

9.3 / 20

3.7 below avg 13.0

Activity Inputs

80.7 / 100

StarsRepository reach

23.3 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

19.6 / 25

CommunityFork signal

13.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.4 / 10

OpenSSF Scorecard · scanned Aug 5, 2026

Signed Commits

15%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 9

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Yao safe?

Public trust evidence for Yao is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Yao publish package provenance?

No published build provenance is currently detected for Yao. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Yao have an OpenSSF Scorecard?

Yao has an OpenSSF Scorecard score of 3.4/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 Yao actively maintained?

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

What license does Yao use?

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

Are Yao's commits signed?

15% of the last 100 commits to Yao 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.

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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

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

Maintain Yao?

For maintainers

HVTrust scores Yao 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-07-29

Rank Moved

Rank dropped 10 spots (#284 → #294)

2026-07-15

Rank Moved

Rank dropped 14 spots (#253 → #267)

2026-07-14

Rank Moved

Rank dropped 14 spots (#239 → #253)

2026-07-13

Rank Moved

Rank dropped 28 spots (#211 → #239)

2026-06-24

Rank Moved

Rank dropped 25 spots (#183 → #208)

2026-06-23

Scorecard Added

OSSF Scorecard: 3.4/10

2026-06-23

Grade Changed

Trust grade D → C

2026-06-23

Rank Moved

Rank rose 93 spots (#276 → #183)

2026-06-23

HVTrust Changed

HVTrust up 32.7pts (22.4 → 55.1)

2026-06-23

Activity Score Changed

Activity score up 9pts (73 → 82)

2026-06-21

Newly Listed

First tracked at rank #273

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in UI & App Builders

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