Is Computer Use safe to use?

Computer Use has an HVTrust score of 64.2/100 (Grade C), ranked #503 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Computer Use?

Computer Use scores 64.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 379 GitHub stars and is categorized under MCP Servers.

Computer Use

domdomegg/computer-use-mcp

💻 Give AI models complete control of your computer (probably a bad idea)

MCP Servers TypeScript Listed MIT

Is Computer Use safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.0 / 10

Provenance None

Signed commits 85%

Last push 17d ago

Compare Computer Use

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Computer Use scores 64.2/100 (Grade C), ranked #503 of 1325 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 5.0/10; 85% of recent commits are signed; last pushed 2026-09-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Computer Use compares in MCP Servers

Bars show each HVTrust score; the tick marks Computer Use’s 64.2.

Where the 64.2 comes from

HVTrust dimensions vs the MCP Servers average

64.2 / 100 · 100.0% confidence

Computer Use MCP Servers average (775 agents)

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

10.5 / 25

in line with avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

0.6 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

14.5 / 20

2.5 above avg 12.0

AdoptionLog-scaled stars · package downloads

9.6 / 20

2.4 above avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 350 spots (#841 → #491)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.0/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.

Compare with another agent Get email alerts for Computer Use View MCP Servers Report missing data

57.5

Activity sub-score · out of 100

#290

In MCP Servers

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

379

Forks

Last Push

2026-09-09

17 days ago

Commits (4 wk)

Downloads (7d)

379

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #502

Analysis

Activity Inputs

57.5 / 100

StarsRepository reach

15.5 / 30

FreshnessLast push recency

22.6 / 25

ActivityRecent commits

11.3 / 25

CommunityFork signal

7.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.0 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

85%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 4

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 7

Common questions about Computer Use

Computer Use 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 Computer Use publish package provenance?

No published build provenance is currently detected for 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 Computer Use have an OpenSSF Scorecard?

Computer Use has an OpenSSF Scorecard score of 5.0/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 Computer Use actively maintained?

Maintained. Last push was 17 days ago.

What license does Computer Use use?

Computer Use ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Computer Use's commits signed?

85% of the last 100 commits to 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

high confidence

Implemented

Computer Use appears to expose MCP server capabilities.

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

high confidence

Match

Published package metadata matches the tracked repo

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 Computer Use'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-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Computer Use?

For maintainers

HVTrust scores 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 350 spots (#841 → #491)

2026-09-23

HVTrust Changed

HVTrust up 36.3pts (28.1 → 64.4)

2026-09-22

Newly Listed

First tracked at rank #841

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank rose 49 spots (#520 → #471)

2026-09-09

Rank Moved

Rank rose 24 spots (#522 → #498)

2026-09-08

Rank Moved

Rank dropped 12 spots (#510 → #522)

2026-09-07

Grade Changed

Trust grade D → C

2026-09-07

Rank Moved

Rank rose 565 spots (#1075 → #510)

2026-09-07

HVTrust Changed

HVTrust up 21.0pts (41.5 → 62.5)

2026-09-06

Rank Moved

Rank dropped 14 spots (#1061 → #1075)

2026-09-05

Rank Moved

Rank dropped 30 spots (#1031 → #1061)

2026-09-04

Rank Moved

Rank dropped 50 spots (#981 → #1031)

2026-09-03

Rank Moved

Rank dropped 15 spots (#966 → #981)

2026-09-03

Activity Score Changed

Activity score up 8pts (51 → 58)

2026-09-02

Rank Moved

Rank dropped 34 spots (#932 → #966)

2026-09-01

Rank Moved

Rank dropped 35 spots (#897 → #932)

2026-08-31

Rank Moved

Rank dropped 32 spots (#865 → #897)

2026-08-30

Scorecard Added

OSSF Scorecard: 4.6/10

2026-08-30

Rank Moved

Rank rose 259 spots (#1124 → #865)

2026-08-30

HVTrust Changed

HVTrust up 17.4pts (22.4 → 39.8)

2026-08-29

Rank Moved

Rank dropped 35 spots (#1089 → #1124)

2026-08-28

Rank Moved

Rank dropped 34 spots (#1055 → #1089)

2026-08-27

Rank Moved

Rank dropped 20 spots (#1035 → #1055)

2026-08-26

Rank Moved

Rank dropped 89 spots (#946 → #1035)

2026-08-24

Rank Moved

Rank dropped 24 spots (#925 → #949)

2026-08-16

Rank Moved

Rank dropped 26 spots (#913 → #939)

2026-08-10

Rank Moved

Rank dropped 54 spots (#870 → #924)

2026-08-08

Newly Listed

First tracked at rank #860

GitHub → npm: computer-use-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/computer-use.svg)](https://hvtracker.net/agents/computer-use)
            
HTML:
            <a href="https://hvtracker.net/agents/computer-use"><img src="https://hvtracker.net/badge/computer-use.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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