Tools / babybuddy / Security

Security Deep Dive

babybuddy

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 critical dependency CVEs affects v2.9.2.

Audit transitive dependencies; consider upgrading or pinning replacements.

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

Release cadence: weekly Present

8d median over recent releases Release history

Latest release: 9d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 9d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 9d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 9d ago

Signing assets Not active yet

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

Latest release: 9d ago

4.5/10 Security Score

5.7/10 Scorecard

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

1.00 / 1.0

9d stale

scorecard

2.28 / 4.0

Score 5.7/10

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

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

2.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

6.1

10%

supply chain risk: 38.67 transitive cves: 2c/15h

Provenance trust

provenance trust

5.7

40%

scorecard score: 5.7 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 9d

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

2 Transitive critical CVEs

0 KEV-transitive CVEs

67% Dependency freshness

Scorecard

Scorecard 5.7/10

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

Check	Score	Reason
Dangerous-Workflow	10	no dangerous workflow patterns detected
Packaging	-1	packaging workflow not detected
Code-Review	3	Found 9/23 approved changesets -- score normalized to 3
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Maintained	10	27 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Security-Policy	10	security policy file detected
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts	10	no binaries found in the repo
Pinned-Dependencies	1	dependency not pinned by hash detected -- score normalized to 1
Fuzzing	0	project is not fuzzed
License	10	license file detected
Branch-Protection	5	branch protection is not maximal on development and all release branches
Signed-Releases	-1	no releases found
SAST	4	SAST tool is not run on all commits -- score normalized to 4

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

838 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 (0) All (35)

Critical 2 High 15 Medium 17 Low 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2024-42005	critical	—	django	5.0	v2.9.0
CVE-2025-64459	critical	—	django	5.0	v2.9.0
CVE-2021-23337	high	—	lodash.template	3.6.2	v2.9.0
CVE-2022-25858	high	—	terser	3.17.0	v2.9.0
CVE-2024-24680	high	—	django	5.0	v2.9.0
CVE-2024-38875	high	—	django	5.0	v2.9.0
CVE-2024-39330	high	—	django	5.0	v2.9.0
CVE-2024-39614	high	—	django	5.0	v2.9.0
CVE-2024-53908	high	—	django	5.0	v2.9.0
CVE-2025-57833	high	—	django	5.0	v2.9.0
CVE-2025-64458	high	—	django	5.0	v2.9.0
CVE-2026-25990	high	—	pillow	11.3.0	v2.9.0
CVE-2026-32274	high	—	black	26.0	v2.9.0
CVE-2026-40192	high	—	pillow	11.3.0	v2.9.0
CVE-2026-42311	high	—	pillow	11.3.0	v2.9.0
CVE-2026-6321	high	—	fast-uri	3.1.0	v2.9.0
CVE-2026-6322	high	—	fast-uri	3.1.0	v2.9.0
CVE-2020-25626	medium	—	djangorestframework	3.0	v2.9.0
CVE-2024-27351	medium	—	django	5.0	v2.9.0
CVE-2024-39329	medium	—	django	5.0	v2.9.0
CVE-2024-41989	medium	—	django	5.0	v2.9.0
CVE-2024-41990	medium	—	django	5.0	v2.9.0
CVE-2024-41991	medium	—	django	5.0	v2.9.0
CVE-2024-45230	medium	—	django	5.0	v2.9.0
CVE-2024-45231	medium	—	django	5.0	v2.9.0
CVE-2024-53907	medium	—	django	5.0	v2.9.0
CVE-2024-56374	medium	—	django	5.0	v2.9.0
CVE-2025-26699	medium	—	django	5.0	v2.9.0
CVE-2025-27556	medium	—	django	5.0	v2.9.0
CVE-2025-48432	medium	—	django	5.0	v2.9.0
CVE-2026-28684	medium	—	python-dotenv	1.0	v2.9.0
CVE-2026-42308	medium	—	pillow	11.3.0	v2.9.0
CVE-2026-42309	medium	—	pillow	11.3.0	v2.9.0
CVE-2026-42310	medium	—	pillow	11.3.0	v2.9.0
CVE-2024-21520	low	—	djangorestframework	3.0	v2.9.0

Showing 35 of 35