Is UI-TARS safe to use?

UI-TARS has an HVTrust score of 40.0/100 (Grade D), ranked #632 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for UI-TARS?

UI-TARS scores 40.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 11.4k GitHub stars and is categorized under Browser & Computer Use.

UI-TARS

bytedance/UI-TARS

Pioneering Automated GUI Interaction with Native Agents

Browser & Computer Use Python Grade D Listed Apache-2.0

40.0/100

Rank #632 of 1308

Compare UI-TARS

How does it stack up against its Browser & Computer Use 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 A · 4/5 signals

Last push

2026-01-27 · 210d ago

Recent change

Rank

Is UI-TARS safe? UI-TARS scores 40.0/100 (Grade D), ranked #632 of 1308 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; last pushed 2026-01-27. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#25 MolmoWeb — 42.9 (D) → #26 Peekaboo — 42.8 (D) → #28 Understudy — 39.2 (D) → #29 Agent-E — 37.8 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

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

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 210 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.0

Activity sub-score · out of 100

#27

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 →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

11.4k

Forks

871

Last Push

2026-01-27

210 days ago

Commits (4 wk)

Downloads (7d)

4,039

pypi

HN mentions (30d)

Open Issues

Rank Change

▲5

was #637

Analysis

HVTrust Dimensions vs Browser & Computer Use

40.0 / 100 · 100.0% confidence

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

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

4.1 / 25

3.4 below avg 7.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.6 below avg 12.4

Transparency50% declared license · 50% OSSF Scorecard

10.6 / 17

in line with avg 10.8

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.8 below avg 12.8

AdoptionLog-scaled stars · package downloads

14.5 / 20

3.2 above avg 11.3

Activity Inputs

38.0 / 100

StarsRepository reach

24.3 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

13.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.5 / 10

OpenSSF Scorecard · scanned Aug 25, 2026

Signed Commits

19%

of last 100 commits verified

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

Is UI-TARS safe?

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 210 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

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)

2026-06-24

Rank Moved

Rank dropped 34 spots (#237 → #271)

2026-06-23

Rank Moved

Rank dropped 18 spots (#219 → #237)

2026-06-22

Rank Moved

Rank dropped 10 spots (#209 → #219)

2026-06-21

Rank Moved

Rank dropped 14 spots (#195 → #209)

2026-06-18

Rank Moved

Rank dropped 12 spots (#175 → #187)

2026-06-02

Rank Moved

Rank dropped 12 spots (#144 → #156)

2026-06-01

Rank Moved

Rank dropped 17 spots (#127 → #144)

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (31.8 → 41.8)

GitHub → PyPI: ui-tars

Embed Badge Badge guide for maintainers →

For maintainers

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