Tools / kubetail / Security

Security Deep Dive

kubetail

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 high-severity dependency CVEs affects cli/v0.17.0.

Review the dependency vulnerabilities below.

— Signed — SLSA ✓ SBOM ✓ Security policy Weekly cadence · 8d median Active maintainer

Trust Signals — 4 of 9 Present

Evidence already collected from releases and repository metadata.

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

GitHub repository metadata Repository policy

Checked: 22d ago

Release cadence: weekly Present

8d median over recent releases Release history

Latest release: 29d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 9d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 29d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 29d ago

Signing assets Not active yet

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

Latest release: 29d ago

5.5/10 Security Score

Dependency Exposure 12 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

9d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

0.75 / 2.5

⚠ No direct scan — 0c/2h transitive 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.45 / 10.0

Risk 4.5/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

3.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

9.5

10%

supply chain risk: 4.52 transitive cves: 0c/2h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 9d

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

74% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1965 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 (12) All (12)

High 2 Medium 1 Low 3 Unknown 6

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-35469	high	—	github.com/moby/spdystream	v0.5.0	—
GHSA-82j2-j2ch-gfr8	high	—	rustls-webpki	0.103.10	—
CVE-2026-41305	medium	—	postcss	8.5.9	—
GHSA-965h-392x-2mh5	low	—	rustls-webpki	0.103.10	—
GHSA-cq8v-f236-94qc	low	—	rand	0.9.2	—
GHSA-xgp8-3hg3-c2mh	low	—	rustls-webpki	0.103.10	—
CVE-2026-33814	unknown	—	golang.org/x/net	v0.52.0	—
RUSTSEC-2025-0134	unknown	—	rustls-pemfile	2.2.0	—
RUSTSEC-2026-0097	unknown	—	rand	0.9.2	—
RUSTSEC-2026-0098	unknown	—	rustls-webpki	0.103.10	—
RUSTSEC-2026-0099	unknown	—	rustls-webpki	0.103.10	—
RUSTSEC-2026-0104	unknown	—	rustls-webpki	0.103.10	—

Showing 12 of 12