updated 2026-08-11 20:02 UTC

Open Computer Use

iFurySt/open-codex-computer-use

👾 Open Computer Use – Open-Source Alternative to Codex Computer Use

Browser & Computer Use Swift Grade C Listed MIT
53.2/100
Rank #427 of 1283
Compare Open Computer Use

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 C · 2/5 signals
Last push
2026-08-07 · 4d ago
Recent change
Rank +1

Is Open Computer Use safe? Open Computer Use scores 53.2/100 (Grade C), ranked #427 of 1283 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.5/10; 15% of recent commits are signed; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#16 UI-TARS Desktop — 55.8 (C) → #17 Magentic-UI — 55.7 (C) → #19 autoMate — 52.2 (C) → #20 OmniParser — 50.5 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 17 spots (#409 → #426)
2026-08-08
Rank Moved
Rank dropped 102 spots (#304 → #406)
2026-07-29
Scorecard Added
OSSF Scorecard: 4.5/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
Compare with another agent Get email alerts for Open Computer Use View Browser & Computer Use Report missing data
68.4
Activity sub-score · out of 100
#18
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 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-08-11 20:02 UTC · Repo last pushed 4 days ago

Activity & Reach

Stars
1.7k
Forks
157
Last Push
2026-08-07
4 days ago
Commits (4 wk)
13
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
8
Rank Change
▼1
was #426

Analysis

HVTrust Dimensions vs Browser & Computer Use

53.2 / 100 · 100.0% confidence

Open Computer Use Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.4 / 25
1.0 below avg 7.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.6 below avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
1.5 above avg 10.8
Maintenance60% last-push freshness · 40% commit activity
16.3 / 20
3.2 above avg 13.1
AdoptionLog-scaled stars · package downloads
7.7 / 20
3.5 below avg 11.2

Activity Inputs

68.4 / 100
StarsRepository reach
19.3 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
14.3 / 25
CommunityFork signal
10.2 / 20

Supply Chain Trust

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

Is Open Computer Use safe?

Public trust evidence for Open Computer Use 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 Open Computer Use publish package provenance?
No published build provenance is currently detected for Open Computer Use. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Open Computer Use have an OpenSSF Scorecard?
Open Computer Use has an OpenSSF Scorecard score of 4.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 Open Computer Use actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does Open Computer Use use?
Open Computer Use ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Open Computer Use's commits signed?
15% of the last 100 commits to Open Computer Use 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
high confidence
Declared
Declared plugin/integration 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

Maintain Open Computer Use?

For maintainers

HVTrust scores Open Computer Use 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 3Listed 1HVTrust 1Grade 1Scorecard 1
2026-08-10
Rank Moved
Rank dropped 17 spots (#409 → #426)
2026-08-08
Rank Moved
Rank dropped 102 spots (#304 → #406)
2026-07-29
Scorecard Added
OSSF Scorecard: 4.5/10
2026-07-29
Grade Changed
Trust grade D → C
2026-07-29
Rank Moved
Rank rose 134 spots (#426 → #292)
2026-07-29
HVTrust Changed
HVTrust up 31.4pts (21.9 → 53.3)
2026-07-28
Newly Listed
First tracked at rank #426
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 53.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/open-computer-use.svg)](https://hvtracker.net/agents/open-computer-use)
HTML:
<a href="https://hvtracker.net/agents/open-computer-use"><img src="https://hvtracker.net/badge/open-computer-use.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.3 · Raw JSON