ollama/ollama

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

67 of your 162 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 23.37s · analysis 8.68s · 52.9 MB · GitHub API rate-limit (preflight)

https://github.com/ollama/ollama · scanned 2026-06-05 04:39 UTC (1 week, 1 day ago) · 10 languages

330 raw signals (144 security + 186 graph) 11/13 scanners ran 73rd percentile · Go · large (100-500K LoC) System graph score 64 (higher by 25)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 1 day ago · v2 · 134 actionable findings from 2 signal sources. 103 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 78 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	95.0	0.20	19.00
`documentation_score`	77.0	0.15	11.55
`practices_score`	87.0	0.15	13.05
`code_quality`	70.0	0.10	7.00
Overall		1.00	88.3

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 15 Medium 17 Low 59 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 56 System graph 78 Crowd 0 Layer: Security 16 Cicd 8 Software 23 Quality 57 Api 1 Frontend 12 Data 1 Network 8 Hardware 8

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 2 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

2 matching findings on this repo

info Commented-code block (5 lines) in app/ui/app/src/components/StreamingMarkdownCo…
info Commented-code block (6 lines) in app/ui/app/src/components/Message.tsx:92

View all commented-out code findings →

Config drift 5 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

5 matching findings on this repo

low File has no detected symbols: app/ui/app/vite.config.ts
low File has no detected symbols: app/ui/app/tailwind.config.js
low File has no detected symbols: app/ui/app/eslint.config.js
low File has no detected symbols: app/ui/app/vitest.config.ts
low File has no detected symbols: app/ui/app/src/lib/config.ts

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/ff72a002-360c-4f68-8a75-bd77281b31a1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ff72a002-360c-4f68-8a75-bd77281b31a1/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.