Tools / Performance Co-Pilot / Security

Security Deep Dive

Performance Co-Pilot

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects 7.1.5.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✗ Security policy Monthly cadence · 19d median 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 Unknown

GitHub SBOM API Latest release

—

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 22d ago

Release cadence: monthly Present

19d median over recent releases Release history

Latest release: 9d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 3d 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

5.0/10 Security Score

5.5/10 Scorecard

Dependency Exposure 24 transitive dependency CVEs found in the latest SBOM. 1 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

3d stale

scorecard

2.20 / 4.0

Score 5.5/10

cve health

1.00 / 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 20.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

4.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

8.0

10%

supply chain risk: 20.0 transitive cves: 1c/8h

Provenance trust

provenance trust

5.5

40%

scorecard score: 5.5 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 3d

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

1 Transitive critical CVEs

0 KEV-transitive CVEs

100% Dependency freshness

Scorecard

Scorecard 5.5/10

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

Check	Score	Reason
Code-Review	0	Found 0/26 approved changesets -- score normalized to 0
Maintained	10	30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow	10	no dangerous workflow patterns detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
CII-Best-Practices	5	badge detected: Passing
Security-Policy	0	security policy file not detected
License	9	license file detected
Signed-Releases	0	Project has not signed or included provenance with any releases.
Fuzzing	10	project is fuzzed
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
Binary-Artifacts	9	binaries present in source code
Packaging	10	packaging workflow detected
SAST	10	SAST tool is run on all commits
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0

Dependency Vulnerabilities

24 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 (24)

Critical 1 High 8 Medium 14 Unknown 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2023-47248	critical	—	pyarrow	—	7.1.4
CVE-2013-1633	high	—	setuptools	—	7.1.4
CVE-2018-18074	high	—	requests	—	7.1.4
CVE-2019-12408	high	—	pyarrow	—	7.1.4
CVE-2019-12410	high	—	pyarrow	—	7.1.4
CVE-2022-40897	high	—	setuptools	—	7.1.4
CVE-2024-6345	high	—	setuptools	—	7.1.4
CVE-2025-47273	high	—	setuptools	—	7.1.4
CVE-2026-41066	high	—	lxml	—	7.1.4
CVE-2014-1829	medium	—	requests	—	7.1.4
CVE-2014-1830	medium	—	requests	—	7.1.4
CVE-2014-3146	medium	—	lxml	—	7.1.4
CVE-2015-2296	medium	—	requests	—	7.1.4
CVE-2017-5992	medium	—	openpyxl	—	7.1.4
CVE-2018-19787	medium	—	lxml	—	7.1.4
CVE-2020-27783	medium	—	lxml	—	7.1.4
CVE-2021-28957	medium	—	lxml	—	7.1.4
CVE-2021-43818	medium	—	lxml	—	7.1.4
CVE-2022-2309	medium	—	lxml	—	7.1.4
CVE-2023-32681	medium	—	requests	—	7.1.4
CVE-2024-35195	medium	—	requests	—	7.1.4
CVE-2024-47081	medium	—	requests	—	7.1.4
CVE-2026-25645	medium	—	requests	—	7.1.4
CVE-2024-52338	unknown	—	pyarrow	—	7.1.4

Showing 24 of 24