Open Operator
A template for building web agents with Stagehand on Browserbase
Compare Open Operator
How does it stack up against its Browser & Computer Use neighbours?
Pick any agent to compare →Thin or incomplete trust evidence. Review carefully before production use.
Is Open Operator safe? Open Operator scores 28.1/100 (Grade D), ranked #744 of 1204 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 2.4/10; 23% of recent commits are signed; last pushed 2026-05-04. 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 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 →
Activity & Reach
Analysis
HVTrust Dimensions vs Browser & Computer Use
28.1 / 100 · 100.0% confidenceOpen Operator Browser & Computer Use average (34 agents)
Activity Inputs
43.1 / 100Supply Chain Trust
Is Open Operator safe?
Does Open Operator publish package provenance?
Does Open Operator have an OpenSSF Scorecard?
Is Open Operator actively maintained?
What license does Open Operator use?
Are Open Operator's commits signed?
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
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
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Open Operator'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 Open Operator?
For maintainers
HVTrust scores Open Operator 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/open-operator)
<a href="https://hvtracker.net/agents/open-operator"><img src="https://hvtracker.net/badge/open-operator.svg" alt="HVTrust"></a>
Other agents in Browser & Computer Use
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