updated 2026-07-29 00:30 UTC

BrowserOS

browseros-ai/BrowserOS

🌐 The open-source Agentic browser; alternative to ChatGPT Atlas, Perplexity Comet, Dia.

Browser & Computer Use TypeScript Grade D Listed AGPL-3.0
Compare → Suggest correction
Listing state
Listed
HVTrust
28.3/100 · Grade D
Evidence coverage
Grade D · 1/5 signals
Last push
2026-07-28 · 1d ago
Recent change
New

Is BrowserOS safe? BrowserOS scores 28.3/100 (Grade D), ranked #408 of 441 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 95% of recent commits are signed; last pushed 2026-07-28. Every point is earned from checkable signals — never paid placement. How scoring works →

Quick Trust Read

Verdict
Thin or incomplete trust evidence. Review carefully before production use.
28.3/100 · Grade D
Strongest Signal
Maintenance
19.9/20
Weakest Signal
Safety / Integrity
4.8/25
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-07-28
Newly Listed
First tracked at rank #408
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for BrowserOS View Browser & Computer Use Report missing data
89.2
Activity sub-score · out of 100
28.3
HVTrust Score · out of 100
#408
Global Rank · of 441
#28
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-07-29 00:30 UTC · Repo last pushed yesterday

Rank Trend

2026-07-28 2026-07-29

Activity & Reach

Stars
12.8k
Forks
1.3k
Last Push
2026-07-28
yesterday
Commits (4 wk)
549
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
40
Rank Change
=
was #408

Analysis

HVTrust Dimensions

28.3 / 100 · 50.0% confidence
Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.8 / 25
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
Adoption60% stars · 40% downloads, log-scaled
9.9 / 20

Activity Inputs

89.2 / 100
StarsRepository reach
24.6 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
95%
of last 100 commits verified

Is BrowserOS safe?

Public trust evidence for BrowserOS is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does BrowserOS publish package provenance?
No published build provenance is currently detected for BrowserOS. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does BrowserOS have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for BrowserOS. 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 BrowserOS actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does BrowserOS use?
BrowserOS ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are BrowserOS's commits signed?
95% of the last 100 commits to BrowserOS 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.

Ranked neighbours in Browser & Computer Use

#26 PyWinAssistant — 29.2 (D) → #27 Open Operator — 28.9 (D) → #29 Open Computer Use — 21.8 (D) → #30 TuriX — 17.4 (D) →

AI agent 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
BrowserOS appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Extensions
Extension based plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain BrowserOS?

HVTrust scores BrowserOS 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

Listed 1
2026-07-28
Newly Listed
First tracked at rank #408
GitHub →

Embed Badge Badge guide for maintainers →

HVTrust 28.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/browseros.svg)](https://hvtracker.net/agents/browseros)
HTML:
<a href="https://hvtracker.net/agents/browseros"><img src="https://hvtracker.net/badge/browseros.svg" alt="HVTrust"></a>

Other agents in Browser & Computer Use

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