updated 2026-08-12 05:02 UTC

Dev Browser

SawyerHood/dev-browser

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

Agent Skills TypeScript Grade B Listed MIT
65.3/100
Rank #5 of 148
Compare Dev Browser

How does it stack up against its Agent Skills 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 B · 3/5 signals
Last push
2026-07-15 · 28d ago
Recent change
New

Is Dev Browser safe? Dev Browser scores 65.3/100 (Grade B), ranked #5 of 148 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; no OSSF Scorecard result yet; 27% of recent commits are signed; last pushed 2026-07-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#3 Better Harness — 70.6 (B) → #4 Waza — 68.9 (B) → #6 Pg Aiguide — 62.4 (C) → #7 Open Code Review — 46.3 (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-11
Newly Listed
First tracked at rank #5
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with Larksuite Cli Get email alerts for Dev Browser View Agent Skills Report missing data
63.7
Activity sub-score · out of 100
#5
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-08-12 05:02 UTC · Repo last pushed 28 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
6.5k
Forks
425
Last Push
2026-07-15
28 days ago
Commits (4 wk)
3
Downloads (7d)
4,885
npm
HN mentions (30d)
—
Open Issues
6
Rank Change
=
was #5

Analysis

HVTrust Dimensions vs Agent Skills

65.3 / 100 · 100.0% confidence

Dev Browser Agent Skills average (148 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.8 / 25
6.1 above avg 2.7
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.7 above avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.5
Maintenance60% last-push freshness · 40% commit activity
12.5 / 20
2.6 below avg 15.1
AdoptionLog-scaled stars · package downloads
14.1 / 20
4.9 above avg 9.2

Activity Inputs

63.7 / 100
StarsRepository reach
22.9 / 30
FreshnessLast push recency
21.1 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
12.2 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
27%
of last 100 commits verified

Is Dev Browser safe?

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?
No OpenSSF Scorecard data is currently published for Dev 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 Dev Browser actively maintained?
Maintained. Last push was 28 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?
27% 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.

Compare Dev Browser head-to-head

Dev Browser vs Larksuite Cli → Dev Browser vs Cc Safety Net → Dev Browser vs Better Harness →

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
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared 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 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
Listed 1
2026-08-11
Newly Listed
First tracked at rank #5
GitHub → npm: dev-browser

Embed Badge Badge guide for maintainers →

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