Tools / kitsu / Security

Security Deep Dive

kitsu

Security posture and CVE patch evidence from tracked releases.

Back to Tool

7 high-severity dependency CVEs affects v1.0.43.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 1d 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: weekly Present

1d median over recent releases Release history

Latest release: today

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

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

4.0/10 Security Score

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

Up to date

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

0.25 / 2.5

⚠ No direct scan — 0c/7h 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

-1.47 / 10.0

Risk 14.7/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

1.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

8.5

10%

supply chain risk: 14.74 transitive cves: 0c/7h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 0d

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

63% Dependency freshness

Dependency Vulnerabilities

707 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 (8)

High 7 Low 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-23745	high	—	tar	6.2.1	v1.0.32
CVE-2026-23950	high	—	tar	6.2.1	v1.0.32
CVE-2026-24842	high	—	tar	6.2.1	v1.0.32
CVE-2026-26960	high	—	tar	6.2.1	v1.0.32
CVE-2026-27013	high	—	fabric	5.1.0	v1.0.32
CVE-2026-29786	high	—	tar	6.2.1	v1.0.32
CVE-2026-31802	high	—	tar	6.2.1	v1.0.32
CVE-2026-3449	low	—	@tootallnate/once	2.0.1	v1.0.32

Showing 8 of 8