updated 2026-10-16 16:07 UTC

Dev Browser

Repository

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

Agent Skills TypeScript Listed MIT

Is Dev Browser safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.8 / 10
Provenance Attested
Signed commits 36%
Last push 41d ago
Advisories None known
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 71.3/100 (Grade B), ranked #29 of 385 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 3.8/10; 36% of recent commits are signed; no published advisory affects its latest release (dev-browser); last pushed 2026-09-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How Dev Browser could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Dev Browser and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/SawyerHood/dev-browser, MIT, last pushed 2026-09-05. 36% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Oct 14, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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 7
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked and attested

    • npm dev-browser Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: dev-browser 0.2.9. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-05 OSSF Scorecard: 4.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Dev Browser’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Dev Browser compares in Agent Skills

  1. #27 Memsearch 71.6 +0.3
  2. #28 Arcgentic 71.3 ±0
  3. #29 Dev Browser 71.3 this agent
  4. #30 ClawBio 70.2 −1.1
  5. #31 Container 69.9 −1.4

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

Where the 71.3 comes from

HVTrust dimensions vs the Agent Skills average

71.3 / 100 · 100.0% confidence

Dev Browser Agent Skills average (385 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.0 / 25
6.2 above avg 7.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.6 above avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
9.3 / 20
4.8 below avg 14.1
AdoptionLog-scaled stars · package downloads
14.6 / 20
5.6 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-10-05
Activity Score Changed
Activity score down 6pts (62 → 56)
2026-10-04
Activity Score Changed
Activity score down 7pts (69 → 62)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.8/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.
Refresh maintenance signals The repo was last pushed 41 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Dev Browser View Agent Skills Report missing data
54.5
Activity sub-score · out of 100
#29
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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 41 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
6.7k
Forks
435
Last Push
2026-09-05
41 days ago
Commits (4 wk)
0
Downloads (7d)
11,994
npm
HN mentions (30d)
—
Open Issues
10
Rank Change
=
was #29

Analysis

Activity Inputs

54.5 / 100
StarsRepository reach
22.9 / 30
FreshnessLast push recency
19.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.3 / 20

Common questions about Dev Browser

Dev 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 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 3.8/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?
Slowing down. Last push was 41 days ago — keep an eye on whether activity resumes.
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
Rank 5Score 4Grade 4HVTrust 4Listed 2MCP 2Scorecard 1Surface 1Delisted 1Provenance 1Surface 1
2026-10-05
Activity Score Changed
Activity score down 6pts (62 → 56)
2026-10-04
Activity Score Changed
Activity score down 7pts (69 → 62)
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
HVTrust 71.3 Grade B
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.4 · Raw JSON