Is BrowserOS safe to use?

BrowserOS has an HVTrust score of 65.7/100 (Grade B), ranked #222 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for BrowserOS?

BrowserOS scores 65.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 13.2k GitHub stars and is categorized under Browser & Computer Use.

BrowserOS

browseros-ai/BrowserOS

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

Browser & Computer Use TypeScript Grade B Listed AGPL-3.0

65.7/100

Rank #222 of 1308

Compare BrowserOS

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 C · 2/5 signals

Last push

2026-08-19 · 0d ago

Recent change

Rank +4

Is BrowserOS safe? BrowserOS scores 65.7/100 (Grade B), ranked #222 of 1308 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.7/10; 99% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#9 Camofox Browser — 70.5 (B) → #10 Browser4 — 66.7 (B) → #12 OpenCLI — 64.4 (C) → #13 UFO — 58.5 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-19

Rank Moved

Rank dropped 13 spots (#209 → #222)

2026-08-17

Rank Moved

Rank rose 14 spots (#221 → #207)

2026-08-13

Grade Changed

Trust grade C → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.7/10. Tighten the weakest checks to improve public safety evidence.

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.3

Activity sub-score · out of 100

#11

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

13.2k

Forks

1.4k

Last Push

2026-08-19

today

Commits (4 wk)

416

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼13

was #209

Analysis

HVTrust Dimensions vs Browser & Computer Use

65.7 / 100 · 100.0% confidence

BrowserOS Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.8 / 25

3.4 above avg 7.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.6 below avg 12.4

Transparency50% declared license · 50% OSSF Scorecard

12.5 / 17

1.8 above avg 10.7

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.0 above avg 13.0

AdoptionLog-scaled stars · package downloads

9.9 / 20

1.3 below avg 11.2

Activity Inputs

89.3 / 100

StarsRepository reach

24.7 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.7 / 10

OpenSSF Scorecard · scanned Aug 19, 2026

Signed Commits

99%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 3

CI-Tests 1

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is BrowserOS safe?

BrowserOS 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 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?

BrowserOS has an OpenSSF Scorecard score of 4.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

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?

99% 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.

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

high confidence

Implemented

BrowserOS appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Amazon Bedrock

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared 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

How this surface has changed

Detected changes to BrowserOS'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.

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

Maintain BrowserOS?

For maintainers

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

Signal history

2026-08-19

Rank Moved

Rank dropped 13 spots (#209 → #222)

2026-08-17

Rank Moved

Rank rose 14 spots (#221 → #207)

2026-08-13

Grade Changed

Trust grade C → B

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-12

Rank Moved

Rank rose 17 spots (#244 → #227)

2026-08-10

Rank Moved

Rank dropped 20 spots (#223 → #243)

2026-08-08

Rank Moved

Rank dropped 44 spots (#171 → #215)

2026-08-07

Scorecard Added

OSSF Scorecard: 4.8/10

2026-07-29

Rank Moved

Rank dropped 11 spots (#408 → #419)

2026-07-28

Newly Listed

First tracked at rank #408

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON