updated 2026-08-26 18:33 UTC

Computer Use Linux

agent-sh/computer-use-linux

Pending first signal refresh

Agent Skills Rust Grade D Listed
14.0/100
Rank #266 of 331
Compare Computer Use Linux

How does it stack up against its Agent Skills 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 D · 1/5 signals
Last push
2026-08-25 · 1d ago
Recent change
New

Is Computer Use Linux safe? Computer Use Linux scores 14.0/100 (Grade D), ranked #266 of 331 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; recent commits are unsigned; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#264 Secondsky Claude Skills — 14.1 (D) → #265 Recall — 14.0 (D) → #267 Claude Reflect — 13.9 (D) → #268 Fireworks Tech Graph — 13.9 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-26
Newly Listed
First tracked at rank #266
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 Computer Use Linux View Agent Skills Report missing data
66.9
Activity sub-score · out of 100
#266
In Agent Skills

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-08-26 18:33 UTC · Repo last pushed yesterday

Activity & Reach

Stars
440
Forks
45
Last Push
2026-08-25
yesterday
Commits (4 wk)
29
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
NEW

Analysis

HVTrust Dimensions vs Agent Skills

14.0 / 100 · 40.0% confidence

Computer Use Linux Agent Skills average (331 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0 / 25
1.7 below avg 1.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.1
Transparency50% declared license · 50% OSSF Scorecard
0 / 17
4.4 below avg 4.4
Maintenance60% last-push freshness · 40% commit activity
17.8 / 20
3.3 above avg 14.5
AdoptionLog-scaled stars · package downloads
6.3 / 20
2.0 below avg 8.3

Activity Inputs

66.9 / 100
StarsRepository reach
15.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
18.4 / 25
CommunityFork signal
7.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
—
Unable to query

Is Computer Use Linux safe?

Public trust evidence for Computer Use Linux 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 Computer Use Linux publish package provenance?
No published build provenance is currently detected for Computer Use Linux. 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 Linux have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Computer Use Linux. 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 Computer Use Linux actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Computer Use Linux use?
Computer Use Linux ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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

Maintain Computer Use Linux?

For maintainers

HVTrust scores Computer Use Linux 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
Listed 1
2026-08-26
Newly Listed
First tracked at rank #266
GitHub → npm: @agent-sh/computer-use-linux

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Skills

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