Tools / server / Security

Security Deep Dive

server

Security posture and CVE patch evidence from tracked releases.

Back to Tool

5 high-severity dependency CVEs affects v3.0.0.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✓ Security policy Monthly cadence · 42d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/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 Present

GitHub repository metadata Repository policy

Checked: 9d ago

Release cadence: monthly Present

42d median over recent releases Release history

Latest release: 8d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 8d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 8d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 8d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 8d ago

4.0/10 Security Score

5.5/10 Scorecard

Pending CVE Patch Speed

Open CVEs Open CVEs detected for latest version.

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.20 / 4.0

Score 5.5/10

cve health

0.00 / 2.5

Open CVEs detected

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

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: open cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

5.1

10%

supply chain risk: 48.79 transitive cves: 2c/20h

Provenance trust

provenance trust

5.5

40%

scorecard score: 5.5 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 48.8/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

60% 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
Maintained	10	30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Code-Review	10	all changesets reviewed
Packaging	-1	packaging workflow not detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Security-Policy	10	security policy file detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts	10	no binaries found in the repo
License	9	license file detected
Fuzzing	0	project is not fuzzed
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0
Signed-Releases	0	Project has not signed or included provenance with any releases.
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
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

695 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 (21) All (47)

High 5 Medium 13 Low 2 Unknown 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-29181	high	—	go.opentelemetry.io/otel	v1.40.0	v3.0.0
CVE-2026-42033	high	—	axios	1.13.6	v3.0.0
CVE-2026-42035	high	—	axios	1.13.6	v3.0.0
CVE-2026-42043	high	—	axios	1.13.6	v3.0.0
CVE-2026-42264	high	—	axios	1.13.6	v3.0.0
CVE-2025-62718	medium	—	axios	1.13.6	v3.0.0
CVE-2026-33532	medium	—	yaml	1.10.2	v3.0.0
CVE-2026-33750	medium	—	brace-expansion	2.0.2	v3.0.0
CVE-2026-40175	medium	—	axios	1.13.6	v3.0.0
CVE-2026-42034	medium	—	axios	1.13.6	v3.0.0
CVE-2026-42036	medium	—	axios	1.13.6	v3.0.0
CVE-2026-42037	medium	—	axios	1.13.6	v3.0.0
CVE-2026-42038	medium	—	axios	1.13.6	v3.0.0
CVE-2026-42039	medium	—	axios	1.13.6	v3.0.0
CVE-2026-42041	medium	—	axios	1.13.6	v3.0.0
CVE-2026-42042	medium	—	axios	1.13.6	v3.0.0
CVE-2026-42044	medium	—	axios	1.13.6	v3.0.0
GHSA-r4q5-vmmm-2653	medium	—	follow-redirects	1.15.11	v3.0.0
CVE-2026-26958	low	—	filippo.io/edwards25519	v1.1.0	v3.0.0
CVE-2026-42040	low	—	axios	1.13.6	v3.0.0
CVE-2026-33814	unknown	—	golang.org/x/net	v0.51.0	v3.0.0

Showing 21 of 47