Security Deep Dive
hindsight
Security posture and CVE patch evidence from tracked releases.
2 high-severity dependency CVEs affects v0.7.2.
Review the dependency vulnerabilities below.
Versions by Severity
CVEs are attributed to tracked releases published before the patch release.
| Version | Published | C | H | M | L | KEV | Notes |
|---|---|---|---|---|---|---|---|
| v0.7.2 | 2026-06-02 | — | — | — | — | — |
Latest
|
| v0.7.1 | 2026-05-28 | — | — | — | — | — |
—
|
| v0.7.0 | 2026-05-27 | — | — | — | — | — |
—
|
| v0.6.2 | 2026-05-14 | — | — | — | — | — |
—
|
| v0.6.1 | 2026-05-08 | — | — | — | — | — |
Patches
CVE-2023-4863
Patches
CVE-2026-42208
|
| v0.6.0 | 2026-05-05 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.5.6 | 2026-04-28 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.5.5 | 2026-04-28 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.5.4 | 2026-04-22 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.5.3 | 2026-04-17 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.5.2 | 2026-04-15 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.5.1 | 2026-04-13 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.5.0 | 2026-04-08 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.4.22 | 2026-03-31 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.4.21 | 2026-03-30 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.4.20 | 2026-03-24 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.4.19 | 2026-03-18 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.4.18 | 2026-03-13 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.4.17 | 2026-03-10 | 1 | 1 | — | — | KEV 2 |
—
|
| v0.4.16 | 2026-03-05 | 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.00 / 4.0
⚠ Estimated — not yet collected
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.0
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/100OpenSSF 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 | — | v0.6.1 | — | — | KEV |
| CVE-2026-42208 | CRITICAL | 98%ile | — | v0.6.1 | — | — | 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
2
Medium
3
Low
0
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-42561 | high | — | python-multipart | 0.0.22 | v0.6.1 |
| GHSA-5478-66c3-rhxr | high | — | @chenglou/pretext | 0.0.3 | v0.6.1 |
| CVE-2025-4143 | medium | — | @cloudflare/workers-oauth-provider | 0.0.4 | v0.6.1 |
| CVE-2025-4144 | medium | — | @cloudflare/workers-oauth-provider | 0.0.4 | v0.6.1 |
| CVE-2026-40347 | medium | — | python-multipart | 0.0.22 | v0.6.1 |
Showing 5 of 338