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
45 of your 134 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.64s · analysis 41.65s · 4.4 MB · GitHub API rate-limit (preflight)

simpx/loopat

https://github.com/simpx/loopat · scanned 2026-06-05 17:42 UTC (4 days, 21 hours ago) · 10 languages

698 raw signals (120 security + 578 graph) 39th percentile · Typescript · medium (20-100K LoC) System graph score 46 (higher by 21)

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

Complete repo analysis

Last scanned 4 days, 21 hours ago · v2 · 345 actionable findings from 2 signal sources. 64 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
53.6
/100
Security checks
62
63 findings
System graph
46
100.0% cov · 282 findings
Critical
20
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 58.2 0.25 14.55
testing_score 85.0 0.20 17.00
documentation_score 68.7 0.15 10.30
practices_score 75.0 0.15 11.25
code_quality 46.3 0.10 4.63
Overall 1.00 66.7
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 20 High 71 Medium 26 Low 135 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 63 System graph 282 Crowd 0 Layer: Quality 89 Cicd 11 Security 18 Software 35 Frontend 80 Hardware 3 Api 109
Scan summary Quality grade B- (67/100). Dimensions: security 58, maintainability 60. 120 findings (15 security). 63,038 lines analyzed.

Showing 249 of 345 actionable findings. 409 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.

