ScaleCUA

[ICLR 2026 Oral] ScaleCUA is the open-sourced computer use agents that can operate on cross-platform environments (Windo

Browser & Computer Use Python Grade D Listed Apache-2.0
29.6/100
Rank #413 of 468
Compare ScaleCUA

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-01-07 · 211d ago
Recent change
No recent signal change

Is ScaleCUA safe? ScaleCUA scores 29.6/100 (Grade D), ranked #413 of 468 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 1.4/10; 61% of recent commits are signed; last pushed 2026-01-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-29
Rank Moved
Rank dropped 12 spots (#402 → #414)
2026-07-15
Rank Moved
Rank dropped 24 spots (#373 → #397)
2026-07-14
Rank Moved
Rank dropped 21 spots (#352 → #373)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.4/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.
Refresh maintenance signals The repo was last pushed 211 days ago. Fresh activity helps separate stable projects from stale ones.
27.2
Activity sub-score · out of 100
#27

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 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-06 07:30 UTC · Repo last pushed 211 days ago — may be stale

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
1.1k
Forks
80
Last Push
2026-01-07
211 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
14
Rank Change
=
was #413

Analysis

HVTrust Dimensions vs Browser & Computer Use

29.6 / 100 · 100.0% confidence

ScaleCUA Browser & Computer Use average (31 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.8 / 25
3.4 below avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.4 below avg 12.2
Transparency50% declared license · 50% OSSF Scorecard
9.7 / 17
1.6 below avg 11.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
11.3 below avg 11.3
AdoptionLog-scaled stars · package downloads
7.3 / 20
3.8 below avg 11.1

Activity Inputs

27.2 / 100
StarsRepository reach
18.3 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.9 / 20

Supply Chain Trust

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

Is ScaleCUA safe?

Public trust evidence for ScaleCUA 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 ScaleCUA publish package provenance?
No published build provenance is currently detected for ScaleCUA. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does ScaleCUA have an OpenSSF Scorecard?
ScaleCUA has an OpenSSF Scorecard score of 1.4/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 ScaleCUA actively maintained?
Stale. The repository has not been pushed to in 211 days. Consider whether the project is still being maintained.
What license does ScaleCUA use?
ScaleCUA ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ScaleCUA's commits signed?
60% of the last 100 commits to ScaleCUA 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
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
  • code
  • search
  • shell
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 ScaleCUA?

For maintainers

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

Reputation Timeline

Signal history
Rank 8Listed 1HVTrust 1Scorecard 1
2026-07-29
Rank Moved
Rank dropped 12 spots (#402 → #414)
2026-07-15
Rank Moved
Rank dropped 24 spots (#373 → #397)
2026-07-14
Rank Moved
Rank dropped 21 spots (#352 → #373)
2026-07-13
Rank Moved
Rank dropped 36 spots (#316 → #352)
2026-06-24
Rank Moved
Rank dropped 35 spots (#271 → #306)
2026-06-23
Rank Moved
Rank dropped 23 spots (#248 → #271)
2026-06-22
Rank Moved
Rank dropped 10 spots (#238 → #248)
2026-06-21
Scorecard Added
OSSF Scorecard: 1.4/10
2026-06-21
Rank Moved
Rank rose 30 spots (#268 → #238)
2026-06-21
HVTrust Changed
HVTrust up 18.2pts (15.4 → 33.6)
2026-06-20
Newly Listed
First tracked at rank #268

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 29.6 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/scalecua.svg)](https://hvtracker.net/agents/scalecua)
HTML:
<a href="https://hvtracker.net/agents/scalecua"><img src="https://hvtracker.net/badge/scalecua.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.2 · Raw JSON