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.
Sign up free Scan another repo

timtoole02/Camelid

https://github.com/timtoole02/Camelid · scanned 2026-06-16 00:38 UTC (2 months, 2 weeks ago)

126 raw signals (0 security + 126 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 112 actionable findings from 1 signal source. 14 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
79.1
/100
Security checks
79
0 findings
System graph
79
100.0% cov · 112 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 2 Medium 66 Low 39 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 112 Crowd 0 Layer: Frontend 1 Security 49 Cicd 3 Quality 53 Api 6
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 79.1/100 with 100.0% coverage. It contains 3320 nodes across 14 cross-layer flows, written primarily in mixed languages. Engine surfaced 126 findings — concentrated in quality (53), security (49), cicd (17). Risk profile is high: 0 critical, 2 high, 70 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 88 of 112 actionable findings. 126 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET /cluster-import.json (frontend/src/hooks/useClusterTopology.js:40)
`frontend/src/hooks/useClusterTopology.js:40` calls `GET /cluster-import.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/cluster-import.json` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'eval_used' in scripts/smoke.sh:46
Found a known-risky pattern (eval_used). Review and replace if possible.
scripts/smoke.sh:46 Eval used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/scripts/smoke.mjs:44
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/models/TokenizerPlayground.jsx:44
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/hooks/useDashboardData.js:877
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/apiExamples.js:104
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/bench-generation-prompts.mjs:130
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/bench-llama3-same-host.mjs:360
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/bench-unique-chat.mjs:423
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/chat-parity-qwen3.mjs:55
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/chat-parity-tinyllama.mjs:271
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/model-promotion-smoke-bundle.mjs:213
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/tokenizer-fixture-llama3.mjs:123
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/tokenizer-parity-tinyllama.mjs:101
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/zero-delta-layer-matrix.mjs:189
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tools/conformance/run.mjs:93
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned
dtolnay/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 5 locations
.github/workflows/release.yml:49, 52, 87 (3 hits)
.github/workflows/ci.yml:72, 77 (2 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in frontend/src/lib/devCluster.js:27
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
frontend/src/lib/devCluster.js:27 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in qa/evidence-bundles/frontend-gemini-chat-surface-20260508T1352Z/mock-backend.mjs:71
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
qa/evidence-bundles/frontend-gemini-chat-surface-20260508T1352Z/mock-backend.mjs:71 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/scripts/ui-regression-smoke.mjs:124
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/scripts/ui-regression-smoke.mjs:124 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/views/SettingsView.jsx:97
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/views/SettingsView.jsx:97 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in frontend/vite.config.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
frontend/vite.config.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in qa/evidence-bundles/sev1-llama32-1b-metadata-jinja-4096-8192-current-head-20260514T113325Z-head-7ac14462bbe7/metadata-llama-parity-curl.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
qa/evidence-bundles/sev1-llama32-1b-metadata-jinja-4096-8192-current-head-20260514T113325Z-head-7ac14462bbe7/metadata-llama-parity-curl.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bench-dense-hotloops.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bench-dense-hotloops.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bench-generation-prompts.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bench-generation-prompts.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bench-llama3-same-host.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bench-llama3-same-host.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bench-mlx-memory.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bench-mlx-memory.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bench-q8-hotpath-bundle.mjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bench-q8-hotpath-bundle.mjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bench-unique-chat.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bench-unique-chat.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/build-gemma4-evidence-bundle.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/build-gemma4-evidence-bundle.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/chat-parity-llama3.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/chat-parity-llama3.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/chat-parity-mistral.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/chat-parity-mistral.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/chat-parity-mixtral.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/chat-parity-mixtral.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/chat-parity-tinyllama.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/chat-parity-tinyllama.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/llama3-tokenizer-reference.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/llama3-tokenizer-reference.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/mistral-reference-pack.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/mistral-reference-pack.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/model-promotion-smoke-bundle.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/model-promotion-smoke-bundle.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/prepare-full-support-bundle.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/prepare-full-support-bundle.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/run-llama3-prompt-pack.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/run-llama3-prompt-pack.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/small-model-readiness.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/small-model-readiness.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/tokenizer-fixture-llama3.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/tokenizer-fixture-llama3.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/tokenizer-parity-tinyllama.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/tokenizer-parity-tinyllama.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/zero-delta-layer-matrix.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/zero-delta-layer-matrix.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/bench/v0.1-benchmark-harness.mjs:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/bench/v0.1-benchmark-harness.mjs:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/conformance/run.mjs:33
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/conformance/run.mjs:33 Node child process
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 89 placeholder/mock markers across 24 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 433 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 11 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 11 locations
.github/workflows/ci.yml:14, 20, 69, 96, 99, 119, 122 (7 hits)
.github/workflows/release.yml:31, 36, 69, 81 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
50 tests / 219 src (ratio 0.23).
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `banner__copy` in frontend/src/components/layout/BackendBanner.jsx:13
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `basic_v1` in frontend/src/lib/supportedModels.js:59
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `basic_v1` in scripts/build-gemma4-evidence-bundle.mjs:83
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `endpoint__copy` in frontend/src/components/api/ApiWorkbench.jsx:154
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `head__copy` in frontend/src/views/AnalyticsView.jsx:95
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `head__copy` in frontend/src/views/ApiView.jsx:71
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `head__copy` in frontend/src/views/HistoryView.jsx:25
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `head__copy` in frontend/src/views/InferenceObservatoryView.jsx:39
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `head__copy` in frontend/src/views/MemoryView.jsx:106
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `head__copy` in frontend/src/views/ModelsView.jsx:531
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `head__copy` in frontend/src/views/SystemView.jsx:88
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `head__copy` in frontend/src/views/TelemetryView.jsx:70
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `header__copy` in frontend/src/views/ClusterView.jsx:38
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `pop__copy` in frontend/src/components/ui/EvidenceChip.jsx:162
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `row__copy` in frontend/src/views/CompatibilityView.jsx:82
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/lib/apiExamples.js:105
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: USE /__camelid/backend/launch
`frontend/vite.config.js` declares `USE /__camelid/backend/launch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /__camelid/backend/status
`frontend/vite.config.js` declares `USE /__camelid/backend/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /__camelid/backend/stop
`frontend/vite.config.js` declares `USE /__camelid/backend/stop` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /__camelid/cluster/discover
`frontend/vite.config.js` declares `USE /__camelid/cluster/discover` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /__camelid/cluster/probe
`frontend/vite.config.js` declares `USE /__camelid/cluster/probe` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: frontend/scripts/frontend-integration-smoke.mjs (913 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/hooks/useDashboardData.js (1490 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/views/ModelsView.jsx (1280 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/api/mod.rs (11644 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/cuda_resident.rs (2737 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/execution_plan.rs (1985 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/gemma4_runtime.rs (2074 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/inference.rs (19348 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/inference/tests.rs (11068 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/main.rs (4349 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/metal.rs (18915 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/model.rs (1611 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/tensor/mod.rs (5916 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/api_vertical_slice.rs (4047 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/faef847b-8989-47b6-8af6-c220e98479da/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/faef847b-8989-47b6-8af6-c220e98479da/

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.