Is OpenCUA safe?
OpenCUA scores 39.3/100 (Grade D), ranked #287 of 328 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.6/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 →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
39.3/100 · Grade D
Strongest Signal
Identity / Provenance
10.8/18
Weakest Signal
Safety / Integrity
3.3/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 1.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signalsThe repo was last pushed 47 days ago. Fresh activity helps separate stable projects from stale ones.
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 refreshed2026-07-11 06:04 UTC·Repo last pushed 47 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
796
Forks
104
Last Push
2026-05-25
47 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
264
Open Issues
14
Rank Change
=
was #287
Analysis
HVTrust Dimensions
39.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
3.3 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
9.9 / 17
MaintenanceFreshness and commits
8.9 / 20
AdoptionStars and downloads
7.0 / 20
Activity Inputs
45.3 / 100
StarsRepository reach
17.4 / 30
FreshnessLast push recency
18.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.4 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
1.6 / 10
OpenSSF Scorecard · scanned Jul 11, 2026
Signed Commits
27%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests0
CII-Best-Practices0
Code-Review0
Contributors0
Dangerous-Workflow-1
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies-1
SAST0
Security-Policy0
Signed-Releases0
Token-Permissions-1
Vulnerabilities3
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.6/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 47 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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
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.
Runtime surface grew — new detected provider dependency: OpenAI
Maintain OpenCUA?
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.
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.2 · Raw JSON
