Is bb-browser safe to use?

bb-browser has an HVTrust score of 50.4/100 (Grade C), ranked #906 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for bb-browser?

bb-browser scores 50.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 6.2k GitHub stars and is categorized under Browser & Computer Use.

bb-browser

epiral/bb-browser

Your browser is the API. CLI + MCP server for AI agents to control Chrome with your login state.

Browser & Computer Use TypeScript Grade C Listed MIT

50.4/100

Rank #906 of 1328

Compare bb-browser

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 B · 3/5 signals

Last push

2026-05-29 · 104d ago

Recent change

Rank +8

Is bb-browser safe? bb-browser scores 50.4/100 (Grade C), ranked #906 of 1328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.6/10; 32% of recent commits are signed; last pushed 2026-05-29. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#25 autoMate — 51.5 (C) → #26 openocta — 51.3 (C) → #28 Agent-S — 49.8 (D) → #29 OmniParser — 46.6 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-09

Rank Moved

Rank dropped 17 spots (#887 → #904)

2026-09-08

Rank Moved

Rank dropped 12 spots (#875 → #887)

2026-09-07

Rank Moved

Rank dropped 40 spots (#835 → #875)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.6/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 104 days ago. Fresh activity helps separate stable projects from stale ones.

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

46.3

Activity sub-score · out of 100

#27

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 C 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

2026-08-11 2026-09-10

Activity & Reach

Stars

6.2k

Forks

603

Last Push

2026-05-29

104 days ago

Commits (4 wk)

Downloads (7d)

733

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #904

Analysis

HVTrust Dimensions vs Browser & Computer Use

50.4 / 100 · 100.0% confidence

bb-browser Browser & Computer Use average (42 agents)

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

4.9 / 25

4.5 below avg 9.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.5 below avg 12.3

Transparency50% declared license · 50% OSSF Scorecard

10.7 / 17

1.1 below avg 11.8

Maintenance60% last-push freshness · 40% commit activity

5.1 / 20

8.1 below avg 13.2

AdoptionLog-scaled stars · package downloads

12.9 / 20

1.7 above avg 11.2

Activity Inputs

46.3 / 100

StarsRepository reach

22.8 / 30

FreshnessLast push recency

10.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

12.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.6 / 10

OpenSSF Scorecard · scanned Sep 8, 2026

Signed Commits

32%

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 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is bb-browser safe?

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

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

Does bb-browser have an OpenSSF Scorecard?

bb-browser has an OpenSSF Scorecard score of 2.6/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 bb-browser actively maintained?

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

What license does bb-browser use?

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

Are bb-browser's commits signed?

32% of the last 100 commits to bb-browser 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

Implemented

bb-browser appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

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

Tool / Plugin Surface

None detected

No clear plugin system or broad tool 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

How this surface has changed

Detected changes to bb-browser'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-09-02

Tool Surface Changed

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

2026-08-27

Activity Went Stale

No commits for 90 days

Maintain bb-browser?

For maintainers

HVTrust scores bb-browser 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-09-09

Rank Moved

Rank dropped 17 spots (#887 → #904)

2026-09-08

Rank Moved

Rank dropped 12 spots (#875 → #887)

2026-09-07

Rank Moved

Rank dropped 40 spots (#835 → #875)

2026-09-06

Rank Moved

Rank dropped 15 spots (#820 → #835)

2026-09-05

Grade Changed

Trust grade D → C

2026-09-05

Rank Moved

Rank rose 359 spots (#1179 → #820)

2026-09-05

HVTrust Changed

HVTrust up 17.4pts (33.3 → 50.7)

2026-09-04

Rank Moved

Rank dropped 16 spots (#1163 → #1179)

2026-09-03

Rank Moved

Rank dropped 42 spots (#1121 → #1163)

2026-09-02

Tool Surface Changed

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

2026-09-02

Grade Changed

Trust grade C → D

2026-09-02

Rank Moved

Rank dropped 453 spots (#668 → #1121)

2026-09-02

HVTrust Changed

HVTrust down 16.7pts (50.1 → 33.4)

2026-09-01

Rank Moved

Rank dropped 23 spots (#645 → #668)

2026-08-31

Rank Moved

Rank dropped 39 spots (#606 → #645)

2026-08-29

Rank Moved

Rank dropped 37 spots (#561 → #598)

2026-08-28

Scorecard Added

OSSF Scorecard: 2.6/10

2026-08-28

Grade Changed

Trust grade D → C

2026-08-28

Rank Moved

Rank rose 334 spots (#895 → #561)

2026-08-28

HVTrust Changed

HVTrust up 18.7pts (31.6 → 50.3)

2026-08-27

Activity Went Stale

No commits for 90 days

2026-08-27

Rank Moved

Rank dropped 31 spots (#864 → #895)

2026-08-26

Rank Moved

Rank dropped 111 spots (#753 → #864)

2026-08-16

Rank Moved

Rank dropped 15 spots (#736 → #751)

2026-08-10

Newly Listed

First tracked at rank #736

GitHub → npm: bb-browser

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/bb-browser.svg)](https://hvtracker.net/agents/bb-browser)
            
HTML:
            <a href="https://hvtracker.net/agents/bb-browser"><img src="https://hvtracker.net/badge/bb-browser.svg" alt="HVTrust"></a>

Other agents in Browser & Computer Use

Data sources
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