updated 2026-08-15 10:46 UTC

Ollama

ollama/ollama

Get up and running with Kimi-K2.6, GLM-5.2, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models.

LLM Gateways & Infra Go Grade B Listed MIT
67.5/100
Rank #167 of 1283
Compare Ollama

How does it stack up against its LLM Gateways & Infra neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-15 · 0d ago
Recent change
Rank +3

Is Ollama safe? Ollama scores 67.5/100 (Grade B), ranked #167 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.3/10; 90% of recent commits are signed; last pushed 2026-08-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in LLM Gateways & Infra

#3 vLLM — 81.8 (A) → #4 LiteLLM — 77.6 (B) → #6 Instructor — 66.0 (B) → #7 Jan — 64.5 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-15
Rank Moved
Rank rose 13 spots (#180 → #167)
2026-08-13
Rank Moved
Rank dropped 11 spots (#167 → #178)
2026-08-12
Rank Moved
Rank rose 13 spots (#180 → #167)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.3/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with Bifrost Get email alerts for Ollama View LLM Gateways & Infra Report missing data
99.7
Activity sub-score · out of 100
#5
In LLM Gateways & Infra

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-15 10:46 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars
178.5k
Forks
17.4k
Last Push
2026-08-15
today
Commits (4 wk)
106
Downloads (7d)
—
HN mentions (30d)
66
Open Issues
2388
Rank Change
▲13
was #180

Analysis

HVTrust Dimensions vs LLM Gateways & Infra

67.5 / 100 · 100.0% confidence

Ollama LLM Gateways & Infra average (13 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.1 / 25
0.9 above avg 10.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.1 below avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
13.0 / 17
0.9 above avg 12.1
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
2.9 above avg 17.1
AdoptionLog-scaled stars · package downloads
12.6 / 20
1.3 below avg 13.9

Activity Inputs

99.7 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
19.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.3 / 10
OpenSSF Scorecard · scanned Aug 15, 2026
Signed Commits
90%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 7
CII-Best-Practices 0
Code-Review 9
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 10
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Ollama safe?

Ollama has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Ollama publish package provenance?
No published build provenance is currently detected for Ollama. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Ollama have an OpenSSF Scorecard?
Ollama has an OpenSSF Scorecard score of 5.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Ollama actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Ollama use?
Ollama ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ollama's commits signed?
90% of the last 100 commits to Ollama are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Ollama head-to-head

Ollama vs Bifrost → Ollama vs Headroom → Ollama vs vLLM →

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Ollama?

For maintainers

HVTrust scores Ollama from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 6Grade 2Listed 1HVTrust 1Scorecard 1
2026-08-15
Rank Moved
Rank rose 13 spots (#180 → #167)
2026-08-13
Rank Moved
Rank dropped 11 spots (#167 → #178)
2026-08-12
Rank Moved
Rank rose 13 spots (#180 → #167)
2026-08-08
Rank Moved
Rank dropped 24 spots (#142 → #166)
2026-07-14
Grade Changed
Trust grade C → B
2026-07-13
Rank Moved
Rank dropped 12 spots (#127 → #139)
2026-06-04
Scorecard Added
OSSF Scorecard: 5.4/10
2026-06-04
Grade Changed
Trust grade D → B
2026-06-04
Rank Moved
Rank rose 102 spots (#180 → #78)
2026-06-04
HVTrust Changed
HVTrust up 30.3pts (36.9 → 67.2)
2026-06-02
Newly Listed
First tracked at rank #181
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 67.5 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/ollama.svg)](https://hvtracker.net/agents/ollama)
HTML:
<a href="https://hvtracker.net/agents/ollama"><img src="https://hvtracker.net/badge/ollama.svg" alt="HVTrust"></a>

Other agents in LLM Gateways & Infra

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON