Security Deep Dive
Damselfly
Security posture and CVE patch evidence from tracked releases.
1 open KEV CVE affects 4.5.3.
KEV-listed CVEs are confirmed exploited in the wild — patch urgently.
Trust Signals — 2 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
22d stale
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
0.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 77.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
2.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
2.3
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 77.0/100OpenSSF Badge
Badge indicates adherence to open-source best practices.
1 open CVE against Damselfly
Sorted by KEV-listed first, then longest exposure.| CVE | Severity | CVSS | EPSS | Days open | KEV | Status |
|---|---|---|---|---|---|---|
| CVE-2023-5217 | HIGH | 8.8 | 89%ile | 976d | KEV | Affects vLATEST |
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
0
High
5
Medium
15
Low
3
Unknown
0
1 dependency vulnerabilities are in KEV.
CISA confirmed these vulnerabilities are actively exploited. Treat as critical priority.
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2023-5217 | high | KEV | electron | 20.0.0 | — |
| CVE-2026-34769 | high | — | electron | 20.0.0 | — |
| CVE-2026-34770 | high | — | electron | 20.0.0 | — |
| CVE-2026-34771 | high | — | electron | 20.0.0 | — |
| CVE-2026-34774 | high | — | electron | 20.0.0 | — |
| CVE-2022-36077 | medium | — | electron | 20.0.0 | — |
| CVE-2023-29198 | medium | — | electron | 20.0.0 | — |
| CVE-2023-39956 | medium | — | electron | 20.0.0 | — |
| CVE-2023-44402 | medium | — | electron | 20.0.0 | — |
| CVE-2024-46993 | medium | — | electron | 20.0.0 | — |
| CVE-2025-55305 | medium | — | electron | 20.0.0 | — |
| CVE-2026-34765 | medium | — | electron | 20.0.0 | — |
| CVE-2026-34767 | medium | — | electron | 20.0.0 | — |
| CVE-2026-34772 | medium | — | electron | 20.0.0 | — |
| CVE-2026-34773 | medium | — | electron | 20.0.0 | — |
| CVE-2026-34775 | medium | — | electron | 20.0.0 | — |
| CVE-2026-34776 | medium | — | electron | 20.0.0 | — |
| CVE-2026-34777 | medium | — | electron | 20.0.0 | — |
| CVE-2026-34778 | medium | — | electron | 20.0.0 | — |
| CVE-2026-34779 | medium | — | electron | 20.0.0 | — |
| CVE-2026-34766 | low | — | electron | 20.0.0 | — |
| CVE-2026-34768 | low | — | electron | 20.0.0 | — |
| CVE-2026-34781 | low | — | electron | 20.0.0 | — |
Showing 23 of 135