Security Deep Dive
blackcandy
Security posture and CVE patch evidence from tracked releases.
17 high-severity dependency CVEs affects v3.2.0.
Review the dependency vulnerabilities below.
Trust Signals — 1 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
2d stale
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
0.25 / 2.5
⚠ No direct scan — 0c/17h 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 34.8/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
1.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
6.5
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 34.8/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
17
Medium
13
Low
4
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2019-20149 | high | — | kind-of | 6.0.2 | v3.2.0 |
| CVE-2020-7788 | high | — | ini | 1.3.5 | v3.2.0 |
| CVE-2022-25883 | high | — | semver | 7.3.7 | v3.2.0 |
| CVE-2022-3517 | high | — | minimatch | 3.0.4 | v3.2.0 |
| CVE-2024-21538 | high | — | cross-spawn | 7.0.3 | v3.2.0 |
| CVE-2024-4068 | high | — | braces | 3.0.2 | v3.2.0 |
| CVE-2025-68696 | high | — | httparty | 0.23.2 | v3.2.0 |
| CVE-2026-26996 | high | — | minimatch | 3.0.4 | v3.2.0 |
| CVE-2026-27903 | high | — | minimatch | 3.0.4 | v3.2.0 |
| CVE-2026-27904 | high | — | minimatch | 3.0.4 | v3.2.0 |
| CVE-2026-29063 | high | — | immutable | 4.1.0 | v3.2.0 |
| CVE-2026-32141 | high | — | flatted | 3.2.5 | v3.2.0 |
| CVE-2026-33228 | high | — | flatted | 3.2.5 | v3.2.0 |
| CVE-2026-33671 | high | — | picomatch | 2.3.1 | v3.2.0 |
| CVE-2026-41316 | high | — | erb | 6.0.2 | v3.2.0 |
| CVE-2026-42246 | high | — | net-imap | 0.6.3 | v3.2.0 |
| GHSA-c4rq-3m3g-8wgx | high | — | nokogiri | 1.19.2 | v3.2.0 |
| CVE-2023-44270 | medium | — | postcss | 8.4.27 | v3.2.0 |
| CVE-2024-4067 | medium | — | micromatch | 4.0.5 | v3.2.0 |
| CVE-2024-55565 | medium | — | nanoid | 3.3.6 | v3.2.0 |
| CVE-2025-64718 | medium | — | js-yaml | 4.1.0 | v3.2.0 |
| CVE-2025-69873 | medium | — | ajv | 6.12.6 | v3.2.0 |
| CVE-2026-33672 | medium | — | picomatch | 2.3.1 | v3.2.0 |
| CVE-2026-33750 | medium | — | brace-expansion | 1.1.11 | v3.2.0 |
| CVE-2026-41305 | medium | — | postcss | 8.4.27 | v3.2.0 |
| CVE-2026-42256 | medium | — | net-imap | 0.6.3 | v3.2.0 |
| CVE-2026-42257 | medium | — | net-imap | 0.6.3 | v3.2.0 |
| CVE-2026-42258 | medium | — | net-imap | 0.6.3 | v3.2.0 |
| GHSA-67mh-4wv8-2f99 | medium | — | esbuild | 0.18.17 | v3.2.0 |
| GHSA-v2fc-qm4h-8hqv | medium | — | nokogiri | 1.19.2 | v3.2.0 |
| CVE-2017-16137 | low | — | debug | 4.1.1 | v3.2.0 |
| CVE-2025-5889 | low | — | brace-expansion | 1.1.11 | v3.2.0 |
| CVE-2025-66803 | low | — | @hotwired/turbo | 8.0.13 | v3.2.0 |
| CVE-2026-42245 | low | — | net-imap | 0.6.3 | v3.2.0 |
Showing 34 of 34