AG-UI

AG-UI: the Agent-User Interaction Protocol. Bring Agents into Frontend Applications.

Protocols & Tool Integration Python Grade C Listed MIT
63.6/100
Rank #243 of 1283
Compare AG-UI

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-15 · 0d ago
Recent change
Rank +7

Is AG-UI safe? AG-UI scores 63.6/100 (Grade C), ranked #243 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 6.4/10; 34% of recent commits are signed; last pushed 2026-08-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-15
Rank Moved
Rank rose 22 spots (#265 → #243)
2026-08-14
Rank Moved
Rank dropped 30 spots (#235 → #265)
2026-08-13
Rank Moved
Rank dropped 16 spots (#219 → #235)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.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.
89.7
Activity sub-score · out of 100
#23

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 →

Signals refreshed 2026-08-15 10:46 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars
15.3k
Forks
1.4k
Last Push
2026-08-15
today
Commits (4 wk)
486
Downloads (7d)
HN mentions (30d)
Open Issues
185
Rank Change
▲22
was #265

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

63.6 / 100 · 100.0% confidence

AG-UI Protocols & Tool Integration average (57 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.7 / 25
1.1 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.9 / 17
2.5 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.0 / 20
in line with avg 10.4

Activity Inputs

89.7 / 100
StarsRepository reach
25.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.4 / 10
OpenSSF Scorecard · scanned Aug 14, 2026
Signed Commits
34%
of last 100 commits verified
Binary-Artifacts 4
Branch-Protection 6
CI-Tests 10
CII-Best-Practices 0
Code-Review 8
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 9
SAST 1
Security-Policy 0
Signed-Releases -1
Token-Permissions 9
Vulnerabilities 0

Is AG-UI safe?

AG-UI 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 AG-UI publish package provenance?
No published build provenance is currently detected for AG-UI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does AG-UI have an OpenSSF Scorecard?
AG-UI has an OpenSSF Scorecard score of 6.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 AG-UI actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does AG-UI use?
AG-UI ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are AG-UI's commits signed?
34% of the last 100 commits to AG-UI 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
None detected
No MCP server signal detected.
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 AG-UI?

For maintainers

HVTrust scores AG-UI 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.

Reputation Timeline

Signal history
Rank 7Grade 4Listed 1
2026-08-15
Rank Moved
Rank rose 22 spots (#265 → #243)
2026-08-14
Rank Moved
Rank dropped 30 spots (#235 → #265)
2026-08-13
Rank Moved
Rank dropped 16 spots (#219 → #235)
2026-08-12
Grade Changed
Trust grade B → C
2026-08-12
Rank Moved
Rank rose 11 spots (#230 → #219)
2026-08-10
Grade Changed
Trust grade C → B
2026-08-10
Rank Moved
Rank dropped 11 spots (#214 → #225)
2026-08-08
Rank Moved
Rank dropped 41 spots (#170 → #211)
2026-08-04
Grade Changed
Trust grade C → B
2026-07-29
Grade Changed
Trust grade B → C
2026-07-29
Rank Moved
Rank dropped 23 spots (#140 → #163)
2026-07-28
Newly Listed
First tracked at rank #140

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.6 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/ag-ui.svg)](https://hvtracker.net/agents/ag-ui)
HTML:
<a href="https://hvtracker.net/agents/ag-ui"><img src="https://hvtracker.net/badge/ag-ui.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