Dev Browser vs Waza
An independent, evidence-based trust comparison of Dev Browser and Waza, two Agent Skills projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Waza leads on trust — 68.9/100 (Grade B) vs 65.3/100 (Grade B), a 3.6-point gap. Full breakdown below.
| Signal | Dev BrowserSawyerHood/dev-browser | Wazatw93/Waza |
|---|---|---|
| HVTrust score | 65.3 | 68.9 |
| Evidence grade | B | B |
| Coverage grade | B | B |
| Overall rank | #5 | #4 |
| Rank in Agent Skills | #5 | #4 |
| GitHub stars | 6.5k | 6.8k |
| Last updated | 28d ago | 3d ago |
| Build provenance | Yes | Yes |
| OSSF Scorecard | — | — |
| License | MIT | MIT |
| Downloads | 5k/wk | 265/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 8.8 | 7.8 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 8.5 | 8.5 |
| Maintenance / 20 | 12.5 | 18.5 |
| Adoption / 20 | 14.1 | 12.4 |
| Runtime capability surface (full matrix) | ||
| MCP server | — | — |
| External providers | 1 — Anthropic | — |
| Requires API keys | No | No |
| Plugin surface | plugins | plugins |
| Provenance drift | Match | Match |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.3 →