Security Deep Dive
mlflow
Security posture and CVE patch evidence from tracked releases.
No known vulnerabilities in ts/v0.2.0.
2 CVEs patched in tracked history.
Versions by Severity
CVEs are attributed to tracked releases published before the patch release.
| Version | Published | C | H | M | L | KEV | Notes |
|---|---|---|---|---|---|---|---|
| ts/v0.2.0 | 2026-05-15 | — | — | — | — | — | |
| v3.12.0 | 2026-05-05 | 1 | 1 | — | — | KEV 2 |
—
|
| v3.11.1 | 2026-04-08 | 1 | 1 | — | — | KEV 2 |
—
|
| model-catalog/latest | 2026-04-06 | 1 | 1 | — | — | KEV 2 |
—
|
| v3.10.1 | 2026-03-05 | 1 | 1 | — | — | KEV 2 |
—
|
| v3.10.0 | 2026-02-20 | 1 | 1 | — | — | KEV 2 |
—
|
| v3.9.0 | 2026-01-29 | 1 | 1 | — | — | KEV 2 |
—
|
Trust Signals — 3 of 9 Present
Evidence already collected from releases and repository metadata.
Security Score
A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.
epss
0.00 / 0.5
Max EPSS 0.933
freshness
1.00 / 1.0
1d stale
scorecard
2.24 / 4.0
Score 5.6/10
cve health
0.00 / 2.5
No open CVEs
patch speed
0.50 / 0.5
⚠ Estimated — no CVE patch history
kev exposure
-1.50 / 1.5
KEV exposure detected
supply chain risk
-1.50 / 10.0
Risk 100.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
0.0
10%
Provenance trust
provenance trust
5.6
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
0.0
10%
How is this calculated?
The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.
Supply Chain Risk
Risk 100.0/100Scorecard
Scorecard 5.6/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 10 | all changesets reviewed |
| Maintained | 10 | 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10 |
| Security-Policy | 10 | security policy file detected |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Dangerous-Workflow | 0 | dangerous workflow patterns detected |
| License | 10 | license file detected |
| Pinned-Dependencies | -1 | internal error: internal error: invalid Dockerfile |
| Token-Permissions | 10 | GitHub workflow tokens follow principle of least privilege |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Branch-Protection | 3 | branch protection is not maximal on development and all release branches |
| Packaging | 10 | packaging workflow detected |
| Fuzzing | 0 | project is not fuzzed |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
OpenSSF Badge
Badge indicates adherence to open-source best practices.
CVE Patch History
Tracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.
CVEs Patched by Year
| CVE | Severity | EPSS | Disclosed | Fixed in | Days to fix | vs Ecosystem Median | KEV |
|---|---|---|---|---|---|---|---|
| CVE-2023-4863 | HIGH | 99%ile | — | ts/v0.2.0 | — | — | KEV |
| CVE-2026-42208 | CRITICAL | 98%ile | — | ts/v0.2.0 | — | — | KEV |
KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
0
High
0
Medium
0
Low
0
Unknown
0
No dependency CVEs match this filter.
Showing 0 of 500