Skip to content
Tools / dockman / Security

Security Deep Dive

dockman

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 critical dependency CVEs affects v3.2.0.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA ✓ SBOM ✓ Security policy Monthly cadence · 20d median Sporadic maintainer

Trust Signals — 4 of 9 Present

Evidence already collected from releases and repository metadata.

4/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 Present
GitHub repository metadata Repository policy
Checked: 18d ago
Release cadence: monthly Present
20d median over recent releases Release history
Latest release: 3mo ago
Maintainer sporadic Present
Recent commit activity Repository
Last commit: 2mo ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 3mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 3mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 3mo ago
4.1/10 Security Score
Dependency Exposure 97 transitive dependency CVEs found in the latest SBOM. 2 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

0.84 / 1.0

82d 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 86.9/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

2.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

1.3

10%

supply chain risk: 86.92 transitive cves: 2c/39h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

8.4

10%

activity freshness: 82d

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 86.9/100
2 Transitive critical CVEs
0 KEV-transitive CVEs
54% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

2122 dependencies scanned View full dependency list →

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

Critical

2

High

39

Medium

42

Low

10

Unknown

4

Still affecting latest (97) All (97)
Critical 2 High 39 Medium 42 Low 10 Unknown 4
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2026-33186 critical — google.golang.org/grpc v1.79.1 —
CVE-2026-33816 critical — github.com/jackc/pgx/v5 v5.8.0 —
CVE-2026-26996 high — minimatch 3.1.2 —
CVE-2026-27606 high — rollup 4.57.1 —
CVE-2026-27903 high — minimatch 9.0.6 —
CVE-2026-27904 high — minimatch 9.0.6 —
CVE-2026-29074 high — svgo 3.3.2 —
CVE-2026-29181 high — go.opentelemetry.io/otel v1.40.0 —
CVE-2026-29786 high — tar 7.5.9 —
CVE-2026-31802 high — tar 7.5.9 —
CVE-2026-32141 high — flatted 3.3.3 —
CVE-2026-33228 high — flatted 3.3.3 —
CVE-2026-33671 high — picomatch 4.0.3 —
CVE-2026-33891 high — node-forge 1.3.3 —
CVE-2026-33894 high — node-forge 1.3.3 —
CVE-2026-33895 high — node-forge 1.3.3 —
CVE-2026-33896 high — node-forge 1.3.3 —
CVE-2026-34040 high — github.com/docker/docker v28.5.2+incompatible —
CVE-2026-34601 high — @xmldom/xmldom 0.8.11 —
CVE-2026-34769 high — electron 39.5.1 —
CVE-2026-34770 high — electron 39.5.1 —
CVE-2026-34771 high — electron 39.5.1 —
CVE-2026-34774 high — electron 39.5.1 —
CVE-2026-34780 high — electron 39.5.1 —
CVE-2026-34986 high — github.com/go-jose/go-jose/v4 v4.1.3 —
CVE-2026-39363 high — vite 7.1.11 —
CVE-2026-39364 high — vite 7.1.11 —
CVE-2026-39883 high — go.opentelemetry.io/otel/sdk v1.40.0 —
CVE-2026-41672 high — @xmldom/xmldom 0.8.11 —
CVE-2026-41673 high — @xmldom/xmldom 0.8.11 —
CVE-2026-41674 high — @xmldom/xmldom 0.8.11 —
CVE-2026-41675 high — @xmldom/xmldom 0.8.11 —
CVE-2026-42033 high — axios 1.13.5 —
CVE-2026-42035 high — axios 1.13.5 —
CVE-2026-42043 high — axios 1.13.5 —
CVE-2026-42264 high — axios 1.13.5 —
CVE-2026-4800 high — lodash 4.17.23 —
CVE-2026-4867 high — path-to-regexp 0.1.12 —
CVE-2026-6321 high — fast-uri 3.1.0 —
CVE-2026-6322 high — fast-uri 3.1.0 —
GHSA-5c6j-r48x-rmvq high — serialize-javascript 6.0.2 —
CVE-2025-13465 medium — lodash 4.17.21 —
CVE-2025-62718 medium — axios 1.13.5 —
CVE-2025-69873 medium — ajv 8.17.1 —
CVE-2026-0540 medium — dompurify 3.2.7 —
CVE-2026-2950 medium — lodash 4.17.23 —
CVE-2026-33532 medium — yaml 1.10.2 —
CVE-2026-33672 medium — picomatch 4.0.3 —
CVE-2026-33750 medium — brace-expansion 5.0.3 —
CVE-2026-33809 medium — golang.org/x/image v0.20.0 —
CVE-2026-33997 medium — github.com/docker/docker v28.5.2+incompatible —
CVE-2026-34043 medium — serialize-javascript 6.0.2 —
CVE-2026-34165 medium — github.com/go-git/go-git/v5 v5.17.0 —
CVE-2026-34765 medium — electron 39.5.1 —
CVE-2026-34767 medium — electron 39.5.1 —
CVE-2026-34772 medium — electron 39.5.1 —
CVE-2026-34773 medium — electron 39.5.1 —
CVE-2026-34775 medium — electron 39.5.1 —
CVE-2026-34776 medium — electron 39.5.1 —
CVE-2026-34777 medium — electron 39.5.1 —
CVE-2026-34778 medium — electron 39.5.1 —
CVE-2026-34779 medium — electron 39.5.1 —
CVE-2026-39365 medium — vite 7.1.11 —
CVE-2026-40175 medium — axios 1.13.5 —
CVE-2026-41238 medium — dompurify 3.2.7 —
CVE-2026-41239 medium — dompurify 3.2.7 —
CVE-2026-41240 medium — dompurify 3.2.7 —
CVE-2026-41305 medium — postcss 8.5.6 —
CVE-2026-41506 medium — github.com/go-git/go-git/v5 v5.17.0 —
CVE-2026-42034 medium — axios 1.13.5 —
CVE-2026-42036 medium — axios 1.13.5 —
CVE-2026-42037 medium — axios 1.13.5 —
CVE-2026-42038 medium — axios 1.13.5 —
CVE-2026-42039 medium — axios 1.13.5 —
CVE-2026-42041 medium — axios 1.13.5 —
CVE-2026-42042 medium — axios 1.13.5 —
CVE-2026-42044 medium — axios 1.13.5 —
CVE-2026-42338 medium — ip-address 10.1.0 —
GHSA-39q2-94rc-95cp medium — dompurify 3.2.7 —
GHSA-cj63-jhhr-wcxv medium — dompurify 3.2.7 —
GHSA-cjmm-f4jc-qw8r medium — dompurify 3.2.7 —
GHSA-h8r8-wccr-v5f2 medium — dompurify 3.2.7 —
GHSA-r4q5-vmmm-2653 medium — follow-redirects 1.15.11 —
CVE-2025-68157 low — webpack 5.101.3 —
CVE-2025-68458 low — webpack 5.101.3 —
CVE-2026-2391 low — qs 6.14.1 —
CVE-2026-33762 low — github.com/go-git/go-git/v5 v5.17.0 —
CVE-2026-34764 low — electron 39.5.1 —
CVE-2026-34766 low — electron 39.5.1 —
CVE-2026-34768 low — electron 39.5.1 —
CVE-2026-34781 low — electron 39.5.1 —
CVE-2026-41889 low — github.com/jackc/pgx/v5 v5.8.0 —
CVE-2026-42040 low — axios 1.13.5 —
CVE-2026-33812 unknown — golang.org/x/image v0.20.0 —
CVE-2026-33813 unknown — golang.org/x/image v0.20.0 —
CVE-2026-33814 unknown — golang.org/x/net v0.52.0 —
CVE-2026-33815 unknown — github.com/jackc/pgx/v5 v5.8.0 —

Showing 97 of 97

Beta — feedback welcome: [email protected]