updated 2026-08-12 05:02 UTC

Browser4

platonai/Browser4

Browser4 — an AI-native browser engine for autonomous agents, intelligent extraction, and large-scale web automation.

Browser & Computer Use Kotlin Grade B Listed Apache-2.0
66.6/100
Rank #199 of 1283
Compare Browser4

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 B · 3/5 signals
Last push
2026-08-11 · 1d ago
Recent change
New

Is Browser4 safe? Browser4 scores 66.6/100 (Grade B), ranked #199 of 1283 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; no OSSF Scorecard result yet; 1% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#8 Browser Use — 73.7 (B) → #9 Camofox Browser — 71.9 (B) → #11 OpenCLI — 64.6 (C) → #12 BrowserOS — 64.3 (C) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #197
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Browser4 View Browser & Computer Use Report missing data
78.3
Activity sub-score · out of 100
#10
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 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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
1.1k
Forks
145
Last Push
2026-08-11
yesterday
Commits (4 wk)
761
Downloads (7d)
987
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼2
was #197

Analysis

HVTrust Dimensions vs Browser & Computer Use

66.6 / 100 · 100.0% confidence

Browser4 Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.5 / 25
in line with avg 7.4
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.6 above avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
2.3 below avg 10.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
6.9 above avg 13.0
AdoptionLog-scaled stars · package downloads
11.3 / 20
in line with avg 11.2

Activity Inputs

78.3 / 100
StarsRepository reach
18.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
10.1 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
1%
of last 100 commits verified

Is Browser4 safe?

Browser4 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 Browser4 publish package provenance?
Yes. Browser4's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Browser4 have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Browser4. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Browser4 actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Browser4 use?
Browser4 ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Browser4's commits signed?
1% of the last 100 commits to Browser4 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.

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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium confidence
Extensions
Extension based plugin/integration surface detected.
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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-08-10
Newly Listed
First tracked at rank #197
GitHub → npm: browser4-cli

Embed Badge Badge guide for maintainers →

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

Other agents in Browser & Computer Use

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