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 20:15 UTC·Repo last pushed 171 days ago
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
3.0k
Forks
399
Last Push
2025-12-15
171 days ago
Commits (4 wk)
0
Downloads (7d)
66,392
pypi
HN mentions (30d)
1
Open Issues
35
Rank Change
▼9
was #136
Analysis
HVTrust Dimensions
50.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.6 / 17
MaintenanceFreshness and commits
0.6 / 20
AdoptionStars and downloads
14.8 / 20
Activity Inputs
34.4 / 100
StarsRepository reach
20.9 / 30
FreshnessLast push recency
1.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.0 / 10
via deps.dev · OpenSSF
Signed Commits
60%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests7
CII-Best-Practices0
Code-Review8
Contributors0
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies0
SAST8
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities10
Is LLM Guard safe?
Public trust evidence for LLM Guard 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 LLM Guard publish package provenance?
No published build provenance is currently detected for LLM Guard. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does LLM Guard have an OpenSSF Scorecard?
LLM Guard has an OpenSSF Scorecard score of 6.0/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 LLM Guard actively maintained?
Slowing down. Last push was 171 days ago — keep an eye on whether activity resumes.
What license does LLM Guard use?
LLM Guard ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are LLM Guard's commits signed?
60% of the last 100 commits to LLM Guard 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 LLM Guard?
HVTrust scores LLM Guard 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.
