Better Harness
An open-source Harness Engineering platform for coding agents—define harnesses as code, run controlled experiments, inspect evidence, and compare outcomes. Turn task evidence into actionable team and organization insights.
Is Better Harness safe? Strong public trust posture, backed by multiple independent signals.
Compare Better Harness
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Better Harness scores 79.1/100 (Grade B), ranked #19 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.5/10; 10% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →
How Better Harness compares in Agent Skills
- #17 Modlens 80.9 +1.8
- #18 Dsh Agent Teams 80.5 +1.4
- #19 Better Harness 79.1 this agent
- #20 Waza 78.9 −0.2
- #21 Obsidian Wiki 78.9 −0.2
Bars show each HVTrust score; the tick marks Better Harness’s 79.1.
Where the 79.1 comes from
HVTrust dimensions vs the Agent Skills average
79.1 / 100 · 100.0% confidenceBetter Harness Agent Skills average (351 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
80.7 / 100Supply Chain Trust
Common questions about Better Harness
Does Better Harness publish package provenance?
Does Better Harness have an OpenSSF Scorecard?
Is Better Harness actively maintained?
What license does Better Harness use?
Are Better Harness's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Better Harness'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.
Maintain Better Harness?
For maintainers
HVTrust scores Better Harness 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/better-harness)
<a href="https://hvtracker.net/agents/better-harness"><img src="https://hvtracker.net/badge/better-harness.svg" alt="HVTrust"></a>
Other agents in Agent Skills
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