Security Deep Dive
Splunk Attack Range
Security posture and CVE patch evidence from tracked releases.
20 high-severity dependency CVEs affects v5.0.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
25d stale
scorecard
1.40 / 4.0
Score 3.5/10
cve health
1.50 / 2.5
No open 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 41.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
6.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
5.9
10%
Provenance trust
provenance trust
3.5
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 41.0/100Scorecard
Scorecard 3.5/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Maintained | 1 | 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1 |
| Code-Review | 2 | Found 4/14 approved changesets -- score normalized to 2 |
| Packaging | -1 | packaging workflow not detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0 | project is not fuzzed |
| License | 10 | license file detected |
| Signed-Releases | -1 | no releases found |
| Branch-Protection | -1 | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| Security-Policy | 0 | security policy file not detected |
| Pinned-Dependencies | 1 | dependency not pinned by hash detected -- score normalized to 1 |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
OpenSSF 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
20
Medium
26
Low
7
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2024-34069 | high | — | werkzeug | 3.0.1 | — |
| CVE-2025-66418 | high | — | urllib3 | 2.2.3 | — |
| CVE-2025-66471 | high | — | urllib3 | 2.2.3 | — |
| CVE-2026-21226 | high | — | azure-core | 1.31.0 | — |
| CVE-2026-21441 | high | — | urllib3 | 2.2.3 | — |
| CVE-2026-22774 | high | — | devalue | 5.6.1 | — |
| CVE-2026-22775 | high | — | devalue | 5.6.1 | — |
| CVE-2026-23527 | high | — | h3 | 1.15.4 | — |
| CVE-2026-26007 | high | — | cryptography | 44.0.1 | — |
| CVE-2026-27606 | high | — | rollup | 4.55.1 | — |
| CVE-2026-29074 | high | — | svgo | 4.0.0 | — |
| CVE-2026-32597 | high | — | pyjwt | 2.9.0 | — |
| CVE-2026-33128 | high | — | h3 | 1.15.4 | — |
| CVE-2026-33671 | high | — | picomatch | 4.0.3 | — |
| CVE-2026-35209 | high | — | defu | 6.1.4 | — |
| CVE-2026-39363 | high | — | vite | 6.4.1 | — |
| CVE-2026-42215 | high | — | gitpython | 3.1.43 | — |
| CVE-2026-42284 | high | — | gitpython | 3.1.43 | — |
| CVE-2026-44243 | high | — | gitpython | 3.1.43 | — |
| CVE-2026-44244 | high | — | gitpython | 3.1.43 | — |
| CVE-2024-47081 | medium | — | requests | 2.32.3 | — |
| CVE-2024-49766 | medium | — | werkzeug | 3.0.1 | — |
| CVE-2024-49767 | medium | — | werkzeug | 3.0.1 | — |
| CVE-2024-6839 | medium | — | flask-cors | 5.0.0 | — |
| CVE-2024-6844 | medium | — | flask-cors | 5.0.0 | — |
| CVE-2024-6866 | medium | — | flask-cors | 5.0.0 | — |
| CVE-2025-50181 | medium | — | urllib3 | 2.2.3 | — |
| CVE-2025-50182 | medium | — | urllib3 | 2.2.3 | — |
| CVE-2025-66221 | medium | — | werkzeug | 3.0.1 | — |
| CVE-2026-21860 | medium | — | werkzeug | 3.0.1 | — |
| CVE-2026-25545 | medium | — | @astrojs/node | 9.5.2 | — |
| CVE-2026-25645 | medium | — | requests | 2.32.3 | — |
| CVE-2026-27199 | medium | — | werkzeug | 3.0.1 | — |
| CVE-2026-27729 | medium | — | @astrojs/node | 9.5.2 | — |
| CVE-2026-27829 | medium | — | @astrojs/node | 9.5.2 | — |
| CVE-2026-29772 | medium | — | @astrojs/node | 9.5.2 | — |
| CVE-2026-30226 | medium | — | devalue | 5.6.1 | — |
| CVE-2026-33672 | medium | — | picomatch | 4.0.3 | — |
| CVE-2026-39365 | medium | — | vite | 6.4.1 | — |
| CVE-2026-41067 | medium | — | astro | 5.16.9 | — |
| CVE-2026-41305 | medium | — | postcss | 8.5.6 | — |
| CVE-2026-41322 | medium | — | @astrojs/node | 9.5.2 | — |
| GHSA-4hxc-9384-m385 | medium | — | h3 | 1.15.4 | — |
| GHSA-72gr-qfp7-vwhw | medium | — | h3 | 1.15.4 | — |
| GHSA-v3rj-xjv7-4jmq | medium | — | smol-toml | 1.6.0 | — |
| GHSA-wr4h-v87w-p3r7 | medium | — | h3 | 1.15.4 | — |
| CVE-2026-24001 | low | — | diff | 5.2.0 | — |
| CVE-2026-27205 | low | — | flask | 3.0.0 | — |
| CVE-2026-33769 | low | — | astro | 5.16.9 | — |
| CVE-2026-34073 | low | — | cryptography | 44.0.1 | — |
| GHSA-33hq-fvwr-56pm | low | — | devalue | 5.6.1 | — |
| GHSA-8qm3-746x-r74r | low | — | devalue | 5.6.1 | — |
| GHSA-mwv9-gp5h-frr4 | low | — | devalue | 5.6.1 | — |
Showing 53 of 58