Trust and health report
ollama - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 2w · GitHub synced 2w
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Very active96% signal
last push 1d ago · last release 3w · 25 releases (90d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 658928958
- Not a fork
- Verified publisher: organization account
- Computed 2w
Security intelligence
Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.
OSV dependency advisories
Published findings- Last query
- 1mo
- Scanner
- osv@v1
- Stored findings
- 52
deps.dev advisories
Published findings- Last query
- 1w
- Scanner
- deps.dev@v1
- Stored findings
- 1
OpenSSF Scorecard
No public record from this source- Last query
- 2w
- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
github.com/buger/jsonparser has a denial of service vulnerability
github.com/buger/jsonparser@v1.1.1 · CVE-2026-32285 · deps.dev@v1
https://osv.dev/vulnerability/GHSA-6g7g-w4f8-9c9xGHSA-6g7g-w4f8-9c9x
github.com/buger/jsonparser@v1.1.1 · osv@v1
go.sum
GO-2026-4514
github.com/buger/jsonparser@v1.1.1 · osv@v1
go.sum
GHSA-45gg-vh54-h5m9
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-5cgq-3rg8-m6cv
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-78mq-xcr3-xm33
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-89gr-r52h-f8rx
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-9m57-25v3-79x9
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-f5wc-c3c7-36mc
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-f6x5-jh6r-wrfv
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-j5w8-q4qc-rx2x
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-jppx-rxg9-jmrx
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-q4h4-gmj2-qvw2
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-qpw4-5x99-6vjp
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-rm3j-f69w-wqmq
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-vgwf-h737-ff37
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-w879-237q-wc7r
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-x527-x647-q7gg
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2025-4134
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2025-4135
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5005
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5006
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5013
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5014
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5015
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5016
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5017
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5018
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5019
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5020
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5021
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5023
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5033
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GO-2026-5932
golang.org/x/crypto@v0.43.0 · osv@v1
go.sum
GHSA-44p7-9xx4-hf2g
golang.org/x/image@v0.22.0 · osv@v1
go.sum
GHSA-q675-qj96-32m9
golang.org/x/image@v0.22.0 · osv@v1
go.sum
GO-2026-4815
golang.org/x/image@v0.22.0 · osv@v1
go.sum
GO-2026-4961
golang.org/x/image@v0.22.0 · osv@v1
go.sum
GO-2026-4962
golang.org/x/image@v0.22.0 · osv@v1
go.sum
GO-2026-5031
golang.org/x/image@v0.22.0 · osv@v1
go.sum
GO-2026-5032
golang.org/x/image@v0.22.0 · osv@v1
go.sum
GO-2026-5061
golang.org/x/image@v0.22.0 · osv@v1
go.sum
GO-2026-5062
golang.org/x/image@v0.22.0 · osv@v1
go.sum
GO-2026-5066
golang.org/x/image@v0.22.0 · osv@v1
go.sum
GHSA-5cv4-jp36-h3mw
golang.org/x/net@v0.46.0 · osv@v1
go.sum
GO-2026-4918
golang.org/x/net@v0.46.0 · osv@v1
go.sum
GO-2026-5025
golang.org/x/net@v0.46.0 · osv@v1
go.sum
GO-2026-5026
golang.org/x/net@v0.46.0 · osv@v1
go.sum
GO-2026-5027
golang.org/x/net@v0.46.0 · osv@v1
go.sum
GO-2026-5028
golang.org/x/net@v0.46.0 · osv@v1
go.sum
GO-2026-5029
golang.org/x/net@v0.46.0 · osv@v1
go.sum
GO-2026-5030
golang.org/x/net@v0.46.0 · osv@v1
go.sum
GO-2026-5024
golang.org/x/sys@v0.37.0 · osv@v1
go.sum
Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/ollama-ollama/trust.
Common questions
- Is ollama maintained?
- GraphCanon rates ollama "Very active" (96% maintenance signal from public GitHub metadata, computed 2w). Last push was 1 days ago. 25 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is ollama safe to use?
- Last scanned 1mo (deps profile). Status: 52 low - 52 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify ollama as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is ollama a fork?
- No. ollama is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does ollama have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 52 low - 52 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
- How often is the ollama trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 2w (methodology github_public_v1).
- What does GraphCanon never claim about ollama?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for ollama. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for ollama?
- Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.