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. Full methodology →
Signals refreshed2026-06-22 00:01 UTC·Repo last pushed 13 days ago
Rank Trend
2026-05-242026-06-21
Activity & Reach
Stars
7.2k
Forks
938
Last Push
2026-06-09
13 days ago
Commits (4 wk)
5
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
44
Rank Change
=
was #265
Analysis
HVTrust Dimensions
23.9 / 100 · 50.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
14.2 / 20
AdoptionStars and downloads
9.3 / 20
Activity Inputs
69.9 / 100
StarsRepository reach
23.1 / 30
FreshnessLast push recency
23.2 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
13.8 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
99%
of last 100 commits verified
Is Steel Browser safe?
Public trust evidence for Steel 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 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?
No OpenSSF Scorecard data is currently published for Steel 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 Steel Browser actively maintained?
Maintained. Last push was 13 days ago.
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
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
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?
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.2 · Raw JSON
