A2UI has an HVTrust score of 64.1/100 (Grade C), ranked #248 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for A2UI?

A2UI scores 64.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 16.1k GitHub stars and is categorized under Protocols & Tool Integration.

A2UI

a2ui-project/a2ui

Protocols & Tool Integration TypeScript Grade C Listed Apache-2.0

64.1/100

Rank #248 of 1283

Compare A2UI

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-11 · 0d ago

Recent change

Rank +2

Is A2UI safe? A2UI scores 64.1/100 (Grade C), ranked #248 of 1283 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 5.8/10; 100% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#20 Agent Gateway — 65.2 (B) → #21 Model Context Protocol / MCP — 64.2 (C) → #23 mcp-use — 63.9 (C) → #24 n8n-MCP — 62.6 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-10

Rank Moved

Rank dropped 12 spots (#235 → #247)

2026-08-08

Rank Moved

Rank dropped 44 spots (#185 → #229)

2026-08-07

Scorecard Added

OSSF Scorecard: 5.8/10

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.8/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.

Compare with another agent Get email alerts for A2UI View Protocols & Tool Integration Report missing data

89.6

Activity sub-score · out of 100

#22

In Protocols & Tool Integration

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 →

Activity & Reach

Stars

16.1k

Forks

1.3k

Last Push

2026-08-11

today

Commits (4 wk)

109

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

229

Rank Change

▼1

was #247

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

64.1 / 100 · 100.0% confidence

A2UI Protocols & Tool Integration average (57 agents)

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

12.2 / 25

3.6 above avg 8.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

13.4 / 17

2.0 above avg 11.4

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

6.2 above avg 13.8

AdoptionLog-scaled stars · package downloads

10.1 / 20

in line with avg 10.4

Activity Inputs

89.6 / 100

StarsRepository reach

25.2 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.8 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 7

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is A2UI safe?

A2UI 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 A2UI publish package provenance?

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

Does A2UI have an OpenSSF Scorecard?

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

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

What license does A2UI use?

A2UI ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are A2UI's commits signed?

100% of the last 100 commits to A2UI 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: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration surface detected.

browser

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 A2UI?

For maintainers

HVTrust scores A2UI 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-10

Rank Moved

Rank dropped 12 spots (#235 → #247)

2026-08-08

Rank Moved

Rank dropped 44 spots (#185 → #229)

2026-08-07

Scorecard Added

OSSF Scorecard: 5.8/10

2026-07-29

Rank Moved

Rank dropped 10 spots (#415 → #425)

2026-07-28

Newly Listed

First tracked at rank #415

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Protocols & Tool Integration

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