OpenClaw
Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞
Compare OpenClaw
How does it stack up against its Browser & Computer Use neighbours?
Pick any agent to compare →Strong public trust posture, backed by multiple independent signals.
Is OpenClaw safe? OpenClaw scores 86.3/100 (Grade A), ranked #40 of 1283 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 4.7/10; recent commits are unsigned; last pushed 2026-08-14. Every point is earned from checkable signals — never paid placement. How scoring works →
Ranked neighbours in Browser & Computer Use
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
HVTrust Dimensions vs Browser & Computer Use
86.3 / 100 · 100.0% confidenceOpenClaw Browser & Computer Use average (41 agents)
Activity Inputs
100.0 / 100Supply Chain Trust
Is OpenClaw safe?
Does OpenClaw publish package provenance?
Does OpenClaw have an OpenSSF Scorecard?
Is OpenClaw actively maintained?
What license does OpenClaw use?
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
AI agent surface
MCP, providers, tool surface
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 →
- browser
- shell
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/openclaw)
<a href="https://hvtracker.net/agents/openclaw"><img src="https://hvtracker.net/badge/openclaw.svg" alt="HVTrust"></a>
Other agents in Browser & Computer Use
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON