UI-TARS Desktop

The Open-Source Multimodal AI Agent Stack: Connecting Cutting-Edge AI Models and Agent Infra

Browser & Computer Use TypeScript Listed Apache-2.0

Is UI-TARS Desktop safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.9 / 10
Provenance None
Signed commits 100%
Last push today
Compare UI-TARS Desktop

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

Pick any agent to compare →
Suggest a correction

In detail: UI-TARS Desktop scores 60.7/100 (Grade C), ranked #630 of 1371 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.9/10; 100% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How UI-TARS Desktop 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.

Chain of custody

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

  1. Source Signed

    github.com/bytedance/UI-TARS-desktop, Apache-2.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review10
    • Branch Protectionn/a
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies4
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection -1
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 4
    SAST 7
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages None

    No registry package. UI-TARS Desktop is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

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

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues UI-TARS Desktop’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.

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 Desktop compares in Browser & Computer Use

  1. #16 AIHawk 61.1 +0.4
  2. #17 UFO 60.8 +0.1
  3. #18 UI-TARS Desktop 60.7 this agent
  4. #19 arbigent 58.9 −1.8
  5. #20 ARTEMIS 58.4 −2.3

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

Where the 60.7 comes from

HVTrust dimensions vs the Browser & Computer Use average

60.7 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.4 / 25
3.1 above avg 9.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.6 below avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
13.5 / 17
2.1 above avg 11.4
Maintenance60% last-push freshness · 40% commit activity
13.9 / 20
1.7 above avg 12.2
AdoptionLog-scaled stars · package downloads
11.0 / 20
in line with avg 10.7

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 rose 67 spots (#697 → #630)
2026-10-07
Rank Moved
Rank dropped 64 spots (#642 → #706)
2026-10-06
Rank Moved
Rank rose 37 spots (#679 → #642)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.9/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.
81.2
Activity sub-score · out of 100
#18

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-10-09 08:15 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
39.2k
Forks
4.0k
Last Push
2026-10-09
today
Commits (4 wk)
8?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
350
Rank Change
▲67
was #697

Analysis

Activity Inputs

81.2 / 100
StarsRepository reach
27.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
16.7 / 20

Common questions about UI-TARS Desktop

UI-TARS Desktop 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 UI-TARS Desktop publish package provenance?
No published build provenance is currently detected for UI-TARS Desktop. 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 Desktop have an OpenSSF Scorecard?
UI-TARS Desktop has an OpenSSF Scorecard score of 5.9/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 Desktop actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does UI-TARS Desktop use?
UI-TARS Desktop ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are UI-TARS Desktop's commits signed?
100% of the last 100 commits to UI-TARS Desktop 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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • filesystem
  • shell
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 UI-TARS Desktop?

For maintainers

HVTrust scores UI-TARS Desktop 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 32Score 2
2026-10-09
Rank Moved
Rank rose 67 spots (#697 → #630)
2026-10-07
Rank Moved
Rank dropped 64 spots (#642 → #706)
2026-10-06
Rank Moved
Rank rose 37 spots (#679 → #642)
2026-10-03
Rank Moved
Rank rose 33 spots (#705 → #672)
2026-09-27
Rank Moved
Rank rose 10 spots (#699 → #689)
2026-09-24
Rank Moved
Rank rose 73 spots (#764 → #691)
2026-09-24
Activity Score Changed
Activity score up 11pts (68 → 79)
2026-09-23
Rank Moved
Rank dropped 481 spots (#283 → #764)
2026-09-21
Rank Moved
Rank rose 467 spots (#745 → #278)
2026-09-15
Rank Moved
Rank dropped 11 spots (#729 → #740)
2026-09-11
Rank Moved
Rank rose 75 spots (#794 → #719)
2026-09-11
Activity Score Changed
Activity score up 5pts (64 → 69)
2026-09-09
Rank Moved
Rank dropped 11 spots (#781 → #792)
2026-09-07
Rank Moved
Rank dropped 43 spots (#729 → #772)
2026-09-06
Rank Moved
Rank dropped 11 spots (#718 → #729)
2026-09-05
Rank Moved
Rank dropped 74 spots (#644 → #718)
2026-09-04
Rank Moved
Rank dropped 26 spots (#618 → #644)
2026-09-03
Rank Moved
Rank dropped 32 spots (#586 → #618)
2026-09-02
Rank Moved
Rank dropped 28 spots (#558 → #586)
2026-09-01
Rank Moved
Rank dropped 17 spots (#541 → #558)
2026-08-31
Rank Moved
Rank dropped 30 spots (#511 → #541)
2026-08-29
Rank Moved
Rank dropped 28 spots (#486 → #514)
2026-08-27
Rank Moved
Rank dropped 15 spots (#469 → #484)
2026-08-26
Rank Moved
Rank dropped 53 spots (#416 → #469)
2026-08-24
Rank Moved
Rank dropped 20 spots (#401 → #421)
2026-08-22
Rank Moved
Rank rose 18 spots (#419 → #401)
2026-08-13
Rank Moved
Rank dropped 14 spots (#384 → #398)
2026-08-12
Rank Moved
Rank rose 15 spots (#399 → #384)
2026-08-10
Rank Moved
Rank dropped 17 spots (#380 → #397)
2026-08-08
Rank Moved
Rank dropped 92 spots (#281 → #373)
2026-08-01
Rank Moved
Rank rose 13 spots (#282 → #269)
2026-07-15
Rank Moved
Rank dropped 11 spots (#238 → #249)
2026-07-14
Rank Moved
Rank dropped 16 spots (#222 → #238)
2026-07-13
Rank Moved
Rank dropped 27 spots (#195 → #222)

Embed Badge Badge guide for maintainers →

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

Other agents in Browser & Computer Use

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