Is Leon safe?
Leon scores 38.2/100 (Grade D), ranked #291 of 328 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.5/10;
89% of recent commits are signed;
last pushed 2026-06-29. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
38.2/100 · Grade D
Strongest Signal
Maintenance
16.4/20
Weakest Signal
Safety / Integrity
10.1/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-06-24
Rank Moved
Rank dropped 36 spots (#247 → #283)
2026-06-23
Rank Moved
Rank dropped 19 spots (#228 → #247)
2026-06-22
Rank Moved
Rank dropped 10 spots (#218 → #228)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 4.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
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. 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 →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed 12 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
17.4k
Forks
1.4k
Last Push
2026-06-29
12 days ago
Commits (4 wk)
19
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
94
Rank Change
=
was #291
Analysis
HVTrust Dimensions
38.2 / 100 · 67.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.1 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.3 / 17
MaintenanceFreshness and commits
16.4 / 20
AdoptionStars and downloads
10.2 / 20
Activity Inputs
79.8 / 100
StarsRepository reach
25.4 / 30
FreshnessLast push recency
23.3 / 25
ActivityRecent commits
16.2 / 25
CommunityFork signal
14.7 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.5 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
89%
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?
Maintained. Last push was 12 days ago.
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?
89% 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.
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 Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
search
shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
How this surface has changed
Detected changes to Leon'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.
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI
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.
