Skip to content
Tools / survey-library / Security

Security Deep Dive

survey-library

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 high-severity dependency CVEs affects v3.0.0-beta.7.

Review the dependency vulnerabilities below.

Versions by Severity

CVEs are attributed to tracked releases published before the patch release.

14 versions tracked
Version Published C H M L KEV Notes
v3.0.0-beta.7 2026-06-03
Latest
v3.0.0 2026-06-03
v2.5.27 2026-06-02
v2.5.26 2026-05-28
v3.0.0-beta.6 2026-05-26
v3.0.0-beta.5 2026-05-21
v3.0.0-beta.4 2026-05-20
v2.5.25 2026-05-19
Patches CVE-2025-31125
v2.5.10 2026-02-12 1 KEV 1
v2.5.9 2026-02-04 1 KEV 1
v2.5.8 2026-01-27 1 KEV 1
v2.5.7 2026-01-22 1 KEV 1
v2.5.6 2026-01-15 1 KEV 1
v2.5.5 2026-01-07 1 KEV 1
— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 4d 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: 18d ago
Release cadence: weekly Present
4d median over recent releases Release history
Latest release: today
Maintainer active Present
Recent commit activity Repository
Last commit: today
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: today
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: today
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: today
1.1/10 Security Score
5.2/10 Scorecard
Dependency Exposure 2 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.00 / 0.5

Max EPSS 0.832

freshness

1.00 / 1.0

Up to date

scorecard

2.08 / 4.0

Score 5.2/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

KEV exposure detected

supply chain risk

-1.50 / 10.0

Risk 33.1/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

2.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

6.7

10%

supply chain risk: 33.08 transitive cves: 0c/9h

Provenance trust

provenance trust

5.2

40%

scorecard score: 5.2 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 0d

Operational risk

operational risk

0.0

10%

kev exposure: detected epss max: 0.832
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 33.1/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
96% Dependency freshness

Scorecard

Scorecard 5.2/10

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

Check Score Reason
Code-Review 8 Found 13/16 approved changesets -- score normalized to 8
Maintained 10 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Packaging -1 packaging workflow not detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
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
License 10 license file detected
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0
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
Security-Policy 0 security policy file not detected
Signed-Releases 0 Project has not signed or included provenance with any releases.
SAST 9 SAST tool detected but not run on all commits
Fuzzing 0 project is not fuzzed

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

CVE Patch History

Tracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.

CVEs Patched by Year

Critical High Medium Low
2026
1
CVE Severity EPSS Disclosed Fixed in Days to fix vs Ecosystem Median KEV
CVE-2025-31125 MEDIUM 99%ile v2.5.25 KEV

KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.

Dependency Vulnerabilities

189 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

2

Medium

0

Low

0

Unknown

0

High 2
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2023-43646 high get-func-name 2.0.0 v2.5.25
CVE-2025-59288 high playwright 1.52.0 v2.5.25

Showing 2 of 23

Beta — feedback welcome: [email protected]