Is MLflow safe?
MLflow scores 88.2/100 (Grade A), ranked #17 of 418 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
OSSF Scorecard rates its supply-chain practices 5.5/10;
100% of recent commits are signed;
last pushed 2026-07-18. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Strong public trust posture, backed by multiple independent signals.
88.2/100 · Grade A
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
19.4/25
What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
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. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-19 08:02 UTC·Repo last pushed yesterday
OpenSSF Scorecard · scanned Jun 20, 2026 (refresh pending)
Signed Commits
100%
of last 100 commits verified
Code-Review9
Maintained10
CII-Best-Practices0
Security-Policy10
License10
Dangerous-Workflow0
Pinned-Dependencies-1
Signed-Releases0
Token-Permissions10
Branch-Protection3
Packaging10
Binary-Artifacts10
SAST0
Fuzzing0
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.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 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.
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
high confidence
Implemented
MLflow appears to expose MCP server capabilities.
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
database
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 MLflow'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: Amazon Bedrock, Anthropic, Google Gemini, OpenAI, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
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.
