How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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 yesterday
Rank Trend
2026-06-022026-06-03
Activity & Reach
Stars
42.8k
Forks
3.5k
Last Push
2026-06-03
yesterday
Commits (4 wk)
43
Downloads (7d)
3,307,260
pypi
HN mentions (30d)
102
Open Issues
298
Rank Change
=
was #14
Analysis
HVTrust Dimensions
88.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
19.3 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
13.3 / 17
MaintenanceFreshness and commits
18.5 / 20
AdoptionStars and downloads
19.8 / 20
Activity Inputs
89.8 / 100
StarsRepository reach
27.8 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
20.5 / 25
CommunityFork signal
16.5 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.7 / 10
via deps.dev · OpenSSF
Signed Commits
93%
of last 100 commits verified
Maintained10
Code-Review8
CII-Best-Practices0
Security-Policy10
License10
Signed-Releases-1
Branch-Protection-1
Dangerous-Workflow10
Packaging-1
Token-Permissions0
Fuzzing0
Binary-Artifacts8
SAST0
Pinned-Dependencies0
Is Gradio safe?
Public supply-chain signals for Gradio are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Gradio carries less obvious unverified-evidence risk than projects with thin signals.
Does Gradio publish package provenance?
Yes. Gradio's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Gradio have an OpenSSF Scorecard?
Gradio has an OpenSSF Scorecard score of 5.7/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 Gradio actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Gradio use?
Gradio ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Gradio's commits signed?
93% of the last 100 commits to Gradio 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.
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 Gradio?
HVTrust scores Gradio 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.
