Skip to content
Tools / dragonfly / Security

Security Deep Dive

dragonfly

Security posture and CVE patch evidence from tracked releases.

Back to Tool

5 critical dependency CVEs affects v1.38.1.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA ✓ SBOM ✗ Security policy Monthly cadence · 25d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present
Signed releases Unknown
Latest release artifact signature Latest release
—
SLSA provenance Unknown
Attestation predicate level Latest release
—
SBOM published Present
GitHub SBOM API Latest release
Last verified: 28d ago
SECURITY.md Absent
GitHub repository metadata Repository policy
Checked: 22d ago
Release cadence: monthly Present
25d median over recent releases Release history
Latest release: 1mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: today
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 1mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 1mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 1mo ago
3.9/10 Security Score
5.3/10 Scorecard
Dependency Exposure 74 transitive dependency CVEs found in the latest SBOM. 5 critical.

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.12 / 4.0

Score 5.3/10

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

No KEV exposure

supply chain risk

-1.50 / 10.0

Risk 52.2/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

4.8

10%

supply chain risk: 52.21 transitive cves: 5c/16h

Provenance trust

provenance trust

5.3

40%

scorecard score: 5.3 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 0d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none
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 52.2/100
5 Transitive critical CVEs
0 KEV-transitive CVEs
90% Dependency freshness

Scorecard

Scorecard 5.3/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check Score Reason
Binary-Artifacts 10 no binaries found in the repo
Branch-Protection -1 internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
CI-Tests 10 29 out of 29 merged PRs checked by a CI test -- score normalized to 10
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Code-Review 9 Found 28/29 approved changesets -- score normalized to 9
Contributors 10 project has 9 contributing companies or organizations
Dangerous-Workflow 10 no dangerous workflow patterns detected
Dependency-Update-Tool 10 update tool detected
Fuzzing 0 project is not fuzzed
License 9 license file detected
Maintained 10 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Packaging 10 packaging workflow detected
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0
SAST 0 SAST tool is not run on all commits -- score normalized to 0
Security-Policy 0 security policy file not detected
Signed-Releases 0 Project has not signed or included provenance with any releases.
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
Vulnerabilities 0 14 existing vulnerabilities detected

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

271 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

5

High

16

Medium

35

Low

13

Unknown

5

Still affecting latest (7) All (74)
Critical 5 High 16 Medium 35 Low 13 Unknown 5
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2017-18342 critical — pyyaml — —
CVE-2019-20477 critical — pyyaml — —
CVE-2019-6446 critical — numpy — —
CVE-2020-14343 critical — pyyaml — —
CVE-2020-1747 critical — pyyaml — —
CVE-2014-1858 high — numpy — —
CVE-2014-1859 high — numpy — —
CVE-2017-12852 high — numpy — —
CVE-2018-18074 high — requests — —
CVE-2019-18874 high — psutil — —
CVE-2020-29651 high — py — —
CVE-2021-23727 high — celery — —
CVE-2021-41495 high — numpy — —
CVE-2023-28859 high — redis — —
CVE-2024-23334 high — aiohttp — —
CVE-2024-30251 high — aiohttp — —
CVE-2025-66418 high — urllib3 2.5.0 —
CVE-2025-66471 high — urllib3 2.5.0 —
CVE-2025-69223 high — aiohttp — —
CVE-2026-21441 high — urllib3 2.5.0 —
CVE-2026-34444 high — lupa 2.4 —
CVE-2011-4356 medium — celery — —
CVE-2014-1829 medium — requests — —
CVE-2014-1830 medium — requests — —
CVE-2015-2296 medium — requests — —
CVE-2021-33430 medium — numpy — —
CVE-2021-34141 medium — numpy — —
CVE-2021-41496 medium — numpy — —
CVE-2022-30187 medium — azure-storage-blob — —
CVE-2023-28858 medium — redis — —
CVE-2023-32681 medium — requests — —
CVE-2023-37276 medium — aiohttp — —
CVE-2023-47627 medium — aiohttp — —
CVE-2023-49081 medium — aiohttp — —
CVE-2023-49082 medium — aiohttp — —
CVE-2024-23829 medium — aiohttp — —
CVE-2024-27306 medium — aiohttp — —
CVE-2024-35195 medium — requests — —
CVE-2024-42367 medium — aiohttp — —
CVE-2024-47081 medium — requests — —
CVE-2024-52303 medium — aiohttp — —
CVE-2024-52304 medium — aiohttp — —
CVE-2025-47914 medium — golang.org/x/crypto v0.42.0 —
CVE-2025-58181 medium — golang.org/x/crypto v0.42.0 —
CVE-2025-69227 medium — aiohttp — —
CVE-2025-69228 medium — aiohttp — —
CVE-2025-69229 medium — aiohttp — —
CVE-2025-71176 medium — pytest — —
CVE-2026-22815 medium — aiohttp — —
CVE-2026-25645 medium — requests — —
CVE-2026-34450 medium — anthropic — —
CVE-2026-34452 medium — anthropic — —
CVE-2026-34515 medium — aiohttp — —
CVE-2026-34516 medium — aiohttp — —
CVE-2026-34525 medium — aiohttp — —
GHSA-pjjw-qhg8-p2p9 medium — aiohttp — —
CVE-2021-21330 low — aiohttp — —
CVE-2023-47641 low — aiohttp — —
CVE-2025-53643 low — aiohttp — —
CVE-2025-69224 low — aiohttp — —
CVE-2025-69225 low — aiohttp — —
CVE-2025-69226 low — aiohttp — —
CVE-2025-69230 low — aiohttp — —
CVE-2026-34513 low — aiohttp — —
CVE-2026-34514 low — aiohttp — —
CVE-2026-34517 low — aiohttp — —
CVE-2026-34518 low — aiohttp — —
CVE-2026-34519 low — aiohttp — —
CVE-2026-34520 low — aiohttp — —
CVE-2022-42969 unknown — py — —
CVE-2025-47911 unknown — golang.org/x/net v0.44.0 —
CVE-2025-47913 unknown — golang.org/x/crypto v0.42.0 —
CVE-2025-58190 unknown — golang.org/x/net v0.44.0 —
CVE-2026-33814 unknown — golang.org/x/net v0.44.0 —

Showing 74 of 74

Beta — feedback welcome: [email protected]