How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 10:05 UTC·Repo last pushed today
Activity & Reach
Stars
10.9k
Forks
718
Last Push
2026-06-04
today
Commits (4 wk)
258
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
149
Rank Change
NEW
Analysis
HVTrust Dimensions
43.9 / 100 · 67.0% confidence
Safety / IntegrityOSSF, provenance, signatures
9.6 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
9.7 / 20
Activity Inputs
87.5 / 100
StarsRepository reach
24.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.3 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
41%
of last 100 commits verified
Is Headroom safe?
Public trust evidence for Headroom is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Headroom publish package provenance?
Yes. Headroom's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Headroom have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Headroom. 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 Headroom actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Headroom use?
Headroom ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Headroom's commits signed?
41% of the last 100 commits to Headroom 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Headroom?
HVTrust scores Headroom 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.
