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

QuicksilverSlick/dreamforge-cf

https://github.com/QuicksilverSlick/dreamforge-cf · scanned 2026-06-15 23:44 UTC (2 months, 4 weeks ago)

326 raw signals (0 security + 326 graph)

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

Complete repo analysis

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

JSON
Combined
46.1
/100
Security checks
46
0 findings
System graph
46
100.0% cov · 298 findings
Critical
1
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 1 High 84 Medium 37 Low 105 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 298 Crowd 0 Layer: Frontend 57 Security 10 Cicd 3 Quality 95 Api 133
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 46.1/100 with 100.0% coverage. It contains 2709 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 326 findings — concentrated in api (133), quality (95), frontend (57). Risk profile is high: 3 critical, 84 high, 43 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 226 of 298 actionable findings. 326 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 System graph security Secrets conf 1.00 3 occurrences Possible secret in src/components/auth/login-modal.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 115, 117, 131
src/components/auth/login-modal.tsx:115, 117, 131 (3 hits)
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/auth/api-keys/${keyId} (src/lib/api-client.ts:1091)
`src/lib/api-client.ts:1091` calls `DELETE /api/auth/api-keys/${keyId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/api-keys/<p>` 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/auth/sessions/${sessionId} (src/lib/api-client.ts:1042)
`src/lib/api-client.ts:1042` calls `DELETE /api/auth/sessions/${sessionId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/sessions/<p>` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/model-configs/${agentAction} (src/lib/api-client.ts:709)
`src/lib/api-client.ts:709` calls `DELETE /api/model-configs/${agentAction}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-configs/<p>` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/secrets/${secretId} (src/lib/api-client.ts:949)
`src/lib/api-client.ts:949` calls `DELETE /api/secrets/${secretId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/secrets/<p>` 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: GET /api/apps (src/lib/api-client.ts:437)
`src/lib/api-client.ts:437` calls `GET /api/apps` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps` 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/apps/${appId} (src/lib/api-client.ts:531)
`src/lib/api-client.ts:531` calls `GET /api/apps/${appId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/<p>` 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/apps/favorites (src/lib/api-client.ts:451)
`src/lib/api-client.ts:451` calls `GET /api/apps/favorites` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/favorites` 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/apps/recent (src/lib/api-client.ts:444)
`src/lib/api-client.ts:444` calls `GET /api/apps/recent` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/recent` 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/auth/providers (src/lib/api-client.ts:1306)
`src/lib/api-client.ts:1306` calls `GET /api/auth/providers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/providers` 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/auth/sessions (src/lib/api-client.ts:1033)
`src/lib/api-client.ts:1033` calls `GET /api/auth/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/sessions` 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/data (worker/agents/operations/PhaseImplementation.ts:199)
`worker/agents/operations/PhaseImplementation.ts:199` calls `GET /api/data` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/data` 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/interview/${sessionId} (src/lib/api-client.ts:889)
`src/lib/api-client.ts:889` calls `GET /api/interview/${sessionId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/interview/<p>` 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/model-configs (src/lib/api-client.ts:682)
`src/lib/api-client.ts:682` calls `GET /api/model-configs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-configs` 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/secrets (src/lib/api-client.ts:923)
`src/lib/api-client.ts:923` calls `GET /api/secrets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/secrets` 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/stats/user (src/lib/api-client.ts:634)
`src/lib/api-client.ts:634` calls `GET /api/stats/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/stats/user` 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 http://127.0.0.1:${port}/ (container/process-monitor.ts:1229)
`container/process-monitor.ts:1229` calls `GET http://127.0.0.1:${port}/` 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>` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://analyzer/state (worker/api/controllers/byop/controller.ts:438)
`worker/api/controllers/byop/controller.ts:438` calls `GET http://analyzer/state` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/analyzer/state` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://analyzer/state (worker/api/controllers/byop/controller.ts:474)
`worker/api/controllers/byop/controller.ts:474` calls `GET http://analyzer/state` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/analyzer/state` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://analyzer/state (worker/api/controllers/byop/controller.ts:679)
`worker/api/controllers/byop/controller.ts:679` calls `GET http://analyzer/state` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/analyzer/state` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/analysis/${analysisId}/blueprint (tests/e2e/byop-happy-path.test.ts:189)
`tests/e2e/byop-happy-path.test.ts:189` calls `GET http://example.com/api/byop/analysis/${analysisId}/blueprint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/analysis/<p>/blueprint` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/analysis/${analysisId}/blueprint (tests/integration/controllers/BYOPController.test.ts:401)
`tests/integration/controllers/BYOPController.test.ts:401` calls `GET http://example.com/api/byop/analysis/${analysisId}/blueprint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/analysis/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/analysis/${analysisId}/blueprint (tests/integration/controllers/BYOPController.test.ts:420)
`tests/integration/controllers/BYOPController.test.ts:420` calls `GET http://example.com/api/byop/analysis/${analysisId}/blueprint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/analysis/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/analysis/${analysisId}/blueprint (tests/integration/controllers/BYOPController.test.ts:439)
`tests/integration/controllers/BYOPController.test.ts:439` calls `GET http://example.com/api/byop/analysis/${analysisId}/blueprint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/analysis/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/analysis/${analysisId}/blueprint (tests/integration/controllers/BYOPController.test.ts:465)
`tests/integration/controllers/BYOPController.test.ts:465` calls `GET http://example.com/api/byop/analysis/${analysisId}/blueprint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/analysis/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/analysis/${analysisId}/status (tests/e2e/byop-happy-path.test.ts:160)
`tests/e2e/byop-happy-path.test.ts:160` calls `GET http://example.com/api/byop/analysis/${analysisId}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/analysis/<p>/status` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/analysis/${analysisId}/status (tests/integration/controllers/BYOPController.test.ts:343)
`tests/integration/controllers/BYOPController.test.ts:343` calls `GET http://example.com/api/byop/analysis/${analysisId}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/analysis/<p>…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/analysis/${firstData.analysisId}/blueprint (tests/e2e/byop-happy-path.test.ts:282)
`tests/e2e/byop-happy-path.test.ts:282` calls `GET http://example.com/api/byop/analysis/${firstData.analysisId}/blueprint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/analysis/<p>/bluep…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/analysis/invalid-id/status (tests/integration/controllers/BYOPController.test.ts:366)
`tests/integration/controllers/BYOPController.test.ts:366` calls `GET http://example.com/api/byop/analysis/invalid-id/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/analysis/invali…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/analysis/some-id/status (tests/integration/controllers/BYOPController.test.ts:380)
`tests/integration/controllers/BYOPController.test.ts:380` calls `GET http://example.com/api/byop/analysis/some-id/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/analysis/some-id/s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/repositories (tests/e2e/byop-happy-path.test.ts:63)
`tests/e2e/byop-happy-path.test.ts:63` calls `GET http://example.com/api/byop/repositories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/repositories` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/repositories (tests/integration/controllers/BYOPController.test.ts:114)
`tests/integration/controllers/BYOPController.test.ts:114` calls `GET http://example.com/api/byop/repositories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/repositories` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/repositories (tests/integration/controllers/BYOPController.test.ts:130)
`tests/integration/controllers/BYOPController.test.ts:130` calls `GET http://example.com/api/byop/repositories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/repositories` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/repositories (tests/integration/controllers/BYOPController.test.ts:35)
`tests/integration/controllers/BYOPController.test.ts:35` calls `GET http://example.com/api/byop/repositories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/repositories` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/repositories (tests/integration/controllers/BYOPController.test.ts:57)
`tests/integration/controllers/BYOPController.test.ts:57` calls `GET http://example.com/api/byop/repositories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/repositories` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/repositories (tests/integration/controllers/BYOPController.test.ts:73)
`tests/integration/controllers/BYOPController.test.ts:73` calls `GET http://example.com/api/byop/repositories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/repositories` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com/api/byop/repositories (tests/integration/controllers/BYOPController.test.ts:96)
`tests/integration/controllers/BYOPController.test.ts:96` calls `GET http://example.com/api/byop/repositories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/repositories` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4/accounts (worker/services/cloudflare/CloudflareAccountService.ts:65)
`worker/services/cloudflare/CloudflareAccountService.ts:65` calls `GET https://api.cloudflare.com/client/v4/accounts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/accounts` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4/accounts/${accountId}/ai-gateway-billing/credit_balance (worker/services/cloudflare/CloudflareAccountService.ts:209)
`worker/services/cloudflare/CloudflareAccountService.ts:209` calls `GET https://api.cloudflare.com/client/v4/accounts/${accountId}/ai-gateway-billing/credit_balance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4/accounts/${accountId}/ai-gateway/gateways (worker/services/cloudflare/CloudflareAccountService.ts:103)
`worker/services/cloudflare/CloudflareAccountService.ts:103` calls `GET https://api.cloudflare.com/client/v4/accounts/${accountId}/ai-gateway/gateways` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloud…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4/accounts/${this.config.accountId}/ai-gateway/gateways (scripts/setup.ts:992)
`scripts/setup.ts:992` calls `GET https://api.cloudflare.com/client/v4/accounts/${this.config.accountId}/ai-gateway/gateways` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/accoun…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4/accounts/${this.config.accountId}/r2/buckets/${bucketName} (scripts/setup.ts:803)
`scripts/setup.ts:803` calls `GET https://api.cloudflare.com/client/v4/accounts/${this.config.accountId}/r2/buckets/${bucketName}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4/accounts/${this.config.accountId}/storage/kv/namespaces (scripts/setup.ts:669)
`scripts/setup.ts:669` calls `GET https://api.cloudflare.com/client/v4/accounts/${this.config.accountId}/storage/kv/namespaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/acco…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4/user/tokens/permission_groups?name=AI%20Gateway (scripts/setup.ts:971)
`scripts/setup.ts:971` calls `GET https://api.cloudflare.com/client/v4/user/tokens/permission_groups?name=AI%20Gateway` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/user/tokens/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4/user/tokens/verify (scripts/deploy.ts:424)
`scripts/deploy.ts:424` calls `GET https://api.cloudflare.com/client/v4/user/tokens/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/user/tokens/verify` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4/user/tokens/verify (scripts/setup.ts:950)
`scripts/setup.ts:950` calls `GET https://api.cloudflare.com/client/v4/user/tokens/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/user/tokens/verify` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4/zones?name=${encodeURIComponent(zoneName)} (scripts/deploy.ts:856)
`scripts/deploy.ts:856` calls `GET https://api.cloudflare.com/client/v4/zones?name=${encodeURIComponent(zoneName)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/zones` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/user (worker/api/controllers/byop/controller.ts:190)
`worker/api/controllers/byop/controller.ts:190` calls `GET https://api.github.com/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/user` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/secrets/${secretId}/toggle (src/lib/api-client.ts:960)
`src/lib/api-client.ts:960` calls `PATCH /api/secrets/${secretId}/toggle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/secrets/<p>/toggle` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/apps (src/lib/api-client.ts:481)
`src/lib/api-client.ts:481` calls `POST /api/apps` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps` 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/apps/${appId}/favorite (src/lib/api-client.ts:493)
`src/lib/api-client.ts:493` calls `POST /api/apps/${appId}/favorite` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/<p>/favorite` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/apps/${appId}/fork (src/lib/api-client.ts:550)
`src/lib/api-client.ts:550` calls `POST /api/apps/${appId}/fork` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/<p>/fork` 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/apps/${appId}/star (src/lib/api-client.ts:540)
`src/lib/api-client.ts:540` calls `POST /api/apps/${appId}/star` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/<p>/star` 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/auth/api-keys (src/lib/api-client.ts:1074)
`src/lib/api-client.ts:1074` calls `POST /api/auth/api-keys` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/api-keys` 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: POST /api/auth/login (src/lib/api-client.ts:1231)
`src/lib/api-client.ts:1231` calls `POST /api/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` 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/auth/register (src/lib/api-client.ts:1245)
`src/lib/api-client.ts:1245` calls `POST /api/auth/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/register` 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: POST /api/auth/resend-verification (src/lib/api-client.ts:1270)
`src/lib/api-client.ts:1270` calls `POST /api/auth/resend-verification` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/resend-verification` 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/auth/verify-email (src/lib/api-client.ts:1258)
`src/lib/api-client.ts:1258` calls `POST /api/auth/verify-email` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/verify-email` 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: POST /api/byop/analysis/${analysisId}/start-building (src/lib/api-client.ts:1157)
`src/lib/api-client.ts:1157` calls `POST /api/byop/analysis/${analysisId}/start-building` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/byop/analysis/<p>/start-building` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/interview (src/lib/api-client.ts:879)
`src/lib/api-client.ts:879` calls `POST /api/interview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/interview` 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/interview/${sessionId}/answer (src/lib/api-client.ts:900)
`src/lib/api-client.ts:900` calls `POST /api/interview/${sessionId}/answer` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/interview/<p>/answer` 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/interview/${sessionId}/finish (src/lib/api-client.ts:910)
`src/lib/api-client.ts:910` calls `POST /api/interview/${sessionId}/finish` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/interview/<p>/finish` 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/model-configs/reset-all (src/lib/api-client.ts:775)
`src/lib/api-client.ts:775` calls `POST /api/model-configs/reset-all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/model-configs/reset-all` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/secrets (src/lib/api-client.ts:937)
`src/lib/api-client.ts:937` calls `POST /api/secrets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/secrets` 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 http://analyzer/start (worker/api/controllers/byop/controller.ts:366)
`worker/api/controllers/byop/controller.ts:366` calls `POST http://analyzer/start` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/analyzer/start` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/e2e/byop-happy-path.test.ts:256)
`tests/e2e/byop-happy-path.test.ts:256` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/e2e/byop-happy-path.test.ts:297)
`tests/e2e/byop-happy-path.test.ts:297` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/e2e/byop-happy-path.test.ts:88)
`tests/e2e/byop-happy-path.test.ts:88` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/integration/controllers/BYOPController.test.ts:149)
`tests/integration/controllers/BYOPController.test.ts:149` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/integration/controllers/BYOPController.test.ts:193)
`tests/integration/controllers/BYOPController.test.ts:193` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/integration/controllers/BYOPController.test.ts:219)
`tests/integration/controllers/BYOPController.test.ts:219` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/integration/controllers/BYOPController.test.ts:239)
`tests/integration/controllers/BYOPController.test.ts:239` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/integration/controllers/BYOPController.test.ts:257)
`tests/integration/controllers/BYOPController.test.ts:257` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/integration/controllers/BYOPController.test.ts:280)
`tests/integration/controllers/BYOPController.test.ts:280` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/integration/controllers/BYOPController.test.ts:300)
`tests/integration/controllers/BYOPController.test.ts:300` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://example.com/api/byop/import (tests/integration/controllers/BYOPController.test.ts:327)
`tests/integration/controllers/BYOPController.test.ts:327` calls `POST http://example.com/api/byop/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com/api/byop/import` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.cloudflare.com/client/v4/accounts/${accountId}/ai-gateway/gateways (worker/services/cloudflare/CloudflareAccountService.ts:147)
`worker/services/cloudflare/CloudflareAccountService.ts:147` calls `POST https://api.cloudflare.com/client/v4/accounts/${accountId}/ai-gateway/gateways` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.clou…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.cloudflare.com/client/v4/accounts/${this.config.accountId}/r2/buckets (scripts/setup.ts:820)
`scripts/setup.ts:820` calls `POST https://api.cloudflare.com/client/v4/accounts/${this.config.accountId}/r2/buckets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/accounts/<p>/r…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.cloudflare.com/client/v4/accounts/${this.config.accountId}/storage/kv/namespaces (scripts/setup.ts:692)
`scripts/setup.ts:692` calls `POST https://api.cloudflare.com/client/v4/accounts/${this.config.accountId}/storage/kv/namespaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/acc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.cloudflare.com/client/v4/user/tokens (scripts/deploy.ts:482)
`scripts/deploy.ts:482` calls `POST https://api.cloudflare.com/client/v4/user/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/user/tokens` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.cloudflare.com/client/v4/user/tokens (scripts/setup.ts:1038)
`scripts/setup.ts:1038` calls `POST https://api.cloudflare.com/client/v4/user/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/user/tokens` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.github.com/user/repos (worker/services/github/GitHubService.ts:90)
`worker/services/github/GitHubService.ts:90` calls `POST https://api.github.com/user/repos` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/user/repos` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/apps/${appId}/visibility (src/lib/api-client.ts:505)
`src/lib/api-client.ts:505` calls `PUT /api/apps/${appId}/visibility` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/apps/<p>/visibility` 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: PUT /api/auth/profile (src/routes/settings/index.tsx:136)
`src/routes/settings/index.tsx:136` calls `PUT /api/auth/profile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/profile` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in container/bun-sqlite.d.ts:14
Found a known-risky pattern (exec_used). Review and replace if possible.
container/bun-sqlite.d.ts:14 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — container/monitor-cli.test.ts:2492
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 — debug-tools/test-ai-gateway-analytics.ts:563
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/copy-landing-pages.ts:19
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/setup.ts:692
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/routes/chat/mocks/file-mock.ts:223
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 — worker/agents/core/behaviors/base.ts:1772
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 — worker/agents/core/simpleGeneratorAgent.ts:2243
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 — worker/agents/inferutils/imageGeneration.ts:144
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 — worker/agents/prompts.ts:566
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 — worker/api/controllers/agent/controller.ts:286
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 — worker/api/controllers/byop/controller.ts:366
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 — worker/api/controllers/sentry/tunnelController.ts:66
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 — worker/api/routes/byopRoutes.ts:66
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 — worker/app.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 — worker/index.ts:111
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 — worker/services/aigateway-proxy/controller.ts:186
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 — worker/services/deployer/api/cloudflare-api.ts:43
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 — worker/services/migration/cloudflare-compatibility-checker.ts:274
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 — worker/services/oauth/base.ts:99
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 — worker/services/oauth/github.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 — worker/services/sandbox/remoteSandboxService.ts:42
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 — worker/services/sandbox/resourceProvisioner.ts:72
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 — worker/utils/images.ts:112
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 Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
oven-sh/setup-bun@v1 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 7 locations
.github/workflows/ci.yml:30, 60, 87, 114, 148 (5 hits)
.github/workflows/deploy-templates.yml:77
.github/workflows/deploy.yml:46
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/upstream-sync-manual.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in worker/agents/core/codingAgent.ts:800
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
worker/agents/core/codingAgent.ts:800 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in worker/api/controllers/screenshots/controller.ts:172
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
worker/api/controllers/screenshots/controller.ts:172 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in src/lib/api-client.ts:266
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
src/lib/api-client.ts:266 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in container/process-monitor.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
container/process-monitor.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/deploy.ts:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/deploy.ts:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/setup.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/setup.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/undeploy.ts:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/undeploy.ts:21 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 193 placeholder/mock markers across 53 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
32 test file(s) for 469 source file(s) (ratio 0.07). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Maintenance conf 1.00 40 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 777 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 21 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
5 files, 21 locations
.github/workflows/ci.yml:27, 40, 57, 65, 84, 92, 111, 119, +4 more (12 hits)
.github/workflows/deploy-templates.yml:70, 83, 88, 114 (4 hits)
.github/workflows/deploy.yml:43, 55 (2 hits)
.github/workflows/upstream-sync-manual.yml:38, 347 (2 hits)
.github/workflows/upstream-notifications.yml:19
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: debug-tools/ai_request_analyzer_v2.py:analyze, debug-tools/ai_request_analyzer_v2.py:analyze, debug-tools/ai_request_analyzer_v2.py:analyze, debug-tools/ai_request_analyzer_v2.py:analyze This is *the* AI-coder failure mode (4× more duplication in vib…
duplicatesduplication
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: container/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
container/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `ai_request_analyzer_v2` in debug-tools/ai_request_analyzer_v2.py:19
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `stateWithDeprecated` in worker/agents/core/stateMigration.ts:273
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — container/cli-tools.ts:119
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 — container/monitor-cli.test.ts:46
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 — container/process-monitor.ts:418
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 — debug-tools/test-ai-gateway-analytics.ts:662
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/copy-landing-pages.ts:42
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/deploy.ts:123
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/setup.ts:63
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/undeploy.ts:95
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 — src/contexts/limits-context.tsx:72
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 — src/features/app/index.ts:49
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 — src/features/general/index.tsx: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 — src/features/presentation/index.tsx:92
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 — src/hooks/use-byop.ts:88
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 — src/lib/api-client.ts:389
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 — src/routes/chat/components/preview-iframe.tsx:72
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 — src/routes/chat/utils/file-state-helpers.ts:58
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 — src/utils/screenshot.ts:208
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 — tests/e2e/byop-happy-path.test.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 — tests/helpers/websocket-client.ts:40
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 — worker/agents/assistants/realtimeCodeFixer.ts:541
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 — worker/agents/inferutils/core.ts:57
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 — worker/agents/inferutils/infer.ts:139
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 — worker/agents/inferutils/schemaFormatters.ts:725
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 — worker/agents/output-formats/diff-formats/search-replace.test.ts:7
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 — worker/agents/output-formats/diff-formats/udiff.test.ts:52
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 — worker/agents/output-formats/streaming-formats/scof-comprehensive.test.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 — worker/agents/output-formats/streaming-formats/scof.test.ts:32
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 — worker/agents/planning/blueprint.ts:343
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 — worker/agents/prompts.ts:913
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 — worker/agents/services/implementations/FileManager.ts:48
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 — worker/agents/utils/templateCustomizer.ts:106
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 — worker/api/controllers/modelConfig/byokHelper.ts:128
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 — worker/middleware/auth/routeAuth.ts:74
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 — worker/services/aigateway-proxy/controller.ts:11
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 — worker/services/deployer/api/cloudflare-api.ts:188
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 — worker/services/sandbox/factory.ts:8
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 — worker/services/sandbox/sandboxSdkClient.ts:111
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 /:id
`worker/api/routes/appRoutes.ts` declares `DELETE /: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 /api-keys/:keyId
`worker/api/routes/authRoutes.ts` declares `DELETE /api-keys/:keyId` 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/user/providers/:id
`worker/api/routes/modelProviderRoutes.ts` declares `DELETE /api/user/providers/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /sessions/:sessionId
`worker/api/routes/authRoutes.ts` declares `DELETE /sessions/:sessionId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`worker/api/routes/statusRoutes.ts` declares `GET /` 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 /:file
`worker/api/routes/imagesRoutes.ts` declares `GET /:file` 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 /:id
`worker/api/routes/appRoutes.ts` declares `GET /: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 /:id/:file
`worker/api/routes/imagesRoutes.ts` declares `GET /:id/:file` 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 /:sessionId
`worker/api/routes/interviewRoutes.ts` declares `GET /:sessionId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /analysis/:analysisId/blueprint
`worker/api/routes/byopRoutes.ts` declares `GET /analysis/:analysisId/blueprint` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /analysis/:analysisId/status
`worker/api/routes/byopRoutes.ts` declares `GET /analysis/:analysisId/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api-keys
`worker/api/routes/authRoutes.ts` declares `GET /api-keys` 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/agent/:agentId/connect
`worker/api/routes/codegenRoutes.ts` declares `GET /api/agent/:agentId/connect` 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/agent/:agentId/preview
`worker/api/routes/codegenRoutes.ts` declares `GET /api/agent/:agentId/preview` 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/agent/:agentId/ws
`worker/api/routes/codegenRoutes.ts` declares `GET /api/agent/:agentId/ws` 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
`worker/api/routes/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/user/apps
`worker/api/routes/userRoutes.ts` declares `GET /api/user/apps` 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/user/providers
`worker/api/routes/modelProviderRoutes.ts` declares `GET /api/user/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/user/providers/:id
`worker/api/routes/modelProviderRoutes.ts` declares `GET /api/user/providers/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /callback/:provider
`worker/api/routes/authRoutes.ts` declares `GET /callback/:provider` 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 /check
`worker/api/routes/authRoutes.ts` declares `GET /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 /csrf-token
`worker/api/routes/authRoutes.ts` declares `GET /csrf-token` 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 /favorites
`worker/api/routes/appRoutes.ts` declares `GET /favorites` 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 /oauth/:provider
`worker/api/routes/authRoutes.ts` declares `GET /oauth/:provider` 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 /profile
`worker/api/routes/authRoutes.ts` declares `GET /profile` 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 /providers
`worker/api/routes/authRoutes.ts` declares `GET /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 /public
`worker/api/routes/appRoutes.ts` declares `GET /public` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /recent
`worker/api/routes/appRoutes.ts` declares `GET /recent` 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 /repositories
`worker/api/routes/byopRoutes.ts` declares `GET /repositories` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /sessions
`worker/api/routes/authRoutes.ts` declares `GET /sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`worker/api/routes/interviewRoutes.ts` declares `POST /` 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 /:id/favorite
`worker/api/routes/appRoutes.ts` declares `POST /:id/favorite` 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 /:id/fork
`worker/api/routes/appRoutes.ts` declares `POST /:id/fork` 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 /:id/star
`worker/api/routes/appRoutes.ts` declares `POST /:id/star` 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 /:sessionId/answer
`worker/api/routes/interviewRoutes.ts` declares `POST /:sessionId/answer` 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 /:sessionId/finish
`worker/api/routes/interviewRoutes.ts` declares `POST /:sessionId/finish` 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-keys
`worker/api/routes/authRoutes.ts` declares `POST /api-keys` 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/agent
`worker/api/routes/codegenRoutes.ts` declares `POST /api/agent` 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/user/providers
`worker/api/routes/modelProviderRoutes.ts` declares `POST /api/user/providers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/user/providers/test
`worker/api/routes/modelProviderRoutes.ts` declares `POST /api/user/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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import
`worker/api/routes/byopRoutes.ts` declares `POST /import` 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 /login
`worker/api/routes/authRoutes.ts` declares `POST /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 /logout
`worker/api/routes/authRoutes.ts` declares `POST /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 /register
`worker/api/routes/authRoutes.ts` declares `POST /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 /resend-verification
`worker/api/routes/authRoutes.ts` declares `POST /resend-verification` 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 /tunnel
`worker/api/routes/sentryRoutes.ts` declares `POST /tunnel` 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 /verify-email
`worker/api/routes/authRoutes.ts` declares `POST /verify-email` 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 /:id/visibility
`worker/api/routes/appRoutes.ts` declares `PUT /:id/visibility` 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 /profile
`worker/api/routes/authRoutes.ts` declares `PUT /profile` 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/*
`worker/app.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: container/monitor-cli.test.ts (3052 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/deploy.ts (2131 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/setup.ts (2121 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/routes/chat/components/debug-panel.tsx (1099 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/routes/settings/index.tsx (1834 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: worker/agents/core/behaviors/base.ts (2398 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: worker/agents/core/simpleGeneratorAgent.ts (2863 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: worker/agents/inferutils/schemaFormatters.ts (1311 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: worker/agents/prompts.ts (1502 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: worker/services/sandbox/sandboxSdkClient.ts (2919 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/263e1353-c9aa-48e8-bddb-828857048102/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/263e1353-c9aa-48e8-bddb-828857048102/

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.