Tools / SparkyFitness / Security

Security Deep Dive

SparkyFitness

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v0.16.8.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 5d median Active maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/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 Absent

GitHub repository metadata Repository policy

Checked: 23d ago

Release cadence: weekly Present

5d median over recent releases Release history

Latest release: 3d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 2d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 3d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 3d ago

Signing assets Not active yet

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

Latest release: 3d ago

3.8/10 Security Score

Dependency Exposure 9 transitive dependency CVEs found in the latest SBOM. 1 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

2d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

0.00 / 2.5

⚠ No direct scan — 2c/48h 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 100.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

0.0

10%

supply chain risk: 100.0 transitive cves: 2c/48h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 2d

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 100.0/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

61% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

3338 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 (9) All (110)

Critical 1 High 7 Medium 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2025-24981	critical	—	@nuxtjs/mdc	0.9.5	v0.16.6.2
CVE-2025-54075	high	—	@nuxtjs/mdc	0.9.5	v0.16.6.2
CVE-2026-34601	high	—	@xmldom/xmldom	0.8.11	v0.16.6.2
CVE-2026-41672	high	—	@xmldom/xmldom	0.8.11	v0.16.6.2
CVE-2026-41673	high	—	@xmldom/xmldom	0.8.11	v0.16.6.2
CVE-2026-41674	high	—	@xmldom/xmldom	0.8.11	v0.16.6.2
CVE-2026-41675	high	—	@xmldom/xmldom	0.8.11	v0.16.6.2
CVE-2026-4867	high	—	path-to-regexp	0.1.12	v0.16.6.2
CVE-2026-33732	medium	—	srvx	0.11.12	v0.16.6.2

Showing 9 of 110