updated 2026-10-09 08:15 UTC

OpenClaw

Repository Website by openclaw

The AI that really does things. Any OS. Any Platform. The lobster way. 🦞

Browser & Computer Use TypeScript Listed MIT

Is OpenClaw safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.0 / 10
Provenance Attested
Signed commits 96%
Last push today
Advisories None known
Compare OpenClaw

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

Pick any agent to compare →
Suggest a correction

In detail: OpenClaw scores 91.3/100 (Grade A), ranked #16 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.0/10; 96% of recent commits are signed; no published advisory affects its latest release (openclaw); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenClaw could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships OpenClaw and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/openclaw/openclaw, MIT, last pushed 2026-10-09. 96% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.0/10 (scanned Oct 2, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies9
    All 18 Scorecard checks
    Binary-Artifacts 9
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 1
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 9
    Maintained 10
    Packaging 10
    Pinned-Dependencies 9
    SAST 8
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 3

  3. Published packages Linked and attested

    • npm openclaw Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: openclaw 2026.9.9. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

  • 2026-10-03 License changed from NOASSERTION to MIT
  • 2026-08-07 Provenance drift warning cleared (now: match)

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues OpenClaw’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How OpenClaw compares in Browser & Computer Use

  1. #1 OpenClaw 91.3 this agent
  2. #2 Browser Harness 90.7 −0.6
  3. #3 Peekaboo 89.9 −1.4
  4. #4 Argent 89.3 −2.0
  5. #5 Stagehand 88.9 −2.4

Bars show each HVTrust score; the tick marks OpenClaw’s 91.3.

Where the 91.3 comes from

HVTrust dimensions vs the Browser & Computer Use average

91.3 / 100 · 100.0% confidence

OpenClaw Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.8 / 25
10.5 above avg 9.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.6 above avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
13.6 / 17
2.2 above avg 11.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
20.0 / 20
9.3 above avg 10.7

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-10-03
License Changed
License changed from NOASSERTION to MIT
2026-09-16
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-09-14
Mcp Status Changed
Detected MCP server support changed: implemented → declared
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.0/10. Tighten the weakest checks to improve public safety evidence.
Compare with Browser Harness Get email alerts for OpenClaw View Browser & Computer Use Report missing data
100.0
Activity sub-score · out of 100
#1
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 A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
391.5k
Forks
82.3k
Last Push
2026-10-09
today
Commits (4 wk)
15920
Downloads (7d)
3,669,170
npm
HN mentions (30d)
49
Open Issues
6049
Rank Change
=
was #16

Analysis

Activity Inputs

100.0 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20

Common questions about OpenClaw

Public supply-chain signals for OpenClaw are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but OpenClaw carries less obvious unverified-evidence risk than projects with thin signals.
Does OpenClaw publish package provenance?
Yes. OpenClaw's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does OpenClaw have an OpenSSF Scorecard?
OpenClaw has an OpenSSF Scorecard score of 6.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 OpenClaw actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does OpenClaw use?
OpenClaw ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenClaw's commits signed?
96% of the last 100 commits to OpenClaw 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 OpenClaw head-to-head

OpenClaw vs Browser Harness → OpenClaw vs Peekaboo → OpenClaw vs Argent →

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
OpenClaw appears to expose MCP server capabilities.
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
Extensions
Extension based plugin/integration surface detected.
  • browser
  • shell
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 OpenClaw'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-16
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-09-14
Mcp Status Changed
Detected MCP server support changed: implemented → declared
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → extension-based
2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: match)

Maintain OpenClaw?

For maintainers

HVTrust scores OpenClaw 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 8HVTrust 2Grade 2MCP 2Drift 1Surface 1License 1
2026-10-03
License Changed
License changed from NOASSERTION to MIT
2026-09-16
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-09-14
Mcp Status Changed
Detected MCP server support changed: implemented → declared
2026-09-14
Rank Moved
Rank dropped 11 spots (#15 → #26)
2026-09-06
Rank Moved
Rank dropped 10 spots (#7 → #17)
2026-09-04
Grade Changed
Trust grade B → A
2026-09-04
Rank Moved
Rank rose 257 spots (#264 → #7)
2026-09-04
HVTrust Changed
HVTrust up 24.3pts (67.1 → 91.4)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → extension-based
2026-09-03
Grade Changed
Trust grade A → B
2026-09-03
Rank Moved
Rank dropped 239 spots (#25 → #264)
2026-09-03
HVTrust Changed
HVTrust down 21.1pts (88.2 → 67.1)
2026-09-02
Rank Moved
Rank rose 17 spots (#42 → #25)
2026-08-31
Rank Moved
Rank dropped 11 spots (#32 → #43)
2026-08-15
Rank Moved
Rank rose 10 spots (#44 → #34)
2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: match)
2026-07-13
Rank Moved
Rank dropped 12 spots (#48 → #60)
GitHub → Website → npm: openclaw

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 91.3 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/openclaw.svg)](https://hvtracker.net/agents/openclaw)
HTML:
<a href="https://hvtracker.net/agents/openclaw"><img src="https://hvtracker.net/badge/openclaw.svg" alt="HVTrust"></a>

Other agents in Browser & Computer Use

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