Tools / ollama / Security

Security Deep Dive

ollama

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against v0.30.4.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 2d 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: 22d ago

Release cadence: weekly Present

2d median over recent releases Release history

Latest release: today

Maintainer active Present

Recent commit activity Repository

Last commit: 2d 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 4 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/26h 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 53.1/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

4.7

10%

supply chain risk: 53.1 transitive cves: 0c/26h

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

45% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

981 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 (4) All (57)

Medium 1 Low 1 Unknown 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-33809	medium	—	golang.org/x/image	v0.22.0	v0.23.2
GHSA-xffm-g5w8-qvg7	low	—	@eslint/plugin-kit	0.3.3	v0.23.2
CVE-2026-33812	unknown	—	golang.org/x/image	v0.22.0	v0.23.2
CVE-2026-33813	unknown	—	golang.org/x/image	v0.22.0	v0.23.2

Showing 4 of 57