Is UI-TARS Desktop safe?
UI-TARS Desktop scores 56.7/100 (Grade C), ranked #195 of 328 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 4.8/10;
100% of recent commits are signed;
last pushed 2026-07-01. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
56.7/100 · Grade C
Strongest Signal
Transparency
12.6/17
Weakest Signal
Safety / Integrity
11.0/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-04
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-07-01
Rank Moved
Rank rose 10 spots (#203 → #193)
2026-07-01
Activity Score Changed
Activity score up 6pts (67 → 73)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 4.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
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 refreshed2026-07-11 04:00 UTC·Repo last pushed 10 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
37.9k
Forks
3.8k
Last Push
2026-07-01
10 days ago
Commits (4 wk)
1
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
318
Rank Change
▼1
was #194
Analysis
HVTrust Dimensions
56.7 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.6 / 17
MaintenanceFreshness and commits
12.5 / 20
AdoptionStars and downloads
11.0 / 20
Activity Inputs
71.6 / 100
StarsRepository reach
27.5 / 30
FreshnessLast push recency
23.6 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
16.7 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.8 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection1
CI-Tests8
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained1
Packaging-1
Pinned-Dependencies4
SAST7
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is UI-TARS Desktop safe?
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 4.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 UI-TARS Desktop actively maintained?
Maintained. Last push was 10 days ago.
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.
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.
browser
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
How this surface has changed
Detected changes to UI-TARS Desktop'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-07-04
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
Runtime surface grew — new detected provider dependency: Anthropic
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → declared
Maintain UI-TARS Desktop?
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.
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.2 · Raw JSON
