Skip to content
Tools / notes / Security

Security Deep Dive

notes

Security posture and CVE patch evidence from tracked releases.

Back to Tool

7 high-severity dependency CVEs affects v6.0.0.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✗ Security policy Monthly cadence · 37d 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: 23d ago
Release cadence: monthly Present
37d median over recent releases Release history
Latest release: 1d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 1d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 1d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 1d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 1d ago
5.6/10 Security Score
5.8/10 Scorecard
Dependency Exposure 19 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

1d stale

scorecard

2.32 / 4.0

Score 5.8/10

cve health

1.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 16.6/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

6.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

8.3

10%

supply chain risk: 16.65 transitive cves: 0c/8h

Provenance trust

provenance trust

5.8

40%

scorecard score: 5.8 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

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

Scorecard

Scorecard 5.8/10

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

Check Score Reason
Code-Review 2 Found 2/8 approved changesets -- score normalized to 2
Maintained 10 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
Packaging -1 packaging workflow not detected
Binary-Artifacts 10 no binaries found in the repo
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies 8 dependency not pinned by hash detected -- score normalized to 8
Fuzzing 0 project is not fuzzed
License 10 license file detected
Signed-Releases -1 no releases found
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 10 security policy file detected
SAST 0 SAST tool is not run on all commits -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1350 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

7

Medium

10

Low

2

Unknown

0

High 7 Medium 10 Low 2
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2026-42033 high axios 1.15.0 v5.0.1
CVE-2026-42035 high axios 1.15.0 v5.0.1
CVE-2026-42043 high axios 1.15.0 v5.0.1
CVE-2026-42264 high axios 1.15.0 v5.0.1
CVE-2026-44665 high fast-xml-builder 1.1.5 v5.0.1
CVE-2026-6321 high fast-uri 3.1.0 v5.0.1
CVE-2026-6322 high fast-uri 3.1.0 v5.0.1
CVE-2026-41650 medium fast-xml-parser 4.5.6 v5.0.1
CVE-2026-42034 medium axios 1.15.0 v5.0.1
CVE-2026-42036 medium axios 1.15.0 v5.0.1
CVE-2026-42037 medium axios 1.15.0 v5.0.1
CVE-2026-42038 medium axios 1.15.0 v5.0.1
CVE-2026-42039 medium axios 1.15.0 v5.0.1
CVE-2026-42041 medium axios 1.15.0 v5.0.1
CVE-2026-42042 medium axios 1.15.0 v5.0.1
CVE-2026-42044 medium axios 1.15.0 v5.0.1
CVE-2026-44664 medium fast-xml-builder 1.1.5 v5.0.1
CVE-2024-9506 low vue 2.7.16 v5.0.1
CVE-2026-42040 low axios 1.15.0 v5.0.1

Showing 19 of 23

Beta — feedback welcome: [email protected]