updated 2026-07-29 01:00 UTC

Open Computer Use

iFurySt/open-codex-computer-use

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

Browser & Computer Use Swift Grade D Listed MIT
Compare → Suggest correction
Listing state
Listed
HVTrust
21.8/100 · Grade D
Evidence coverage
Grade D · 1/5 signals
Last push
2026-07-27 · 2d ago
Recent change
New

Is Open Computer Use safe? Open Computer Use scores 21.8/100 (Grade D), ranked #426 of 441 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 15% of recent commits are signed; last pushed 2026-07-27. Every point is earned from checkable signals — never paid placement. How scoring works →

Quick Trust Read

Verdict
Thin or incomplete trust evidence. Review carefully before production use.
21.8/100 · Grade D
Strongest Signal
Maintenance
16.4/20
Weakest Signal
Safety / Integrity
0.8/25
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-07-28
Newly Listed
First tracked at rank #426
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.5
Activity sub-score · out of 100
21.8
HVTrust Score · out of 100
#426
Global Rank · of 441
#29
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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-07-29 01:00 UTC · Repo last pushed 2 days ago

Rank Trend

2026-07-28 2026-07-29

Activity & Reach

Stars
1.6k
Forks
144
Last Push
2026-07-27
2 days ago
Commits (4 wk)
13
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
15
Rank Change
=
was #426

Analysis

HVTrust Dimensions

21.8 / 100 · 50.0% confidence
Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.8 / 25
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
Maintenance60% last-push freshness · 40% commit activity
16.4 / 20
Adoption60% stars · 40% downloads, log-scaled
7.7 / 20

Activity Inputs

68.5 / 100
StarsRepository reach
19.2 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
14.3 / 25
CommunityFork signal
10.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
15%
of last 100 commits verified

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?
No OpenSSF Scorecard data is currently published for Open Computer Use. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Open Computer Use actively maintained?
Actively maintained. The repository was pushed to within the last 2 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.

Ranked neighbours in Browser & Computer Use

#27 Open Operator — 28.9 (D) → #28 BrowserOS — 28.4 (D) → #30 TuriX — 17.4 (D) → #31 Understudy — 15.1 (D) →

AI agent 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
medium 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?

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

Listed 1
2026-07-28
Newly Listed
First tracked at rank #426
GitHub →

Embed Badge Badge guide for maintainers →

HVTrust 21.8 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON