Security Deep Dive
borg
Security posture and CVE patch evidence from tracked releases.
8 high-severity dependency CVEs affects 1.4.4.
Review the dependency vulnerabilities below.
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
1.00 / 1.0
4d stale
scorecard
2.36 / 4.0
Score 5.9/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.5/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
1.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
8.3
10%
Provenance trust
provenance trust
5.9
40%
Maintainer health
maintainer health
10.0
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 16.5/100Scorecard
Scorecard 5.9/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10 |
| Security-Policy | 10 | security policy file detected |
| Code-Review | 4 | Found 6/13 approved changesets -- score normalized to 4 |
| 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 |
| CII-Best-Practices | 5 | badge detected: Passing |
| Fuzzing | 0 | project is not fuzzed |
| License | 9 | license file detected |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Branch-Protection | 0 | branch protection not enabled on development/release branches |
| Signed-Releases | 8 | 5 out of the last 5 releases have a total of 5 signed artifacts. |
| SAST | 9 | SAST tool detected but not run on all commits |
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
0
High
8
Medium
9
Low
1
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2013-1629 | high | — | pip | 24.2 || > 24.2 | — |
| CVE-2013-5123 | high | — | pip | 24.2 || > 24.2 | — |
| CVE-2019-20916 | high | — | pip | 24.2 || > 24.2 | — |
| CVE-2021-3572 | high | — | pip | 24.2 || > 24.2 | — |
| CVE-2022-40898 | high | — | wheel | — | — |
| CVE-2024-53899 | high | — | virtualenv | — | — |
| CVE-2026-24049 | high | — | wheel | — | — |
| CVE-2026-32274 | high | — | black | 24.0,< 25 | — |
| CVE-2011-4617 | medium | — | virtualenv | — | — |
| CVE-2013-1888 | medium | — | pip | 24.2 || > 24.2 | — |
| CVE-2023-5752 | medium | — | pip | 24.2 || > 24.2 | — |
| CVE-2024-21503 | medium | — | black | 24.0,< 25 | — |
| CVE-2025-71176 | medium | — | pytest | — | — |
| CVE-2025-8869 | medium | — | pip | 24.2 || > 24.2 | — |
| CVE-2026-22702 | medium | — | virtualenv | — | — |
| CVE-2026-3219 | medium | — | pip | 26.0.1 | — |
| CVE-2026-6357 | medium | — | pip | 26.0.1 | — |
| CVE-2026-1703 | low | — | pip | 24.2 || > 24.2 | — |
Showing 18 of 18