updated 2026-08-12 05:02 UTC

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 D Listed MIT
32.3/100
Rank #736 of 1283
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 C · 2/5 signals
Last push
2026-05-29 · 75d ago
Recent change
New

Is bb-browser safe? bb-browser scores 32.3/100 (Grade D), ranked #736 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 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

#31 OpenBrowser — 35.7 (D) → #32 Nanobrowser — 33.9 (D) → #34 ScaleCUA — 30.0 (D) → #35 PyWinAssistant — 29.2 (D) →

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 #736
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.
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 75 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
50.3
Activity sub-score · out of 100
#33
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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 75 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
6.0k
Forks
588
Last Push
2026-05-29
75 days ago
Commits (4 wk)
0
Downloads (7d)
733
npm
HN mentions (30d)
—
Open Issues
62
Rank Change
=
was #736

Analysis

HVTrust Dimensions vs Browser & Computer Use

32.3 / 100 · 67.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.6 / 25
5.8 below 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
8.5 / 17
2.3 below avg 10.8
Maintenance60% last-push freshness · 40% commit activity
7.0 / 20
6.0 below avg 13.0
AdoptionLog-scaled stars · package downloads
12.9 / 20
1.7 above avg 11.2

Activity Inputs

50.3 / 100
StarsRepository reach
22.7 / 30
FreshnessLast push recency
14.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.9 / 20

Supply Chain Trust

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

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?
No OpenSSF Scorecard data is currently published for bb-browser. 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 bb-browser actively maintained?
Slowing down. Last push was 75 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
high confidence
Extensions
Extension based plugin/integration surface detected.
  • browser
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 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
Listed 1
2026-08-10
Newly Listed
First tracked at rank #736
GitHub → npm: bb-browser

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 32.3 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON