Security Deep Dive
Hindsight
Security posture and CVE patch evidence from tracked releases.
1 critical dependency CVE affects v2026.04.
Audit transitive dependencies; consider upgrading or pinning replacements.
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
0.99 / 1.0
32d stale
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
1.00 / 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 37.7/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
4.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
6.2
10%
Provenance trust
provenance trust
5.0
40%
Maintainer health
maintainer health
9.9
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 37.7/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
1
High
16
Medium
1
Low
0
Unknown
1
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2022-31799 | critical | — | bottle | — | — |
| CVE-2012-4571 | high | — | keyring | — | — |
| CVE-2012-5577 | high | — | keyring | — | — |
| CVE-2012-5578 | high | — | keyring | — | — |
| CVE-2013-1633 | high | — | setuptools | — | — |
| CVE-2014-3137 | high | — | bottle | — | — |
| CVE-2015-5237 | high | — | protobuf | — | — |
| CVE-2016-9964 | high | — | bottle | — | — |
| CVE-2018-15560 | high | — | pycryptodome | — | — |
| CVE-2022-1941 | high | — | protobuf | — | — |
| CVE-2022-40897 | high | — | setuptools | — | — |
| CVE-2023-52323 | high | — | pycryptodomex | — | — |
| CVE-2023-52323 | high | — | pycryptodome | — | — |
| CVE-2024-6345 | high | — | setuptools | — | — |
| CVE-2025-4565 | high | — | protobuf | — | — |
| CVE-2025-47273 | high | — | setuptools | — | — |
| CVE-2026-0994 | high | — | protobuf | — | — |
| CVE-2020-28473 | medium | — | bottle | — | — |
| CVE-2021-22570 | unknown | — | protobuf | — | — |
Showing 19 of 19