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. Full methodology →
Signals refreshed2026-06-04 00:07 UTC·Repo last pushed 3 days ago
Rank Trend
2026-06-012026-06-03
Activity & Reach
Stars
602
Forks
150
Last Push
2026-06-01
3 days ago
Commits (4 wk)
219
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
107
Rank Change
▼1
was #99
Analysis
HVTrust Dimensions
62.7 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
14.4 / 17
MaintenanceFreshness and commits
19.8 / 20
AdoptionStars and downloads
6.7 / 20
Activity Inputs
76.8 / 100
StarsRepository reach
16.7 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
10.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.9 / 10
via deps.dev · OpenSSF
Signed Commits
47%
of last 100 commits verified
Maintained10
Security-Policy10
Dependency-Update-Tool10
Token-Permissions10
Code-Review3
Dangerous-Workflow10
Binary-Artifacts10
CII-Best-Practices0
Signed-Releases-1
License9
Packaging10
Branch-Protection-1
Fuzzing0
Pinned-Dependencies0
SAST6
Vulnerabilities0
CI-Tests10
Contributors10
Is Traceroot safe?
Traceroot 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 Traceroot publish package provenance?
No published build provenance is currently detected for Traceroot. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Traceroot have an OpenSSF Scorecard?
Traceroot has an OpenSSF Scorecard score of 6.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Traceroot actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does Traceroot use?
Traceroot ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Traceroot's commits signed?
47% of the last 100 commits to Traceroot 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 Traceroot?
HVTrust scores Traceroot 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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
