updated 2026-08-09 19:01 UTC

OpenCLI

jackwener/OpenCLI

Make Any Website into CLI & Use your logged-in browser by AI agent.

Browser & Computer Use JavaScript Grade B Listed Apache-2.0
65.2/100
Rank #211 of 1204
Compare OpenCLI

How does it stack up against its Browser & Computer Use neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-09 · 0d ago
Recent change
Grade Changed +3

Is OpenCLI safe? OpenCLI scores 65.2/100 (Grade B), ranked #211 of 1204 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 5.3/10; 100% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#6 Browser Use — 73.6 (B) → #7 Cua — 72.0 (B) → #9 BrowserOS — 64.4 (C) → #10 Steel Browser — 56.6 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-08
Grade Changed
Trust grade C → B
2026-08-08
Rank Moved
Rank dropped 20 spots (#189 → #209)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.3/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 Browser Harness Get email alerts for OpenCLI View Browser & Computer Use Report missing data
90.0
Activity sub-score · out of 100
#8
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 B 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-09 19:01 UTC · Repo last pushed today

Activity & Reach

Stars
28.0k
Forks
2.8k
Last Push
2026-08-09
today
Commits (4 wk)
60
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
100
Rank Change
▼2
was #209

Analysis

HVTrust Dimensions vs Browser & Computer Use

65.2 / 100 · 100.0% confidence

OpenCLI Browser & Computer Use average (34 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.6 / 25
3.8 above avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
13.0 / 17
1.8 above avg 11.2
Maintenance60% last-push freshness · 40% commit activity
19.1 / 20
7.1 above avg 12.0
AdoptionLog-scaled stars · package downloads
10.7 / 20
in line with avg 10.8

Activity Inputs

90.0 / 100
StarsRepository reach
26.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
22.3 / 25
CommunityFork signal
16.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.3 / 10
OpenSSF Scorecard · scanned Aug 8, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 7
CII-Best-Practices 0
Code-Review 9
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 5
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is OpenCLI safe?

OpenCLI 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 OpenCLI publish package provenance?
No published build provenance is currently detected for OpenCLI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does OpenCLI have an OpenSSF Scorecard?
OpenCLI has an OpenSSF Scorecard score of 5.3/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 OpenCLI actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does OpenCLI use?
OpenCLI ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenCLI's commits signed?
100% of the last 100 commits to OpenCLI 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.

Compare OpenCLI head-to-head

OpenCLI vs Browser Harness → OpenCLI vs Agent Browser → OpenCLI vs OpenClaw →

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
How this surface has changed

Detected changes to OpenCLI'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-08-07
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none

Maintain OpenCLI?

For maintainers

HVTrust scores OpenCLI 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
Rank 4Listed 1Surface 1Grade 1
2026-08-08
Grade Changed
Trust grade C → B
2026-08-08
Rank Moved
Rank dropped 20 spots (#189 → #209)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-08-02
Rank Moved
Rank dropped 13 spots (#160 → #173)
2026-07-29
Rank Moved
Rank rose 10 spots (#175 → #165)
2026-07-14
Rank Moved
Rank dropped 12 spots (#143 → #155)
2026-07-13
Newly Listed
First tracked at rank #143
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.2 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/opencli.svg)](https://hvtracker.net/agents/opencli)
HTML:
<a href="https://hvtracker.net/agents/opencli"><img src="https://hvtracker.net/badge/opencli.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