critical Security checks quality Quality conf 0.80 ✓ Repobility Admin endpoint without auth: DELETE /api/admin/profiles/:name
Express route on /admin path (/api/admin/profiles/:name) with no auth middleware.
server/src/index.ts:483
critical Security checks quality Quality conf 0.80 ✓ Repobility Admin endpoint without auth: DELETE /api/admin/users/:id
Express route on /admin path (/api/admin/users/:id) with no auth middleware.
server/src/index.ts:436
critical Security checks quality Quality conf 0.80 ✓ Repobility Admin endpoint without auth: POST /api/admin/profiles
Express route on /admin path (/api/admin/profiles) with no auth middleware.
server/src/index.ts:456
critical Security checks quality Quality conf 0.80 ✓ Repobility Admin endpoint without auth: POST /api/admin/system/check
Express route on /admin path (/api/admin/system/check) with no auth middleware.
server/src/index.ts:587
critical Security checks quality Quality conf 0.80 ✓ Repobility Admin endpoint without auth: POST /api/admin/system/pull
Express route on /admin path (/api/admin/system/pull) with no auth middleware.
server/src/index.ts:602
critical Security checks quality Quality conf 0.80 ✓ Repobility Admin endpoint without auth: POST /api/admin/users/:id/activate
Express route on /admin path (/api/admin/users/:id/activate) with no auth middleware.
server/src/index.ts:415
critical Security checks quality Quality conf 0.80 ✓ Repobility Admin endpoint without auth: POST /api/admin/users/:id/role
Express route on /admin path (/api/admin/users/:id/role) with no auth middleware.
server/src/index.ts:422
critical Security checks quality Quality conf 0.80 ✓ Repobility Admin endpoint without auth: PUT /api/admin/presets
Express route on /admin path (/api/admin/presets) with no auth middleware.
server/src/index.ts:504
critical Security checks quality Quality conf 0.80 ✓ Repobility Admin endpoint without auth: PUT /api/admin/profiles/:name
Express route on /admin path (/api/admin/profiles/:name) with no auth middleware.
server/src/index.ts:474
critical Security checks cicd CI/CD security conf 0.98 Compose service runs privileged
Privileged containers receive broad host kernel capabilities and can bypass container isolation.
docker-compose.yml:1 CI/CD securitycontainers
critical System graph security Secrets conf 1.00 Possible secret in dogfood/setup.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
dogfood/setup.ts:36
critical System graph security Secrets conf 1.00 Possible secret in dogfood/sync/setup.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
dogfood/sync/setup.ts:32
critical System graph security Secrets conf 1.00 Possible secret in e2e/globalSetup.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
e2e/globalSetup.ts:17
critical System graph security Secrets conf 1.00 Possible secret in scripts/e2e/context-flow-ssh.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/e2e/context-flow-ssh.ts:77
critical System graph security Secrets conf 1.00 Possible secret in scripts/e2e/context-flow.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/e2e/context-flow.ts:61
critical System graph security Secrets conf 1.00 Possible secret in scripts/e2e/personal-permissions.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/e2e/personal-permissions.ts:100
critical System graph security Secrets conf 1.00 Possible secret in scripts/e2e/setup-ws.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/e2e/setup-ws.ts:14
high Security checks software dependencies conf 0.90 ✓ Repobility Dockerfile FROM `oven/bun:1-slim` not pinned by digest
`FROM oven/bun:1-slim` resolves the tag at build time. The registry CAN re-push a different image for the same tag, so every build is potentially different. Production images should pin to `image@sha256:...` for reproducibility + supply-chain integrity.
Dockerfile:1
high Security checks quality Quality conf 0.80 ✓ Repobility Express DELETE /api/chat/channels/:id has no auth
Express route DELETE /api/chat/channels/:id declared without an auth middleware in its handler chain. Destructive methods (POST/PUT/DELETE/PATCH) on unauthenticated routes are OWASP A01:2021 broken access control.
server/src/index.ts:2770
high Security checks quality Quality conf 0.80 ✓ Repobility Express POST /api/auth/login has no auth
Express route POST /api/auth/login declared without an auth middleware in its handler chain. Destructive methods (POST/PUT/DELETE/PATCH) on unauthenticated routes are OWASP A01:2021 broken access control.
server/src/index.ts:376
high Security checks quality Quality conf 0.80 ✓ Repobility Express POST /api/auth/logout has no auth
Express route POST /api/auth/logout declared without an auth middleware in its handler chain. Destructive methods (POST/PUT/DELETE/PATCH) on unauthenticated routes are OWASP A01:2021 broken access control.
server/src/index.ts:393
high Security checks quality Quality conf 0.80 ✓ Repobility Express POST /api/auth/register has no auth
Express route POST /api/auth/register declared without an auth middleware in its handler chain. Destructive methods (POST/PUT/DELETE/PATCH) on unauthenticated routes are OWASP A01:2021 broken access control.
server/src/index.ts:343
high Security checks quality Quality conf 0.80 ✓ Repobility Express PUT /api/serve/config has no auth
Express route PUT /api/serve/config declared without an auth middleware in its handler chain. Destructive methods (POST/PUT/DELETE/PATCH) on unauthenticated routes are OWASP A01:2021 broken access control.
server/src/index.ts:175
low Security checks cicd CI/CD security conf 0.90 ✓ Repobility 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
Action `actions/checkout` pinned to mutable ref `@v5` uses a mutable tag or branch. Pin external actions to a reviewed full commit SHA when the workflow is security-sensitive.
3 files, 4 locations
.github/workflows/publish.yml:26, 32 (2 hits)
.github/workflows/docker.yml:26
.github/workflows/sandbox-image.yml:34
CI/CD securitySupply chainGitHub Actions
high Security checks software dependencies conf 0.88 instant: RUSTSEC-2024-0384
`instant` is unmaintained
server/src/port-proxy-rs/Cargo.lock
high Security checks security auth conf 0.83 4 occurrences Secret-like setting is echoed into a password input value
Settings screens sometimes render API keys, tokens, or passwords back into HTML/JSX password fields. That still exposes the secret to page source, browser extensions, screenshots, and DOM scraping.
3 files, 4 locations
web/src/components/dialog/PersonalRepoPanel.tsx:1150, 1368 (2 hits)
web/src/components/dialog/AdminDialog.tsx:534
web/src/pages/AuthPage.tsx:116
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/envs/1STARTS (server/test/api-mcp.test.ts:268)
`server/test/api-mcp.test.ts:268` calls `DELETE /api/envs/1STARTS` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/envs/1starts` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/envs/foo%3Brm (server/test/api-mcp.test.ts:273)
`server/test/api-mcp.test.ts:273` calls `DELETE /api/envs/foo%3Brm` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/envs/foo%3brm` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/envs/GITHUB_TOKEN (server/test/api-mcp.test.ts:246)
`server/test/api-mcp.test.ts:246` calls `DELETE /api/envs/GITHUB_TOKEN` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/envs/github_token` If this points at an external API, prefix it with `https://` so the …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/envs/lowercase (server/test/api-mcp.test.ts:263)
`server/test/api-mcp.test.ts:263` calls `DELETE /api/envs/lowercase` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/envs/lowercase` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/envs/NEVER_EXISTED (server/test/api-mcp.test.ts:255)
`server/test/api-mcp.test.ts:255` calls `DELETE /api/envs/NEVER_EXISTED` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/envs/never_existed` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/loops/${createdLoopId} (server/test/api-v1.test.ts:258)
`server/test/api-v1.test.ts:258` calls `DELETE /api/v1/loops/${createdLoopId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/loops/${id} (server/test/api-v1.test.ts:287)
`server/test/api-v1.test.ts:287` calls `DELETE /api/v1/loops/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/me/tokens/${cj.tokenId} (server/test/api-v1.test.ts:76)
`server/test/api-v1.test.ts:76` calls `DELETE /api/v1/me/tokens/${cj.tokenId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/me/tokens/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/me/tokens/tok_nonexistent (server/test/api-v1.test.ts:97)
`server/test/api-v1.test.ts:97` calls `DELETE /api/v1/me/tokens/tok_nonexistent` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/me/tokens/tok_nonexistent` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops (server/test/api-v1.test.ts:117)
`server/test/api-v1.test.ts:117` calls `GET /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops (server/test/api-v1.test.ts:122)
`server/test/api-v1.test.ts:122` calls `GET /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops (server/test/api-v1.test.ts:129)
`server/test/api-v1.test.ts:129` calls `GET /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops (server/test/api-v1.test.ts:136)
`server/test/api-v1.test.ts:136` calls `GET /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops (server/test/api-v1.test.ts:143)
`server/test/api-v1.test.ts:143` calls `GET /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops (server/test/api-v1.test.ts:206)
`server/test/api-v1.test.ts:206` calls `GET /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops (server/test/api-v1.test.ts:227)
`server/test/api-v1.test.ts:227` calls `GET /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops (server/test/api-v1.test.ts:231)
`server/test/api-v1.test.ts:231` calls `GET /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops (server/test/api-v1.test.ts:268)
`server/test/api-v1.test.ts:268` calls `GET /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops/${createdLoopId} (server/test/api-v1.test.ts:237)
`server/test/api-v1.test.ts:237` calls `GET /api/v1/loops/${createdLoopId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops/${createdLoopId} (server/test/api-v1.test.ts:247)
`server/test/api-v1.test.ts:247` calls `GET /api/v1/loops/${createdLoopId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops/${createdLoopId} (server/test/api-v1.test.ts:263)
`server/test/api-v1.test.ts:263` calls `GET /api/v1/loops/${createdLoopId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops/loop_doesnotexist (server/test/api-v1.test.ts:253)
`server/test/api-v1.test.ts:253` calls `GET /api/v1/loops/loop_doesnotexist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/loop_doesnotexist` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops?archived=true (server/test/api-v1.test.ts:274)
`server/test/api-v1.test.ts:274` calls `GET /api/v1/loops?archived=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/loops?limit=1 (server/test/api-v1.test.ts:215)
`server/test/api-v1.test.ts:215` calls `GET /api/v1/loops?limit=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/me/tokens (server/test/api-v1.test.ts:52)
`server/test/api-v1.test.ts:52` calls `GET /api/v1/me/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/me/tokens` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/me/tokens (server/test/api-v1.test.ts:69)
`server/test/api-v1.test.ts:69` calls `GET /api/v1/me/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/me/tokens` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/me/tokens (server/test/api-v1.test.ts:82)
`server/test/api-v1.test.ts:82` calls `GET /api/v1/me/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/me/tokens` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/me/tokens (server/test/api-v1.test.ts:92)
`server/test/api-v1.test.ts:92` calls `GET /api/v1/me/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/me/tokens` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testServerPort}/api/health (dogfood/first-run/setup.ts:129)
`dogfood/first-run/setup.ts:129` calls `GET http://127.0.0.1:${testServerPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testServerPort}/api/health (dogfood/setup.ts:125)
`dogfood/setup.ts:125` calls `GET http://127.0.0.1:${testServerPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testServerPort}/api/health (e2e/globalSetup.ts:74)
`e2e/globalSetup.ts:74` calls `GET http://127.0.0.1:${testServerPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops (server/test/api-v1.test.ts:153)
`server/test/api-v1.test.ts:153` calls `POST /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops (server/test/api-v1.test.ts:174)
`server/test/api-v1.test.ts:174` calls `POST /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops (server/test/api-v1.test.ts:186)
`server/test/api-v1.test.ts:186` calls `POST /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops (server/test/api-v1.test.ts:196)
`server/test/api-v1.test.ts:196` calls `POST /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops (server/test/api-v1.test.ts:222)
`server/test/api-v1.test.ts:222` calls `POST /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops (server/test/api-v1.test.ts:281)
`server/test/api-v1.test.ts:281` calls `POST /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops (server/test/api-v1.test.ts:298)
`server/test/api-v1.test.ts:298` calls `POST /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops (server/test/api-v1.test.ts:359)
`server/test/api-v1.test.ts:359` calls `POST /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops (server/test/chat-integration.test.ts:163)
`server/test/chat-integration.test.ts:163` calls `POST /api/v1/loops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/${id}/choices/choice_does_not_exist (server/test/api-v1.test.ts:378)
`server/test/api-v1.test.ts:378` calls `POST /api/v1/loops/${id}/choices/choice_does_not_exist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>/choices/choice_does_not_exist` If this points at a…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/${id}/choices/choice_xyz (server/test/api-v1.test.ts:368)
`server/test/api-v1.test.ts:368` calls `POST /api/v1/loops/${id}/choices/choice_xyz` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>/choices/choice_xyz` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/${id}/interrupt (server/test/api-v1.test.ts:388)
`server/test/api-v1.test.ts:388` calls `POST /api/v1/loops/${id}/interrupt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>/interrupt` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/${id}/interrupt (server/test/api-v1.test.ts:396)
`server/test/api-v1.test.ts:396` calls `POST /api/v1/loops/${id}/interrupt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>/interrupt` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/${id}/messages (server/test/api-v1.test.ts:322)
`server/test/api-v1.test.ts:322` calls `POST /api/v1/loops/${id}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>/messages` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/${id}/messages (server/test/api-v1.test.ts:332)
`server/test/api-v1.test.ts:332` calls `POST /api/v1/loops/${id}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>/messages` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/${id}/messages (server/test/api-v1.test.ts:342)
`server/test/api-v1.test.ts:342` calls `POST /api/v1/loops/${id}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>/messages` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/${loop.id}/messages (server/test/chat-integration.test.ts:173)
`server/test/chat-integration.test.ts:173` calls `POST /api/v1/loops/${loop.id}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/loops/<p>/messages` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/loop_${loopId}/choices/${choiceId} (web/src/useLoopRuntime.tsx:652)
`web/src/useLoopRuntime.tsx:652` calls `POST /api/v1/loops/loop_${loopId}/choices/${choiceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/loops/loop_/<p>/choices/<p>` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/loop_${loopId}/choices/${choiceId} (web/src/useLoopRuntime.tsx:697)
`web/src/useLoopRuntime.tsx:697` calls `POST /api/v1/loops/loop_${loopId}/choices/${choiceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/loops/loop_/<p>/choices/<p>` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/loop_${loopId}/interrupt (web/src/useLoopRuntime.tsx:830)
`web/src/useLoopRuntime.tsx:830` calls `POST /api/v1/loops/loop_${loopId}/interrupt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/loops/loop_/<p>/interrupt` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/loop_${loopId}/messages (web/src/useLoopRuntime.tsx:1631)
`web/src/useLoopRuntime.tsx:1631` calls `POST /api/v1/loops/loop_${loopId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/loops/loop_/<p>/messages` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/loop_${loopId}/messages (web/src/useLoopRuntime.tsx:874)
`web/src/useLoopRuntime.tsx:874` calls `POST /api/v1/loops/loop_${loopId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/loops/loop_/<p>/messages` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/loops/loop_${loopId}/messages (web/src/useLoopRuntime.tsx:987)
`web/src/useLoopRuntime.tsx:987` calls `POST /api/v1/loops/loop_${loopId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/loops/loop_/<p>/messages` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/me/tokens (server/test/api-v1.test.ts:108)
`server/test/api-v1.test.ts:108` calls `POST /api/v1/me/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/me/tokens` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/me/tokens (server/test/api-v1.test.ts:57)
`server/test/api-v1.test.ts:57` calls `POST /api/v1/me/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/me/tokens` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/me/tokens (server/test/api-v1.test.ts:87)
`server/test/api-v1.test.ts:87` calls `POST /api/v1/me/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/me/tokens` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST https://github.com/login/device/code (server/src/github.ts:66)
`server/src/github.ts:66` calls `POST https://github.com/login/device/code` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/github.com/login/device/code` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://github.com/login/oauth/access_token (server/src/github.ts:81)
`server/src/github.ts:81` calls `POST https://github.com/login/oauth/access_token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/github.com/login/oauth/access_token` If this points at an external API, prefix…
Dangling fetchFetch
high System graph hardware Supply chain conf 1.00 Dockerfile pipes a remote installer into a shell
Executing downloaded code during image build gives the remote endpoint build-time code execution. Prefer pinned packages or verify downloaded installers by checksum/signature.
Dockerfile:19 containersRemote installer
medium Security checks quality Error handling conf 1.00 3 occurrences [ERR002] Empty Catch Block: Empty catch blocks hide errors.
Log the error or rethrow it. Use console.error() at minimum.
3 files, 3 locations
scripts/loopat.ts:268
server/src/api-tokens.ts:105
server/src/auth.ts:246
medium Security checks cicd CI/CD security conf 0.68 Agent auto-approve or skip-permissions mode is easy to enable
Codex/agent auto-approve, YOLO, or skip-permissions modes can be useful in isolated automation, but they remove the human checkpoint before command execution, network access, and file edits.
server/src/podman.ts:412 CI/CD securityagent runtimepermissions
high Security checks quality Quality conf 0.72 Agent control bridge may listen on a network interface without visible auth
Agent, MCP, sidecar, and command bridge servers often start as local helpers. Binding them to 0.0.0.0 or a default all-interface listener without an authorization guard can expose tool execution or session data to the LAN.
server/src/podman.ts:25
medium Security checks cicd CI/CD security conf 0.94 Compose service `loopat` image uses the latest tag
The latest tag is mutable and can change without a code review, producing different images from the same source.
docker-compose.yml:1 CI/CD securitycontainers
medium Security checks cicd CI/CD security conf 0.76 Dockerfile copies broad context with incomplete .dockerignore
COPY . or ADD . is safer when .dockerignore excludes secrets, git history, keys, and generated artifacts.
Dockerfile:24 CI/CD securitycontainers
high Security checks quality Quality conf 0.80 8 occurrences localStorage write failures are swallowed silently
localStorage quotas are small and writes can fail. Catching storage errors without a user-visible warning causes silent data loss when notes, images, or snapshots exceed quota.
8 files, 8 locations
web/src/App.tsx:360
web/src/Editor.tsx:93
web/src/components/SetupPersonalRepoCard.tsx:40
web/src/components/Tree.tsx:25
web/src/components/chat/ChatInterface.tsx:51
web/src/pages/ContextPage.tsx:290
web/src/theme.tsx:52
web/src/useLoopRuntime.tsx:48
medium Security checks quality Quality conf 0.70 Public web app has no Content Security Policy
A Content Security Policy reduces the blast radius of injected scripts if the app is ever served through preview, static hosting, or a web container outside its normal sandbox.
index.html
medium Security checks quality Quality conf 0.78 Public web service has no security.txt
security.txt gives researchers and customers a safe disclosure channel. Public web apps and APIs should publish it under /.well-known/security.txt.
.well-known/security.txt
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/src/components/chat/GraphvizBlock.tsx:106
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/src/components/chat/PlantUMLBlock.tsx:116
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/src/components/chat/SvgRenderer.tsx:160
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/src/components/chat/ToolRenderer.tsx:309
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 — dogfood/first-run/setup.ts:129
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 — dogfood/setup.ts:125
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 — e2e/globalSetup.ts:74
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/src/a2a.ts:97
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/test/api-e2e/mock-anthropic.ts:88
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 — web/src/api.ts: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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — web/src/useLoopRuntime.tsx:874
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 6 occurrences Frontend route `/loop/:id` has no Link/navigate to it — web/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
6 occurrences
repo-level (6 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/metadata-action@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 4 locations
.github/workflows/sandbox-image.yml:55, 62 (2 hits)
.github/workflows/docker.yml:38
.github/workflows/publish.yml:29
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/docker.yml 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/sandbox-image.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in server/src/index.ts:109
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
server/src/index.ts:109 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/src/components/chat/GraphvizBlock.tsx:106
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/src/components/chat/GraphvizBlock.tsx:106 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/src/components/chat/PlantUMLBlock.tsx:116
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/src/components/chat/PlantUMLBlock.tsx:116 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/src/components/chat/SvgRenderer.tsx:160
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/src/components/chat/SvgRenderer.tsx:160 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/src/components/chat/ToolRenderer.tsx:309
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/src/components/chat/ToolRenderer.tsx:309 Dangerous innerhtml
low Security checks cicd CI/CD security conf 0.72 .dockerignore misses sensitive defaults
.dockerignore exists but does not cover common secret or VCS patterns.
.dockerignore CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.62 Compose service lacks no-new-privileges hardening
no-new-privileges prevents processes from gaining additional privileges through setuid binaries or file capabilities.
docker-compose.yml:1 CI/CD securitycontainers
low Security checks quality Quality conf 0.60 15 occurrences Duplicated implementation block across source files
Duplicate implementation blocks are maintenance debt. Keep them visible, but they are not a high-severity defect unless the duplicated logic is security-sensitive or drifting.
12 files, 14 locations
dogfood/sync/setup.ts:10, 11 (2 hits)
web/src/components/assistant-ui/tool-group.tsx:48, 75 (2 hits)
dogfood/playwright.config.ts:18
dogfood/setup.ts:12
dogfood/sync/playwright.config.ts:18
e2e/globalSetup.ts:33
server/src/workspace.ts:51
web/src/components/assistant-ui/tool-fallback.tsx:38
duplicationquality
low Security checks software dependencies conf 0.90 npm package `@codemirror/view` is minor version(s) behind (^6.42.1 -> 6.43.0)
`@codemirror/view` is pinned/resolved at ^6.42.1 but the latest stable release on the npm registry is 6.43.0 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
web/package.json
low Security checks software dependencies conf 0.90 npm package `@types/react-dom` is minor version(s) behind (^19.0.0 -> 19.2.3)
`@types/react-dom` is pinned/resolved at ^19.0.0 but the latest stable release on the npm registry is 19.2.3 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
web/package.json
low Security checks software dependencies conf 0.90 npm package `@viz-js/viz` is minor version(s) behind (^3.27.0 -> 3.28.0)
`@viz-js/viz` is pinned/resolved at ^3.27.0 but the latest stable release on the npm registry is 3.28.0 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
web/package.json
low Security checks software dependencies conf 0.90 npm package `tailwind-merge` is minor version(s) behind (^3.5.0 -> 3.6.0)
`tailwind-merge` is pinned/resolved at ^3.5.0 but the latest stable release on the npm registry is 3.6.0 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
web/package.json
low Security checks quality Quality conf 0.64 Public docs site has no llms.txt
AI coding agents increasingly read llms.txt to find canonical docs and API workflows. Without it, agents are more likely to browse pages repeatedly or use stale instructions.
llms.txt
low Security checks quality Quality conf 0.50 Public web app has no humans.txt
humans.txt is optional, but it gives operators and reviewers a simple place to find ownership, contact, and important public documentation links.
humans.txt
low Security checks quality Quality conf 0.74 Public web app has no robots.txt
Public websites should publish a robots.txt file so crawlers and AI agents can discover crawl rules and sitemap locations without guessing.
robots.txt
low Security checks quality Quality conf 0.72 Public web app has no sitemap
A sitemap gives search engines, docs crawlers, and AI agents a structured list of public pages. Without one, important docs and product pages are easy to miss.
sitemap.xml
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — web/src/components/chat/ChatInterface.tsx:453
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — web/src/components/ChatListContent.tsx:119
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — web/src/pages/LoopPage.tsx:438
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: oven/bun:1-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph software Dead code candidate conf 1.00 File has no detected symbols: e2e/loop.spec.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: scripts/e2e/setup-ws.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/src/api-v1-openapi.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/src/presets.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/api-e2e/cross-surface.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/api-e2e/file-roundtrip.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/api-e2e/hello.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/api-e2e/multi-tool.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/api-e2e/queue.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/api-e2e/reconnect.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/api-e2e/tool-error.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/e2e-ai.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/host-exec.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/mcp-oauth.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: server/test/profile-description.test.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: web/src/components/assistant-ui/tooltip-icon-button.tsx
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: web/src/main.tsx
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — web/src/components/DiffModal.tsx:80
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — web/src/components/kanban/CardDetailDialog.tsx:114
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — web/src/FileTree.tsx:243
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — web/src/pages/ChatPage.tsx:682
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — web/src/pages/ContextPage.tsx:683
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — web/src/pages/KanbanPage.tsx:226
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Tests conf 1.00 Low test-to-source ratio
37 tests / 178 src (ratio 0.21).
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `editOld` in web/src/components/chat/ToolRenderer.tsx:626
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 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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — dogfood/attach-detach/journey.spec.ts:163
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 — dogfood/concurrent-push/journey.spec.ts:278
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 — dogfood/context-notes-sync/journey.spec.ts:184
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 — dogfood/first-5-minutes/journey.spec.ts:234
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 — dogfood/first-run/journey.spec.ts:165
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 — dogfood/first-run/setup.ts:59
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 — dogfood/first-run/teardown.ts:19
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 — dogfood/multi-turn-task/journey.spec.ts:202
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 — dogfood/repos-page/journey.spec.ts:158
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 — dogfood/second-loop-warm/journey.spec.ts:234
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 — dogfood/setup.ts:61
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 — dogfood/sync/setup.ts:81
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 — dogfood/sync/sync.spec.ts:59
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 — dogfood/sync/teardown.ts:34
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 — dogfood/sync/zzz-s3-ai.spec.ts:44
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 — dogfood/teardown.ts:21
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 — e2e/globalSetup.ts:44
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 — e2e/globalTeardown.ts:18
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 — scripts/e2e/context-flow-ssh.ts:91
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 — scripts/e2e/context-flow.ts:79
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 — scripts/e2e/personal-permissions.ts:133
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 — scripts/e2e/setup-ws.ts:18
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 — scripts/loopat.ts:87
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 — scripts/mock-mcp-server.ts:131
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/src/bootstrap.ts:148
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/src/index.ts:3410
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/src/loops.ts:313
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/src/podman.ts:634
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/src/providers.ts:41
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/src/serve.ts:270
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/src/session.ts:262
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/src/uninstall.ts: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 — web/src/App.tsx:134
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: DELETE /api/admin/profiles/:name
`server/src/index.ts` declares `DELETE /api/admin/profiles/:name` 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: DELETE /api/admin/users/:id
`server/src/index.ts` declares `DELETE /api/admin/users/: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: DELETE /loops/:id
`server/src/api-v1.ts` declares `DELETE /loops/: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: DELETE /me/tokens/:tokenId
`server/src/api-v1.ts` declares `DELETE /me/tokens/:tokenId` 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 /a2a/:user/.well-known/agent-card.json
`server/src/a2a.ts` declares `GET /a2a/:user/.well-known/agent-card.json` 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 /a2a/:user/agent-card.json
`server/src/a2a.ts` declares `GET /a2a/:user/agent-card.json` 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 /a2a/:user/agent.json
`server/src/a2a.ts` declares `GET /a2a/:user/agent.json` 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 /api/admin/presets
`server/src/index.ts` declares `GET /api/admin/presets` 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 /api/admin/profiles
`server/src/index.ts` declares `GET /api/admin/profiles` 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 /api/admin/profiles/:name
`server/src/index.ts` declares `GET /api/admin/profiles/:name` 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 /api/admin/system
`server/src/index.ts` declares `GET /api/admin/system` 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 /api/admin/users
`server/src/index.ts` declares `GET /api/admin/users` 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 /api/auth/me
`server/src/index.ts` declares `GET /api/auth/me` 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 /api/health
`server/src/index.ts` declares `GET /api/health` 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 /api/mcp-auth/callback
`server/src/index.ts` declares `GET /api/mcp-auth/callback` 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 /api/providers
`server/src/index.ts` declares `GET /api/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 /api/serve/alias-check
`server/src/index.ts` declares `GET /api/serve/alias-check` 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 /api/serve/available-port
`server/src/index.ts` declares `GET /api/serve/available-port` 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 /api/serve/check-port
`server/src/index.ts` declares `GET /api/serve/check-port` 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 /api/serve/config
`server/src/index.ts` declares `GET /api/serve/config` 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 /api/settings/personal
`server/src/index.ts` declares `GET /api/settings/personal` 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 /api/version
`server/src/index.ts` declares `GET /api/version` 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 /docs
`server/src/api-v1.ts` declares `GET /docs` 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 /loops
`server/src/api-v1.ts` declares `GET /loops` 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 /loops/:id
`server/src/api-v1.ts` declares `GET /loops/: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 /loops/:id/events
`server/src/api-v1.ts` declares `GET /loops/:id/events` 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 /me/tokens
`server/src/api-v1.ts` declares `GET /me/tokens` 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 /openapi.json
`server/src/api-v1.ts` declares `GET /openapi.json` 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 /a2a/:user
`server/src/a2a.ts` declares `POST /a2a/:user` 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/admin/profiles
`server/src/index.ts` declares `POST /api/admin/profiles` 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/admin/system/check
`server/src/index.ts` declares `POST /api/admin/system/check` 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/admin/system/pull
`server/src/index.ts` declares `POST /api/admin/system/pull` 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/admin/users/:id/activate
`server/src/index.ts` declares `POST /api/admin/users/:id/activate` 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/admin/users/:id/role
`server/src/index.ts` declares `POST /api/admin/users/:id/role` 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/auth/login
`server/src/index.ts` declares `POST /api/auth/login` 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/auth/logout
`server/src/index.ts` declares `POST /api/auth/logout` 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/auth/register
`dogfood/setup.ts` declares `POST /api/auth/register` 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/mcp-servers/reprobe
`server/src/index.ts` declares `POST /api/mcp-servers/reprobe` 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/mcp-setup/parse
`server/src/index.ts` declares `POST /api/mcp-setup/parse` 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/providers/test
`server/src/index.ts` declares `POST /api/providers/test` 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 /loops
`server/src/api-v1.ts` declares `POST /loops` 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 /loops/:id/choices/:choiceId
`server/src/api-v1.ts` declares `POST /loops/:id/choices/:choiceId` 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 /loops/:id/interrupt
`server/src/api-v1.ts` declares `POST /loops/:id/interrupt` 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 /loops/:id/messages
`server/src/api-v1.ts` declares `POST /loops/:id/messages` 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 /me/tokens
`server/src/api-v1.ts` declares `POST /me/tokens` 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 /api/admin/presets
`server/src/index.ts` declares `PUT /api/admin/presets` 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 /api/admin/profiles/:name
`server/src/index.ts` declares `PUT /api/admin/profiles/:name` 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 /api/serve/config
`server/src/index.ts` declares `PUT /api/serve/config` 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 /api/settings/personal
`server/src/index.ts` declares `PUT /api/settings/personal` 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/src/index.ts` 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: server/src/index.ts (3516 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server/src/loops.ts (2409 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server/src/podman.ts (1398 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server/src/session.ts (1554 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/src/api.ts (2059 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/src/components/dialog/PersonalRepoPanel.tsx (1405 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/src/components/settings/MiseConfigPanel.tsx (1517 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/src/pages/ContextPage.tsx (1300 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/src/pages/SettingsPage.tsx (1123 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/src/useLoopRuntime.tsx (1679 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/b60525ac-5073-488b-b96c-88a6cf0caf4c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b60525ac-5073-488b-b96c-88a6cf0caf4c/

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.