Browser4
Browser4 — an AI-native browser engine for autonomous agents, intelligent extraction, and large-scale web automation.
Is Browser4 safe? Strong public trust posture, backed by multiple independent signals.
Compare Browser4
How does it stack up against its Browser & Computer Use neighbours?
Pick any agent to compare →In detail: Browser4 scores 75.0/100 (Grade B), ranked #225 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.1/10; 1% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How Browser4 compares in Browser & Computer Use
- #8 agent-device 80.1 +5.1
- #9 Peekaboo 76.9 +1.9
- #10 Browser4 75.0 this agent
- #11 Cua 74.3 −0.7
- #12 Browser Use 72.4 −2.6
Bars show each HVTrust score; the tick marks Browser4’s 75.0.
Where the 75.0 comes from
HVTrust dimensions vs the Browser & Computer Use average
75.0 / 100 · 100.0% confidenceBrowser4 Browser & Computer Use average (42 agents)
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 B 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
78.5 / 100Supply Chain Trust
Common questions about Browser4
Does Browser4 publish package provenance?
Does Browser4 have an OpenSSF Scorecard?
Is Browser4 actively maintained?
What license does Browser4 use?
Are Browser4'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 →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Browser4'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 Browser4?
For maintainers
HVTrust scores Browser4 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/browser4)
<a href="https://hvtracker.net/agents/browser4"><img src="https://hvtracker.net/badge/browser4.svg" alt="HVTrust"></a>
Other agents in Browser & Computer Use
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON