Autoharness
Autoharness — a self-learning skill layer for Claude Code — distills skills from your real sessions, updates them as you work, and prunes the ones that stop getting used. No daemon, no benchmark.
Is Autoharness safe? Promising trust profile, but some evidence still deserves review.
Compare Autoharness
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Autoharness scores 59.3/100 (Grade C), ranked #111 of 351 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; 60% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Autoharness compares in Agent Skills
- #109 Chatbox 59.4 +0.1
- #110 9Router 59.3 ±0
- #111 Autoharness 59.3 this agent
- #112 Builderio Skills 59.2 −0.1
- #113 Md2Wechat Skill 59.0 −0.3
Bars show each HVTrust score; the tick marks Autoharness’s 59.3.
Where the 59.3 comes from
HVTrust dimensions vs the Agent Skills average
59.3 / 100 · 100.0% confidenceAutoharness 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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
76.8 / 100Supply Chain Trust
Common questions about Autoharness
Does Autoharness publish package provenance?
Does Autoharness have an OpenSSF Scorecard?
Is Autoharness actively maintained?
What license does Autoharness use?
Are Autoharness'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 Autoharness'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 Autoharness?
For maintainers
HVTrust scores Autoharness 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/autoharness)
<a href="https://hvtracker.net/agents/autoharness"><img src="https://hvtracker.net/badge/autoharness.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON