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

ai-azure-agentic-va/agent-web-ui

https://github.com/ai-azure-agentic-va/agent-web-ui · scanned 2026-06-17 01:30 UTC (1 month, 2 weeks ago)

30 raw signals (0 security + 30 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -21.1 (diff) · 28 actionable findings from 1 signal source. 2 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
55.6
/100
Security checks
56
0 findings
System graph
56
88.9% cov · 28 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 5 Medium 9 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 28 Crowd 0 Layer: Frontend 5 Hardware 3 Security 6 Quality 7 Api 7
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 55.6/100 with 88.9% coverage. It contains 367 nodes across 11 cross-layer flows, written primarily in mixed languages. Engine surfaced 30 findings — concentrated in quality (7), api (7), security (6). Risk profile is high: 0 critical, 5 high, 9 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 24 of 28 actionable findings. 30 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 /api/defaults (src/components/thread/settings-panel.tsx:46)
`src/components/thread/settings-panel.tsx:46` calls `GET /api/defaults` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/defaults` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/starter-prompts (src/components/thread/index.tsx:252)
`src/components/thread/index.tsx:252` calls `GET /api/starter-prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/starter-prompts` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `create_thread` without auth dependency — mock-langgraph-api/main.py:86
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mock-langgraph-api/main.py:86 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `run_stream` without auth dependency — mock-langgraph-api/main.py:120
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mock-langgraph-api/main.py:120 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `search_threads` without auth dependency — mock-langgraph-api/main.py:94
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
mock-langgraph-api/main.py:94 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/app/api/[..._path]/route.ts:95
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 — src/components/thread/settings-panel.tsx:46
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 hardware Security conf 1.00 Dockerfile runs as root: mock-langgraph-api/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in mock-langgraph-api/main.py:35
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
mock-langgraph-api/main.py:35 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/app/api/[..._path]/route.ts:28
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/app/api/[..._path]/route.ts:28 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/smoke-chat.mjs:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/smoke-chat.mjs:23 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 16 placeholder/mock markers across 7 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 Tests conf 1.00 Very low test-to-source ratio
6 test file(s) for 70 source file(s) (ratio 0.09). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 14 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AGENT_BACKEND_URL`, `BACKEND_DEV_BEARER_TOKEN`, `BACKEND_DEV_GROUP_IDS`, `BACKEND_URL`, `DEFAULT_STARTER_PROMPTS`, `NODE_ENV`, `PARENT_AGENT_API_URL`, `PARENT_AGENT_DEV_TOKEN` + 6 more. Add them (with a placeholder/comment) to .env.example so onbo…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 9 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 hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 7, 21, 40
Dockerfile:7, 21, 40 (3 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
mock-langgraph-api/Dockerfile:4 containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/app/chat/auth/callback/route.ts:36
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 /threads/{thread_id}
`mock-langgraph-api/main.py` declares `GET /threads/{thread_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: GET /threads/{thread_id}/history
`mock-langgraph-api/main.py` declares `GET /threads/{thread_id}/history` 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 /threads
`mock-langgraph-api/main.py` declares `POST /threads` 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 /threads/search
`mock-langgraph-api/main.py` declares `POST /threads/search` 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 /threads/{thread_id}/runs/stream
`mock-langgraph-api/main.py` declares `POST /threads/{thread_id}/runs/stream` 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
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/42bd021d-38ad-48db-b7ea-5dd9178950c1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/42bd021d-38ad-48db-b7ea-5dd9178950c1/

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.