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 20:01 UTC·Repo last pushed yesterday
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
17.3k
Forks
1.4k
Last Push
2026-06-03
yesterday
Commits (4 wk)
102
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
108
Rank Change
▼9
was #164
Analysis
HVTrust Dimensions
41.9 / 100 · 67.0% confidence
Safety / IntegrityOSSF, provenance, signatures
9.7 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.3 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
10.2 / 20
Activity Inputs
90.0 / 100
StarsRepository reach
25.4 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.7 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.5 / 10
via deps.dev · OpenSSF
Signed Commits
82%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection8
CI-Tests-1
CII-Best-Practices0
Code-Review0
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases0
Token-Permissions0
Vulnerabilities0
Is Leon safe?
Public trust evidence for Leon 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 Leon publish package provenance?
No published build provenance is currently detected for Leon. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Leon have an OpenSSF Scorecard?
Leon has an OpenSSF Scorecard score of 4.5/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 Leon actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Leon use?
Leon ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Leon's commits signed?
82% of the last 100 commits to Leon 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 Leon?
HVTrust scores Leon 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) · npm Registry (downloads, provenance) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
