updated 2026-10-09 12:08 UTC

UI-TARS

Repository by bytedance

Pioneering Automated GUI Interaction with Native Agents

Browser & Computer Use Python Listed Apache-2.0

Is UI-TARS safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.5 / 10
Provenance None
Signed commits 19%
Last push 255d ago
Advisories None known
Compare UI-TARS

How does it stack up against its Browser & Computer Use neighbours?

Pick any agent to compare →
Suggest a correction

In detail: UI-TARS scores 41.0/100 (Grade D), ranked #1172 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.5/10; 19% of recent commits are signed; no published advisory affects its latest release (ui-tars); last pushed 2026-01-27. Every point is earned from checkable signals — never paid placement. How scoring works →

How UI-TARS could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships UI-TARS and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/bytedance/UI-TARS, Apache-2.0, last pushed 2026-01-27. 19% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.5/10 (scanned Oct 6, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 1
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Not linked

    • PyPI ui-tars Source link isn't a GitHub repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: ui-tars 0.5.1. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of UI-TARS.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues UI-TARS’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How UI-TARS compares in Browser & Computer Use

  1. #35 OmniParser 44.9 +3.9
  2. #36 MolmoWeb 41.5 +0.5
  3. #37 UI-TARS 41.0 this agent
  4. #38 Understudy 35.0 −6.0
  5. #39 Agent-E 34.8 −6.2

Bars show each HVTrust score; the tick marks UI-TARS’s 41.0.

Where the 41.0 comes from

HVTrust dimensions vs the Browser & Computer Use average

41.0 / 100 · 100.0% confidence

UI-TARS Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.1 / 25
5.7 below avg 9.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.8 below avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
10.6 / 17
1.3 below avg 11.9
Maintenance60% last-push freshness · 40% commit activity
0 / 20
13.0 below avg 13.0
AdoptionLog-scaled stars · package downloads
15.5 / 20
4.3 above avg 11.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 10 spots (#1162 → #1172)
2026-09-23
Rank Moved
Rank dropped 643 spots (#505 → #1148)
2026-09-22
Rank Moved
Rank dropped 119 spots (#386 → #505)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.5/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.
Refresh maintenance signals The repo was last pushed 255 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for UI-TARS View Browser & Computer Use Report missing data
38.1
Activity sub-score · out of 100
#37
In Browser & Computer Use

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-09 12:08 UTC · Repo last pushed 255 days ago — may be stale

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
11.6k
Forks
885
Last Push
2026-01-27
255 days ago
Commits (4 wk)
0
Downloads (7d)
19,151
pypi
HN mentions (30d)
0
Open Issues
44
Rank Change
▼10
was #1162

Analysis

Activity Inputs

38.1 / 100
StarsRepository reach
24.4 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.7 / 20

Common questions about UI-TARS

Public trust evidence for UI-TARS 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 UI-TARS publish package provenance?
No published build provenance is currently detected for UI-TARS. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does UI-TARS have an OpenSSF Scorecard?
UI-TARS has an OpenSSF Scorecard score of 2.5/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 UI-TARS actively maintained?
Stale. The repository has not been pushed to in 255 days. Consider whether the project is still being maintained.
What license does UI-TARS use?
UI-TARS ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are UI-TARS's commits signed?
19% of the last 100 commits to UI-TARS 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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 UI-TARS'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-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain UI-TARS?

For maintainers

HVTrust scores UI-TARS 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
Rank 27Surface 1
2026-10-09
Rank Moved
Rank dropped 10 spots (#1162 → #1172)
2026-09-23
Rank Moved
Rank dropped 643 spots (#505 → #1148)
2026-09-22
Rank Moved
Rank dropped 119 spots (#386 → #505)
2026-09-21
Rank Moved
Rank rose 765 spots (#1151 → #386)
2026-09-19
Rank Moved
Rank rose 16 spots (#1165 → #1149)
2026-09-09
Rank Moved
Rank dropped 13 spots (#1151 → #1164)
2026-09-07
Rank Moved
Rank dropped 13 spots (#1129 → #1142)
2026-09-06
Rank Moved
Rank dropped 28 spots (#1101 → #1129)
2026-09-05
Rank Moved
Rank dropped 38 spots (#1063 → #1101)
2026-09-04
Rank Moved
Rank dropped 26 spots (#1037 → #1063)
2026-09-03
Rank Moved
Rank dropped 56 spots (#981 → #1037)
2026-09-02
Rank Moved
Rank dropped 56 spots (#925 → #981)
2026-09-01
Rank Moved
Rank dropped 35 spots (#890 → #925)
2026-08-31
Rank Moved
Rank dropped 30 spots (#860 → #890)
2026-08-30
Rank Moved
Rank dropped 42 spots (#818 → #860)
2026-08-29
Rank Moved
Rank dropped 42 spots (#776 → #818)
2026-08-28
Rank Moved
Rank dropped 25 spots (#751 → #776)
2026-08-27
Rank Moved
Rank dropped 21 spots (#730 → #751)
2026-08-26
Rank Moved
Rank dropped 97 spots (#633 → #730)
2026-08-24
Rank Moved
Rank rose 15 spots (#652 → #637)
2026-08-16
Rank Moved
Rank dropped 15 spots (#634 → #649)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-10
Rank Moved
Rank dropped 26 spots (#623 → #649)
2026-08-08
Rank Moved
Rank dropped 222 spots (#398 → #620)
2026-07-29
Rank Moved
Rank dropped 10 spots (#373 → #383)
2026-07-15
Rank Moved
Rank dropped 25 spots (#337 → #362)
2026-07-14
Rank Moved
Rank dropped 19 spots (#318 → #337)
2026-07-13
Rank Moved
Rank dropped 36 spots (#282 → #318)
GitHub → PyPI: ui-tars

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 41.0 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/ui-tars.svg)](https://hvtracker.net/agents/ui-tars)
HTML:
<a href="https://hvtracker.net/agents/ui-tars"><img src="https://hvtracker.net/badge/ui-tars.svg" alt="HVTrust"></a>

Other agents in Browser & Computer Use

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON