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
26.3k
Forks
5.8k
Last Push
2026-06-03
yesterday
Commits (4 wk)
608
Downloads (7d)
8,813,855
pypi
HN mentions (30d)
2
Open Issues
2068
Rank Change
=
was #9
Analysis
HVTrust Dimensions
90.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
19.5 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
13.3 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
19.9 / 20
Activity Inputs
94.0 / 100
StarsRepository reach
26.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.5 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.6 / 10
via deps.dev · OpenSSF
Signed Commits
100%
of last 100 commits verified
Code-Review10
Maintained10
Security-Policy10
CII-Best-Practices0
Dangerous-Workflow0
License10
Pinned-Dependencies-1
Token-Permissions10
Signed-Releases0
Binary-Artifacts10
Branch-Protection3
Packaging10
Fuzzing0
SAST0
Is MLflow safe?
Public supply-chain signals for MLflow are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but MLflow carries less obvious unverified-evidence risk than projects with thin signals.
Does MLflow publish package provenance?
Yes. MLflow's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does MLflow have an OpenSSF Scorecard?
MLflow has an OpenSSF Scorecard score of 5.6/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 MLflow actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MLflow use?
MLflow ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MLflow's commits signed?
100% of the last 100 commits to MLflow 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 MLflow?
HVTrust scores MLflow 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.
