Is OpenBrowser safe to use?

OpenBrowser has an HVTrust score of 34.9/100 (Grade D), ranked #397 of 468 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for OpenBrowser?

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

OpenBrowser

ntegrals/openbrowser

Let AI agents browse the web. An autonomous toolkit for browser-based AI agents.

Browser & Computer Use TypeScript Grade D Listed MIT

34.9/100

Rank #397 of 468

Compare OpenBrowser

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.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-04-02 · 126d ago

Recent change

No recent signal change

Is OpenBrowser safe? OpenBrowser scores 34.9/100 (Grade D), ranked #397 of 468 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 2.7/10; 1% of recent commits are signed; last pushed 2026-04-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#23 OpenAI CUA Sample App — 37.0 (D) → #24 Agent-E — 36.7 (D) → #26 Nanobrowser — 34.3 (D) → #27 ScaleCUA — 29.6 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-07-29

Rank Moved

Rank dropped 13 spots (#386 → #399)

2026-07-15

Rank Moved

Rank dropped 25 spots (#353 → #378)

2026-07-14

Rank Moved

Rank dropped 20 spots (#333 → #353)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 126 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for OpenBrowser View Browser & Computer Use Report missing data

45.2

Activity sub-score · out of 100

#25

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 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-07-05 2026-08-06

Activity & Reach

Stars

9.5k

Forks

863

Last Push

2026-04-02

126 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #397

Analysis

HVTrust Dimensions vs Browser & Computer Use

34.9 / 100 · 100.0% confidence

OpenBrowser Browser & Computer Use average (31 agents)

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

3.4 / 25

4.8 below avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.4 below avg 12.2

Transparency50% declared license · 50% OSSF Scorecard

10.8 / 17

0.5 below avg 11.3

Maintenance60% last-push freshness · 40% commit activity

3.6 / 20

7.7 below avg 11.3

AdoptionLog-scaled stars · package downloads

9.5 / 20

1.6 below avg 11.1

Activity Inputs

45.2 / 100

StarsRepository reach

23.9 / 30

FreshnessLast push recency

7.5 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

13.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.7 / 10

OpenSSF Scorecard · scanned Jul 11, 2026 (refresh pending)

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 7

Is OpenBrowser safe?

Public trust evidence for OpenBrowser 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 OpenBrowser publish package provenance?

No published build provenance is currently detected for OpenBrowser. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does OpenBrowser have an OpenSSF Scorecard?

OpenBrowser has an OpenSSF Scorecard score of 2.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 OpenBrowser actively maintained?

Slowing down. Last push was 126 days ago — keep an eye on whether activity resumes.

What license does OpenBrowser use?

OpenBrowser ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are OpenBrowser's commits signed?

1% of the last 100 commits to OpenBrowser 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

None detected

No MCP server signal detected.

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

high confidence

Declared

Declared plugin/integration surface detected.

browser
code
search

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 OpenBrowser'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-07-01

Activity Went Stale

No commits for 90 days

Maintain OpenBrowser?

For maintainers

HVTrust scores OpenBrowser 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-07-29

Rank Moved

Rank dropped 13 spots (#386 → #399)

2026-07-15

Rank Moved

Rank dropped 25 spots (#353 → #378)

2026-07-14

Rank Moved

Rank dropped 20 spots (#333 → #353)

2026-07-13

Rank Moved

Rank dropped 36 spots (#297 → #333)

2026-07-01

Activity Went Stale

No commits for 90 days

2026-06-24

Rank Moved

Rank dropped 33 spots (#246 → #279)

2026-06-23

Scorecard Added

OSSF Scorecard: 2.8/10

2026-06-23

Rank Moved

Rank rose 51 spots (#297 → #246)

2026-06-23

HVTrust Changed

HVTrust up 23.4pts (17.8 → 41.2)

2026-06-21

Newly Listed

First tracked at rank #296

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/openbrowser.svg)](https://hvtracker.net/agents/openbrowser)
            
HTML:
            <a href="https://hvtracker.net/agents/openbrowser"><img src="https://hvtracker.net/badge/openbrowser.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.2 · Raw JSON