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

wsxwj123/claude-gui

https://github.com/wsxwj123/claude-gui · scanned 2026-06-16 01:00 UTC (2 months, 1 week ago)

124 raw signals (0 security + 124 graph)

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

Complete repo analysis

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

JSON
Combined
62.9
/100
Security checks
63
0 findings
System graph
63
100.0% cov · 120 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 33 Low 28 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 120 Crowd 0 Layer: Frontend 26 Security 21 Cicd 4 Quality 49 Api 20
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 62.9/100 with 100.0% coverage. It contains 1001 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 124 findings — concentrated in quality (49), frontend (26), security (21). Risk profile is high: 0 critical, 2 high, 35 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 63 of 120 actionable findings. 124 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 https://api.github.com/repos/wsxwj123/claude-gui/releases/latest (server/routes/version-check.js:62)
`server/routes/version-check.js:62` calls `GET https://api.github.com/repos/wsxwj123/claude-gui/releases/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/wsxwj123/claude-gui/release…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/@anthropic-ai/claude-code/latest (server/routes/version-check.js:145)
`server/routes/version-check.js:145` calls `GET https://registry.npmjs.org/@anthropic-ai/claude-code/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/registry.npmjs.org/@anthropic-ai/claude-code/latest`…
Dangling fetchFetch
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — client/src/components/ArtifactPreview.jsx:82
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — client/src/App.jsx:2298
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 — client/src/components/McpForm.jsx: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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — server/index.js:190
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 — server/routes/version-check.js:62
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 Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
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 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
dtolnay/rust-toolchain@stable can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 34, 37, 53
.github/workflows/tauri.yml:34, 37, 53 (3 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/tauri.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in client/src/components/ArtifactPreview.jsx:82
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
client/src/components/ArtifactPreview.jsx:82 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/audit-public.cjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/audit-public.cjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-http-smoke.cjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-http-smoke.cjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/public-build.cjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/public-build.cjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/index.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/index.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/agents.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/agents.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/chat.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/chat.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/checkpoints.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/checkpoints.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/cli-check.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/cli-check.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/download-update.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/download-update.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/file-changes.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/file-changes.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/files.js:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/files.js:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/git.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/git.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/mcp.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/mcp.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/open-url.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/open-url.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/permission-check.js:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/permission-check.js:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/picker.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/picker.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/processes.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/processes.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/settings.js:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/settings.js:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/version-check.js:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/version-check.js:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server/routes/worktree.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
server/routes/worktree.js:2 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 33 placeholder/mock markers across 8 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 92 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 30 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 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-node@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 29, 81, 100
.github/workflows/tauri.yml:29, 81, 100 (3 hits)
CI/CD securitySupply chainGithub actions
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
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 — client/src/App.jsx:2800
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — client/src/hooks/useWebSocket.js:76
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — server/index.js:93
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — server/routes/chat.js:374
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: GET /active-sessions
`server/routes/sessions.js` declares `GET /active-sessions` 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: GET /custom-providers
`server/routes/settings.js` declares `GET /custom-providers` 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: GET /provider-models
`server/routes/settings.js` declares `GET /provider-models` 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: GET /recent-session
`server/routes/sessions.js` declares `GET /recent-session` 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: GET /sessions/:sessionId
`server/routes/sessions.js` declares `GET /sessions/:sessionId` 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: GET /sessions/:sessionId/file-changes
`server/routes/file-changes.js` declares `GET /sessions/:sessionId/file-changes` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{*splat}
`server/index.js` declares `GET /{*splat}` 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: POST /api/network/password
`server/index.js` declares `POST /api/network/password` 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: POST /custom-providers
`server/routes/settings.js` declares `POST /custom-providers` 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: POST /permissions/request
`server/routes/permissions.js` declares `POST /permissions/request` 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: POST /system/permission-guide-reset
`server/routes/permission-check.js` declares `POST /system/permission-guide-reset` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /custom-providers/:id
`server/routes/settings.js` declares `PUT /custom-providers/:id` 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: PUT /mcp/:name/autoapprove
`server/routes/mcp.js` declares `PUT /mcp/:name/autoapprove` 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: PUT /mcp/:name/disable
`server/routes/mcp.js` declares `PUT /mcp/:name/disable` 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: PUT /mcp/:name/enable
`server/routes/mcp.js` declares `PUT /mcp/:name/enable` 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: PUT /plugins/:name/disable
`server/routes/mcp.js` declares `PUT /plugins/:name/disable` 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: PUT /plugins/:name/enable
`server/routes/mcp.js` declares `PUT /plugins/:name/enable` 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 /api
`server/index.js` declares `USE /api` 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: client/src/App.jsx (6380 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server/routes/settings.js (1096 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/f476c23d-781d-40c7-bd0f-755bc2465a14/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f476c23d-781d-40c7-bd0f-755bc2465a14/

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.