Security Deep Dive
dynamodb-dashboard
Security posture and CVE patch evidence from tracked releases.
1 critical dependency CVE affects v1.25.6.
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
1.00 / 1.0
Up to date
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
0.00 / 2.5
⚠ No direct scan — 1c/12h 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 29.1/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
7.1
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 29.1/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
12
Medium
18
Low
7
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-25896 | critical | — | fast-xml-parser | 5.2.5 | — |
| CVE-2026-25128 | high | — | fast-xml-parser | 5.2.5 | — |
| CVE-2026-26278 | high | — | fast-xml-parser | 5.2.5 | — |
| CVE-2026-26996 | high | — | minimatch | 9.0.5 | — |
| CVE-2026-27903 | high | — | minimatch | 9.0.5 | — |
| CVE-2026-27904 | high | — | minimatch | 9.0.5 | — |
| CVE-2026-33036 | high | — | fast-xml-parser | 5.2.5 | — |
| CVE-2026-33671 | high | — | picomatch | 2.3.1 | — |
| CVE-2026-34769 | high | — | electron | 33.3.1 | — |
| CVE-2026-34770 | high | — | electron | 33.3.1 | — |
| CVE-2026-34771 | high | — | electron | 33.3.1 | — |
| CVE-2026-34774 | high | — | electron | 33.3.1 | — |
| CVE-2026-44665 | high | — | fast-xml-builder | 1.1.5 | — |
| CVE-2025-15284 | medium | — | qs | 6.13.0 | — |
| CVE-2025-55305 | medium | — | electron | 33.3.1 | — |
| CVE-2025-69873 | medium | — | ajv | 6.12.6 | — |
| CVE-2026-33349 | medium | — | fast-xml-parser | 5.2.5 | — |
| CVE-2026-33532 | medium | — | yaml | 2.8.0 | — |
| CVE-2026-33672 | medium | — | picomatch | 2.3.1 | — |
| CVE-2026-33750 | medium | — | brace-expansion | 1.1.11 | — |
| CVE-2026-34765 | medium | — | electron | 33.3.1 | — |
| CVE-2026-34767 | medium | — | electron | 33.3.1 | — |
| CVE-2026-34772 | medium | — | electron | 33.3.1 | — |
| CVE-2026-34773 | medium | — | electron | 33.3.1 | — |
| CVE-2026-34775 | medium | — | electron | 33.3.1 | — |
| CVE-2026-34776 | medium | — | electron | 33.3.1 | — |
| CVE-2026-34777 | medium | — | electron | 33.3.1 | — |
| CVE-2026-34778 | medium | — | electron | 33.3.1 | — |
| CVE-2026-34779 | medium | — | electron | 33.3.1 | — |
| CVE-2026-41650 | medium | — | fast-xml-parser | 5.2.5 | — |
| CVE-2026-44664 | medium | — | fast-xml-builder | 1.1.5 | — |
| CVE-2025-5889 | low | — | brace-expansion | 1.1.11 | — |
| CVE-2026-2391 | low | — | qs | 6.13.0 | — |
| CVE-2026-27942 | low | — | fast-xml-parser | 5.2.5 | — |
| CVE-2026-34764 | low | — | electron | 33.3.1 | — |
| CVE-2026-34766 | low | — | electron | 33.3.1 | — |
| CVE-2026-34768 | low | — | electron | 33.3.1 | — |
| CVE-2026-34781 | low | — | electron | 33.3.1 | — |
Showing 38 of 38