Tools / dozzle / Security

Security Deep Dive

dozzle

Security posture and CVE patch evidence from tracked releases.

Back to Tool

8 high-severity dependency CVEs affects v10.6.4.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 4d 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 Unknown

GitHub SBOM API Latest release

—

SECURITY.md Present

GitHub repository metadata Repository policy

Checked: 23d ago

Release cadence: weekly Present

4d median over recent releases Release history

Latest release: 1d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 2d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 1d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 1d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 1d ago

5.7/10 Security Score

6.0/10 Scorecard

Dependency Exposure 21 transitive dependency CVEs found in the latest SBOM.

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

Score 6.0/10

cve health

1.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 16.9/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

6.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

8.3

10%

supply chain risk: 16.88 transitive cves: 0c/8h

Provenance trust

provenance trust

6.0

40%

scorecard score: 6.0 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 16.9/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

56% Dependency freshness

Scorecard

Scorecard 6.0/10

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

Check	Score	Reason
Security-Policy	10	security policy file detected
Maintained	10	30 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow	10	no dangerous workflow patterns detected
Code-Review	0	Found 1/29 approved changesets -- score normalized to 0
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts	10	no binaries found in the repo
Fuzzing	0	project is not fuzzed
License	10	license file detected
Signed-Releases	-1	no releases found
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0
Branch-Protection	-1	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Packaging	10	packaging workflow detected
SAST	9	SAST tool is not run on all commits -- score normalized to 9

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1071 dependencies scanned View full dependency list →

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

Critical

High

Medium

Low

Unknown

Still affecting latest (19) All (21)

High 8 Medium 8 Low 4 Unknown 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2025-64756	high	—	glob	10.4.5	v10.5.3
CVE-2026-22028	high	—	preact	10.26.5	v10.5.3
CVE-2026-26996	high	—	minimatch	9.0.1	v10.5.3
CVE-2026-27606	high	—	rollup	4.53.3	v10.5.3
CVE-2026-27903	high	—	minimatch	9.0.1	v10.5.3
CVE-2026-27904	high	—	minimatch	9.0.1	v10.5.3
CVE-2026-33671	high	—	picomatch	4.0.3	v10.5.3
CVE-2026-35209	high	—	defu	6.1.4	v10.5.3
CVE-2025-66400	medium	—	mdast-util-to-hast	13.2.0	v10.5.3
CVE-2026-33532	medium	—	yaml	2.8.2	v10.5.3
CVE-2026-33672	medium	—	picomatch	4.0.3	v10.5.3
CVE-2026-33750	medium	—	brace-expansion	5.0.3	v10.5.3
CVE-2026-35166	medium	—	github.com/gohugoio/hugo	v0.149.1	v10.5.3
CVE-2026-39365	medium	—	vite	5.4.21	v10.5.3
CVE-2026-44301	medium	—	github.com/gohugoio/hugo	v0.149.1	v10.5.3
GHSA-67mh-4wv8-2f99	medium	—	esbuild	0.23.1	v10.5.3
CVE-2025-5889	low	—	brace-expansion	2.0.1	v10.5.3
CVE-2026-2391	low	—	qs	6.14.1	v10.5.3
CVE-2026-24001	low	—	diff	4.0.2	v10.5.3
GHSA-xffm-g5w8-qvg7	low	—	@eslint/plugin-kit	0.2.8	v10.5.3
CVE-2026-33814	unknown	—	golang.org/x/net	v0.52.0	v10.5.3

Showing 21 of 21