Tools / deck / Security

Security Deep Dive

deck

Security posture and CVE patch evidence from tracked releases.

Back to Tool

8 high-severity dependency CVEs affects v1.13.10.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 0d 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: 22d ago

Release cadence: weekly Present

0d median over recent releases Release history

Latest release: 13d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 13d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 13d ago

Signing assets Not active yet

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

Latest release: 13d ago

4.5/10 Security Score

6.3/10 Scorecard

Dependency Exposure 19 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.52 / 4.0

Score 6.3/10

cve health

0.25 / 2.5

⚠ No direct scan — 0c/8h 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 16.9/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

1.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

8.3

10%

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

Provenance trust

provenance trust

6.3

40%

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

57% Dependency freshness

Scorecard

Scorecard 6.3/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 8 issue activity found in the last 90 days -- score normalized to 10
Code-Review	5	Found 6/12 approved changesets -- score normalized to 5
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Packaging	-1	packaging workflow not detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
Binary-Artifacts	10	no binaries found in the repo
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
License	10	license file detected
Signed-Releases	-1	no releases found
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
Pinned-Dependencies	9	dependency not pinned by hash detected -- score normalized to 9
Fuzzing	0	project is not fuzzed
SAST	0	SAST tool is not run on all commits -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1766 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 (2) All (19)

High 8 Medium 8 Low 3

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2022-21680	high	—	marked	2.1.3	v1.16.5
CVE-2022-21681	high	—	marked	2.1.3	v1.16.5
CVE-2026-44665	high	—	fast-xml-builder	1.1.4	v1.16.5
CVE-2026-44728	high	—	@babel/plugin-transform-modules-systemjs	7.29.0	v1.16.5
CVE-2026-4800	high	—	lodash	4.17.21	v1.16.5
CVE-2026-4867	high	—	path-to-regexp	0.1.12	v1.16.5
CVE-2026-6321	high	—	fast-uri	3.1.0	v1.16.5
CVE-2026-6322	high	—	fast-uri	3.1.0	v1.16.5
CVE-2023-44270	medium	—	postcss	7.0.39	v1.16.5
CVE-2024-6783	medium	—	vue-template-compiler	2.7.16	v1.16.5
CVE-2025-13465	medium	—	lodash	4.17.21	v1.16.5
CVE-2025-15284	medium	—	qs	6.14.0	v1.16.5
CVE-2026-2739	medium	—	bn.js	4.12.0	v1.16.5
CVE-2026-2950	medium	—	lodash	4.17.21	v1.16.5
CVE-2026-41305	medium	—	postcss	8.5.8	v1.16.5
CVE-2026-41650	medium	—	fast-xml-parser	5.5.11	v1.16.5
CVE-2024-9506	low	—	vue	2.7.16	v1.16.5
CVE-2025-14505	low	—	elliptic	6.6.1	v1.16.5
CVE-2026-2391	low	—	qs	6.14.1	v1.16.5

Showing 19 of 19