Security Deep Dive
manyfold
Security posture and CVE patch evidence from tracked releases.
11 high-severity dependency CVEs affects v0.143.0.
Review the dependency vulnerabilities below.
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.25 / 0.5
No EPSS data
freshness
1.00 / 1.0
1d stale
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
0.25 / 2.5
⚠ No direct scan — 0c/11h transitive CVEs
patch speed
0.50 / 0.5
⚠ Estimated — no CVE patch history
kev exposure
1.50 / 1.5
No KEV exposure
supply chain risk
-1.50 / 10.0
Risk 22.4/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
1.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
7.8
10%
Provenance trust
provenance trust
5.0
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
8.5
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 22.4/100OpenSSF Badge
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
0
High
11
Medium
3
Low
1
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2025-64756 | high | — | glob | 10.4.5 | v0.139.1 |
| CVE-2026-23745 | high | — | tar | 6.2.1 | v0.139.1 |
| CVE-2026-23950 | high | — | tar | 6.2.1 | v0.139.1 |
| CVE-2026-24842 | high | — | tar | 6.2.1 | v0.139.1 |
| CVE-2026-26960 | high | — | tar | 6.2.1 | v0.139.1 |
| CVE-2026-26996 | high | — | minimatch | 9.0.5 | v0.139.1 |
| CVE-2026-27903 | high | — | minimatch | 9.0.5 | v0.139.1 |
| CVE-2026-27904 | high | — | minimatch | 9.0.5 | v0.139.1 |
| CVE-2026-29786 | high | — | tar | 6.2.1 | v0.139.1 |
| CVE-2026-31802 | high | — | tar | 6.2.1 | v0.139.1 |
| GHSA-c4rq-3m3g-8wgx | high | — | nokogiri | 1.19.2 | v0.139.1 |
| CVE-2026-33750 | medium | — | brace-expansion | 5.0.2 | v0.139.1 |
| CVE-2026-40295 | medium | — | devise | 5.0.3 | v0.139.1 |
| GHSA-v2fc-qm4h-8hqv | medium | — | nokogiri | 1.19.2 | v0.139.1 |
| CVE-2025-5889 | low | — | brace-expansion | 2.0.1 | v0.139.1 |
Showing 15 of 15