updated 2026-08-06 05:00 UTC

Steel Browser

steel-dev/steel-browser

🔥 Open Source Browser API for AI Agents & Apps. Steel Browser is a batteries-included browser sandbox that lets you auto

Browser & Computer Use TypeScript Grade C Listed Apache-2.0
56.5/100
Rank #264 of 468
Compare Steel Browser

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-05 · 1d ago
Recent change
No recent signal change

Is Steel Browser safe? Steel Browser scores 56.5/100 (Grade C), ranked #264 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 4.9/10; 99% of recent commits are signed; last pushed 2026-08-05. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#7 Cua — 68.8 (B) → #8 OpenCLI — 63.4 (C) → #10 UI-TARS Desktop — 56.1 (C) → #11 Magentic-UI — 56.0 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-20
Rank Moved
Rank rose 14 spots (#245 → #231)
2026-07-15
Rank Moved
Rank dropped 13 spots (#226 → #239)
2026-07-14
Rank Moved
Rank dropped 14 spots (#212 → #226)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/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 Steel Browser View Browser & Computer Use Report missing data
68.1
Activity sub-score · out of 100
#9
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 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-06 05:00 UTC · Repo last pushed yesterday

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
7.4k
Forks
952
Last Push
2026-08-05
yesterday
Commits (4 wk)
2
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
31
Rank Change
▼1
was #263

Analysis

HVTrust Dimensions vs Browser & Computer Use

56.5 / 100 · 100.0% confidence

Steel Browser Browser & Computer Use average (31 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.1 / 25
2.9 above 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
12.7 / 17
1.4 above avg 11.3
Maintenance60% last-push freshness · 40% commit activity
13.8 / 20
2.5 above avg 11.3
AdoptionLog-scaled stars · package downloads
9.3 / 20
1.8 below avg 11.1

Activity Inputs

68.1 / 100
StarsRepository reach
23.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
13.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.9 / 10
OpenSSF Scorecard · scanned Aug 6, 2026
Signed Commits
99%
of last 100 commits verified
Binary-Artifacts 8
Branch-Protection 4
CI-Tests 10
CII-Best-Practices 0
Code-Review 10
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 2
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Steel Browser safe?

Steel Browser 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 Steel Browser publish package provenance?
No published build provenance is currently detected for Steel 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 Steel Browser have an OpenSSF Scorecard?
Steel Browser has an OpenSSF Scorecard score of 4.9/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 Steel Browser actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Steel Browser use?
Steel Browser ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Steel Browser's commits signed?
99% of the last 100 commits to Steel 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
None detected
No MCP server signal detected.
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
  • code
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 Steel Browser?

For maintainers

HVTrust scores Steel 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
Rank 6Listed 2Delisted 1HVTrust 1Grade 1Scorecard 1
2026-07-20
Rank Moved
Rank rose 14 spots (#245 → #231)
2026-07-15
Rank Moved
Rank dropped 13 spots (#226 → #239)
2026-07-14
Rank Moved
Rank dropped 14 spots (#212 → #226)
2026-07-13
Rank Moved
Rank dropped 27 spots (#185 → #212)
2026-06-24
Rank Moved
Rank dropped 14 spots (#167 → #181)
2026-06-23
Scorecard Added
OSSF Scorecard: 4.9/10
2026-06-23
Grade Changed
Trust grade D → C
2026-06-23
Rank Moved
Rank rose 102 spots (#269 → #167)
2026-06-23
HVTrust Changed
HVTrust up 34.2pts (23.9 → 58.1)
2026-06-21
Newly Listed
First tracked at rank #265
2026-05-25
Removed From Active Tracking
Removed from active tracking
2026-05-24
Newly Listed
First tracked at rank #66
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/steel-browser.svg)](https://hvtracker.net/agents/steel-browser)
HTML:
<a href="https://hvtracker.net/agents/steel-browser"><img src="https://hvtracker.net/badge/steel-browser.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