Is Dev Browser safe to use?

Dev Browser has an HVTrust score of 76.5/100 (Grade B), ranked #24 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Dev Browser?

Dev Browser scores 76.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 6.6k GitHub stars and is categorized under Agent Skills.

Dev Browser

SawyerHood/dev-browser

A Claude Skill to give your agent the ability to use a web browser

Agent Skills TypeScript Listed MIT

Is Dev Browser safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.0 / 10

Provenance Attested

Signed commits 36%

Last push 21d ago

Compare Dev Browser

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Dev Browser scores 76.5/100 (Grade B), ranked #24 of 351 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.0/10; 36% of recent commits are signed; last pushed 2026-09-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How Dev Browser compares in Agent Skills

Bars show each HVTrust score; the tick marks Dev Browser’s 76.5.

Where the 76.5 comes from

HVTrust dimensions vs the Agent Skills average

76.5 / 100 · 100.0% confidence

Dev Browser Agent Skills average (351 agents)

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

14.3 / 25

6.2 above avg 8.1

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.6 above avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

11.9 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

14.6 / 20

in line with avg 14.2

AdoptionLog-scaled stars · package downloads

14.0 / 20

5.0 above avg 9.0

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.0/10. Tighten the weakest checks to improve public safety evidence.

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

Compare with another agent Get email alerts for Dev Browser View Agent Skills Report missing data

69.8

Activity sub-score · out of 100

#24

In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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-26

Activity & Reach

Stars

6.6k

Forks

435

Last Push

2026-09-05

21 days ago

Commits (4 wk)

Downloads (7d)

4,302

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #24

Analysis

Activity Inputs

69.8 / 100

StarsRepository reach

22.9 / 30

FreshnessLast push recency

22.1 / 25

ActivityRecent commits

12.5 / 25

CommunityFork signal

12.3 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.0 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

36%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Common questions about Dev Browser

Public supply-chain signals for Dev Browser are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Dev Browser carries less obvious unverified-evidence risk than projects with thin signals.

Does Dev Browser publish package provenance?

Yes. Dev Browser's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Dev Browser have an OpenSSF Scorecard?

Dev Browser has an OpenSSF Scorecard score of 4.0/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 Dev Browser actively maintained?

Maintained. Last push was 21 days ago.

What license does Dev Browser use?

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

Are Dev Browser's commits signed?

36% of the last 100 commits to Dev 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

Declared

MCP support appears present, but direct server implementation is less certain.

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

Declared

Declared plugin/integration 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 Dev 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-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-05

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

2026-09-05

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain Dev Browser?

For maintainers

HVTrust scores Dev 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-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 257 spots (#280 → #23)

2026-09-23

HVTrust Changed

HVTrust up 47.6pts (28.9 → 76.5)

2026-09-22

Newly Listed

First tracked at rank #280

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-05

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

2026-09-05

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-05

Scorecard Added

OSSF Scorecard: 4.0/10

2026-09-05

Grade Changed

Trust grade D → B

2026-09-05

Rank Moved

Rank rose 207 spots (#224 → #17)

2026-09-05

HVTrust Changed

HVTrust up 33.7pts (42.3 → 76.0)

2026-09-04

Rank Moved

Rank rose 16 spots (#240 → #224)

2026-09-04

HVTrust Changed

HVTrust up 3.4pts (38.9 → 42.3)

2026-09-04

Activity Score Changed

Activity score up 18pts (53 → 72)

2026-09-03

Grade Changed

Trust grade C → D

2026-09-03

Rank Moved

Rank dropped 196 spots (#44 → #240)

2026-09-03

HVTrust Changed

HVTrust down 22.6pts (61.5 → 38.9)

2026-08-26

Rank Moved

Rank dropped 17 spots (#8 → #25)

2026-08-14

Grade Changed

Trust grade B → C

2026-08-14

Activity Score Changed

Activity score down 8pts (64 → 56)

2026-08-11

Newly Listed

First tracked at rank #5

GitHub → npm: dev-browser

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Skills

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