Skip to content
Tools / CAPA / Security

Security Deep Dive

CAPA

Security posture and CVE patch evidence from tracked releases.

Back to Tool

3 high-severity dependency CVEs affects v9.4.0.

Review the dependency vulnerabilities below.

— Signed — SLSA ✓ SBOM ✗ Security policy Unknown cadence 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 Present
GitHub SBOM API Latest release
Last verified: 28d ago
SECURITY.md Absent
GitHub repository metadata Repository policy
Checked: 17d ago
Release cadence Unknown
12-release median Release history
Latest release: 2mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: 6d 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.6/10 Security Score
5.9/10 Scorecard
Dependency Exposure 16 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

1.00 / 1.0

6d stale

scorecard

2.36 / 4.0

Score 5.9/10

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.73 / 10.0

Risk 7.3/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

7.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

9.3

10%

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

Provenance trust

provenance trust

5.9

40%

scorecard score: 5.9 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 6d

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 7.3/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
36% Dependency freshness

Scorecard

Scorecard 5.9/10

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

Check Score Reason
Maintained 10 30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
Code-Review 2 Found 4/20 approved changesets -- score normalized to 2
Dependency-Update-Tool 10 update tool 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
License 10 license file detected
Pinned-Dependencies 5 dependency not pinned by hash detected -- score normalized to 5
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Security-Policy 0 security policy file not detected
Signed-Releases 0 Project has not signed or included provenance with any releases.
Vulnerabilities 5 5 existing vulnerabilities detected
SAST 10 SAST tool is run on all commits
Fuzzing 0 project is not fuzzed
Packaging 10 packaging workflow detected
Branch-Protection -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
CI-Tests 10 13 out of 13 merged PRs checked by a CI test -- score normalized to 10
Contributors 10 project has 18 contributing companies or organizations

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

434 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

0

High

3

Medium

12

Low

1

Unknown

0

High 3 Medium 12 Low 1
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2018-18074 high requests
CVE-2024-21538 high cross-spawn 7.0.3
CVE-2026-0994 high protobuf 5
CVE-2014-1829 medium requests
CVE-2014-1830 medium requests
CVE-2015-2296 medium requests
CVE-2023-32681 medium requests
CVE-2024-35195 medium requests
CVE-2024-3772 medium pydantic 2
CVE-2024-47081 medium requests
CVE-2025-69873 medium ajv 6.12.6
CVE-2025-71176 medium pytest 9.0.2
CVE-2026-25645 medium requests
CVE-2026-33750 medium brace-expansion 2.0.2
CVE-2026-41305 medium postcss 8.5.3
CVE-2025-5889 low brace-expansion 1.1.11

Showing 16 of 16

Beta — feedback welcome: [email protected]