Tools / SparkyBudget / Security

Security Deep Dive

SparkyBudget

Security posture and CVE patch evidence from tracked releases.

Back to Tool

3 high-severity dependency CVEs affects v.21.

Review the dependency vulnerabilities below.

✗ Signed ✗ SLSA ✓ SBOM ✗ Security policy Quarterly cadence · 56d median Sporadic maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present

Signed releases Absent

Latest release artifact signature None

Last verified: 25d ago

SLSA provenance Absent

Attestation predicate level Latest release

Last verified: 25d ago

SBOM published Present

GitHub SBOM API Latest release

Last verified: 28d ago

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 18d ago

Release cadence: quarterly Present

56d median over recent releases Release history

Latest release: 2mo ago

Maintainer sporadic Present

Recent commit activity Repository

Last commit: 2mo ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 2mo ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 2mo ago

Signing assets Not active yet

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

Latest release: 2mo ago

6.2/10 Security Score

Dependency Exposure 9 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

0.83 / 1.0

87d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

1.75 / 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

-0.66 / 10.0

Risk 6.6/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

7.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

9.3

10%

supply chain risk: 6.62 transitive cves: 0c/3h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

8.3

10%

activity freshness: 87d

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

69% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

20 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 (9)

High 3 Medium 4 Low 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2018-1000164	high	—	gunicorn	—	—
CVE-2024-1135	high	—	gunicorn	21.2.0	—
CVE-2024-6827	high	—	gunicorn	21.2.0	—
CVE-2024-35195	medium	—	requests	2.31.0	—
CVE-2024-47081	medium	—	requests	2.31.0	—
CVE-2026-25645	medium	—	requests	2.31.0	—
CVE-2026-28684	medium	—	python-dotenv	1.1.0	—
CVE-2025-47278	low	—	flask	3.1.0	—
CVE-2026-27205	low	—	flask	3.0.2	—

Showing 9 of 9