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.

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

100.0% cov · 120 findings

Severity distribution — click a segment to filter

Active filters: layer: frontend × 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

Exclude dismissed / FP Exclude test files

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 5 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.

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

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

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.