Security Deep Dive
babybuddy
Security posture and CVE patch evidence from tracked releases.
2 critical dependency CVEs affects v2.9.2.
Audit transitive dependencies; consider upgrading or pinning replacements.
Trust Signals — 3 of 9 Present
Evidence already collected from releases and repository metadata.
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.96 / 1.0
42d stale
scorecard
2.20 / 4.0
Score 5.5/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 v2Vulnerability posture
vulnerability posture
2.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
6.1
10%
Provenance trust
provenance trust
5.5
40%
Maintainer health
maintainer health
9.6
10%
Operational risk
operational risk
8.5
10%
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/100Scorecard
Scorecard 5.5/10OpenSSF 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 |
| Code-Review | 4 | Found 10/23 approved changesets -- score normalized to 4 |
| Security-Policy | 10 | security policy file detected |
| Packaging | -1 | packaging workflow not detected |
| Maintained | 10 | 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10 |
| 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 |
| Pinned-Dependencies | 1 | dependency not pinned by hash detected -- score normalized to 1 |
| License | 10 | license file detected |
| Fuzzing | 0 | project is not fuzzed |
| Signed-Releases | -1 | no releases found |
| Branch-Protection | 5 | branch protection is not maximal on development and all release branches |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
OpenSSF Badge
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
2
High
15
Medium
17
Low
1
Unknown
0
| 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