Tools / Kometa / Security

Security Deep Dive

Kometa

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v2.4.5.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✗ Security policy Monthly cadence · 27d 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: 13d ago

Release cadence: monthly Present

27d median over recent releases Release history

Latest release: 4d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 9d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 4d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 4d ago

Signing assets Not active yet

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

Latest release: 4d ago

3.8/10 Security Score

Dependency Exposure 38 transitive dependency CVEs found in the latest SBOM. 1 critical.

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

⚠ Estimated — not yet collected

cve health

0.00 / 2.5

⚠ No direct scan — 1c/16h 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.50 / 10.0

Risk 36.3/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

6.4

10%

supply chain risk: 36.28 transitive cves: 1c/16h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated 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 36.3/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

86% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

60 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 (38)

Critical 1 High 16 Medium 19 Low 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2015-8557	critical	—	pygments	—	v2.4.2
CVE-2014-1402	high	—	jinja2	—	v2.4.2
CVE-2016-10745	high	—	jinja2	—	v2.4.2
CVE-2018-18074	high	—	requests	—	v2.4.2
CVE-2019-10906	high	—	jinja2	—	v2.4.2
CVE-2021-20270	high	—	pygments	—	v2.4.2
CVE-2021-27291	high	—	pygments	—	v2.4.2
CVE-2021-40978	high	—	mkdocs	—	v2.4.2
CVE-2021-42771	high	—	babel	—	v2.4.2
CVE-2023-32309	high	—	pymdown-extensions	—	v2.4.2
CVE-2026-40192	high	—	pillow	12.1.1	v2.4.2
CVE-2026-41066	high	—	lxml	6.0.2	v2.4.2
CVE-2026-42215	high	—	gitpython	3.1.46	v2.4.2
CVE-2026-42284	high	—	gitpython	3.1.46	v2.4.2
CVE-2026-42311	high	—	pillow	12.1.1	v2.4.2
CVE-2026-44243	high	—	gitpython	3.1.46	v2.4.2
CVE-2026-44244	high	—	gitpython	3.1.46	v2.4.2
CVE-2014-0012	medium	—	jinja2	—	v2.4.2
CVE-2014-1829	medium	—	requests	—	v2.4.2
CVE-2014-1830	medium	—	requests	—	v2.4.2
CVE-2015-2296	medium	—	requests	—	v2.4.2
CVE-2020-28493	medium	—	jinja2	—	v2.4.2
CVE-2022-40896	medium	—	pygments	—	v2.4.2
CVE-2023-32681	medium	—	requests	—	v2.4.2
CVE-2024-22195	medium	—	jinja2	—	v2.4.2
CVE-2024-34064	medium	—	jinja2	—	v2.4.2
CVE-2024-35195	medium	—	requests	—	v2.4.2
CVE-2024-47081	medium	—	requests	—	v2.4.2
CVE-2024-56201	medium	—	jinja2	—	v2.4.2
CVE-2024-56326	medium	—	jinja2	—	v2.4.2
CVE-2025-27516	medium	—	jinja2	—	v2.4.2
CVE-2025-69534	medium	—	markdown	—	v2.4.2
CVE-2026-25645	medium	—	requests	—	v2.4.2
CVE-2026-42308	medium	—	pillow	12.1.1	v2.4.2
CVE-2026-42309	medium	—	pillow	12.1.1	v2.4.2
CVE-2026-42310	medium	—	pillow	12.1.1	v2.4.2
CVE-2025-68142	low	—	pymdown-extensions	—	v2.4.2
CVE-2026-4539	low	—	pygments	—	v2.4.2

Showing 38 of 38