OpenCUA

[NeurIPS 2025 Spotlight] OpenCUA: Open Foundations for Computer-Use Agents

Browser & Computer Use Python Grade D Listed MIT
36.3/100
Rank #696 of 1308
Compare OpenCUA

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-05-25 · 92d ago
Recent change
Stale

Is OpenCUA safe? OpenCUA scores 36.3/100 (Grade D), ranked #696 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.3/10; 27% of recent commits are signed; last pushed 2026-05-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-23
Activity Went Stale
No commits for 90 days
2026-08-16
Rank Moved
Rank dropped 13 spots (#669 → #682)
2026-08-10
Rank Moved
Rank dropped 29 spots (#636 → #665)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.3/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 92 days ago. Fresh activity helps separate stable projects from stale ones.
39.2
Activity sub-score · out of 100
#30

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-25 10:02 UTC · Repo last pushed 92 days ago

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars
825
Forks
108
Last Push
2026-05-25
92 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
264
Open Issues
14
Rank Change
▼2
was #694

Analysis

HVTrust Dimensions vs Browser & Computer Use

36.3 / 100 · 100.0% confidence

OpenCUA Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.0 / 25
4.5 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
9.6 / 17
1.2 below avg 10.8
Maintenance60% last-push freshness · 40% commit activity
5.9 / 20
6.9 below avg 12.8
AdoptionLog-scaled stars · package downloads
7.0 / 20
4.3 below avg 11.3

Activity Inputs

39.2 / 100
StarsRepository reach
17.5 / 30
FreshnessLast push recency
12.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.5 / 20

Supply Chain Trust

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

Is OpenCUA safe?

Public trust evidence for OpenCUA 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 OpenCUA publish package provenance?
No published build provenance is currently detected for OpenCUA. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does OpenCUA have an OpenSSF Scorecard?
OpenCUA has an OpenSSF Scorecard score of 1.3/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 OpenCUA actively maintained?
Slowing down. Last push was 92 days ago — keep an eye on whether activity resumes.
What license does OpenCUA use?
OpenCUA ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenCUA's commits signed?
26% of the last 100 commits to OpenCUA 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
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 OpenCUA'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-23
Activity Went Stale
No commits for 90 days

Maintain OpenCUA?

For maintainers

HVTrust scores OpenCUA 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 15Stale 1
2026-08-23
Activity Went Stale
No commits for 90 days
2026-08-16
Rank Moved
Rank dropped 13 spots (#669 → #682)
2026-08-10
Rank Moved
Rank dropped 29 spots (#636 → #665)
2026-08-08
Rank Moved
Rank dropped 234 spots (#399 → #633)
2026-07-29
Rank Moved
Rank dropped 10 spots (#376 → #386)
2026-07-15
Rank Moved
Rank dropped 24 spots (#342 → #366)
2026-07-14
Rank Moved
Rank dropped 19 spots (#323 → #342)
2026-07-13
Rank Moved
Rank dropped 36 spots (#287 → #323)
2026-06-24
Rank Moved
Rank dropped 43 spots (#239 → #282)
2026-06-23
Rank Moved
Rank dropped 17 spots (#222 → #239)
2026-06-22
Rank Moved
Rank dropped 11 spots (#211 → #222)
2026-06-21
Rank Moved
Rank dropped 14 spots (#197 → #211)
2026-06-18
Rank Moved
Rank dropped 13 spots (#176 → #189)
2026-06-02
Rank Moved
Rank dropped 10 spots (#148 → #158)
2026-06-01
Rank Moved
Rank dropped 17 spots (#131 → #148)
2026-05-29
Rank Moved
Rank dropped 17 spots (#107 → #124)

Embed Badge Badge guide for maintainers →

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

Other agents in Browser & Computer Use

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