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

SinishaDjukic/worca-cc

https://github.com/SinishaDjukic/worca-cc · scanned 2026-06-16 00:14 UTC (2 months, 2 weeks ago)

555 raw signals (0 security + 555 graph)

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

Complete repo analysis

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

JSON
Combined
52.5
/100
Security checks
53
0 findings
System graph
53
100.0% cov · 506 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 130 Medium 129 Low 125 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 506 Crowd 0 Layer: Software 7 Frontend 13 Security 32 Cicd 5 Quality 270 Api 179
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 52.5/100 with 100.0% coverage. It contains 14028 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 555 findings — concentrated in quality (286), api (179), security (32). Risk profile is high: 0 critical, 130 high, 129 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 374 of 506 actionable findings. 555 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/fleet-runs/${fleetId} (worca-ui/app/main.js:3553)
`worca-ui/app/main.js:3553` calls `DELETE /api/fleet-runs/${fleetId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fleet-runs/<p>` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/fleet-runs/${fleetId}?cleanup=1&force=1 (worca-ui/app/main.js:3645)
`worca-ui/app/main.js:3645` calls `DELETE /api/fleet-runs/${fleetId}?cleanup=1&force=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fleet-runs/<p>` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/projects/${projectName} (worca-ui/app/views/settings.js:3175)
`worca-ui/app/views/settings.js:3175` calls `DELETE /api/projects/${projectName}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/<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: DELETE /api/workspace-runs/${id} (worca-ui/e2e/workspaces.spec.js:578)
`worca-ui/e2e/workspaces.spec.js:578` calls `DELETE /api/workspace-runs/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/workspaces/${encodeURIComponent(name)} (worca-ui/app/main.js:3791)
`worca-ui/app/main.js:3791` calls `DELETE /api/workspaces/${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces/<p>` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/fleet-runs/${route.runId} (worca-ui/app/main.js:5607)
`worca-ui/app/main.js:5607` calls `GET /api/fleet-runs/${route.runId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fleet-runs/<p>` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/preferences (worca-ui/app/main.js:6153)
`worca-ui/app/main.js:6153` calls `GET /api/preferences` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/preferences` 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/projects (worca-ui/app/main.js:1503)
`worca-ui/app/main.js:1503` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` 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/projects (worca-ui/app/main.js:5814)
`worca-ui/app/main.js:5814` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` 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/projects (worca-ui/app/main.js:5824)
`worca-ui/app/main.js:5824` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` 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/projects (worca-ui/app/main.js:5833)
`worca-ui/app/main.js:5833` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` 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/projects (worca-ui/app/main.js:6028)
`worca-ui/app/main.js:6028` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` 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/projects (worca-ui/app/main.js:6116)
`worca-ui/app/main.js:6116` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` 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/projects/${name}/worktrees (worca-ui/app/main.js:1576)
`worca-ui/app/main.js:1576` calls `GET /api/projects/${name}/worktrees` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/<p>/worktrees` 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 /api/projects/${p.name}/runs (worca-ui/app/main.js:1531)
`worca-ui/app/main.js:1531` calls `GET /api/projects/${p.name}/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/<p>/runs` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.name}/worca-status (worca-ui/app/views/add-project-dialog.js:553)
`worca-ui/app/views/add-project-dialog.js:553` calls `GET /api/projects/${p.name}/worca-status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/<p>/worca-status` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${projectName}/runs (worca-ui/app/main-default-branch.test.js:169)
`worca-ui/app/main-default-branch.test.js:169` calls `GET /api/projects/${projectName}/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/<p>/runs` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${projectName}/worktrees (worca-ui/app/main-default-branch.test.js:210)
`worca-ui/app/main-default-branch.test.js:210` calls `GET /api/projects/${projectName}/worktrees` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/<p>/worktrees` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/status/runs-count (worca-ui/app/main.js:6156)
`worca-ui/app/main.js:6156` calls `GET /api/status/runs-count` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/status/runs-count` 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/status/runs-count (worca-ui/app/main.js:6193)
`worca-ui/app/main.js:6193` calls `GET /api/status/runs-count` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/status/runs-count` 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/templates/project/effort-mode (worca-ui/e2e/pipelines-templates.spec.js:871)
`worca-ui/e2e/pipelines-templates.spec.js:871` calls `GET /api/templates/project/effort-mode` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/templates/project/effort-mode` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/templates/project/gov-strike (worca-ui/e2e/pipelines-templates.spec.js:923)
`worca-ui/e2e/pipelines-templates.spec.js:923` calls `GET /api/templates/project/gov-strike` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/templates/project/gov-strike` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workspace-runs/${encodeURIComponent(id)}/plan (worca-ui/app/views/workspace-detail.js:324)
`worca-ui/app/views/workspace-detail.js:324` calls `GET /api/workspace-runs/${encodeURIComponent(id)}/plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>/plan` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workspace-runs/${encodeURIComponent(ws.workspace_id)}/guide (worca-ui/app/views/workspace-detail.js:607)
`worca-ui/app/views/workspace-detail.js:607` calls `GET /api/workspace-runs/${encodeURIComponent(ws.workspace_id)}/guide` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>/guide` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workspace-runs/${id} (worca-ui/e2e/workspaces.spec.js:1140)
`worca-ui/e2e/workspaces.spec.js:1140` calls `GET /api/workspace-runs/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workspace-runs/${id} (worca-ui/e2e/workspaces.spec.js:470)
`worca-ui/e2e/workspaces.spec.js:470` calls `GET /api/workspace-runs/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<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 /api/workspace-runs/${id} (worca-ui/e2e/workspaces.spec.js:723)
`worca-ui/e2e/workspaces.spec.js:723` calls `GET /api/workspace-runs/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<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 /api/workspace-runs/${id}/context/web (worca-ui/e2e/workspaces.spec.js:1062)
`worca-ui/e2e/workspaces.spec.js:1062` calls `GET /api/workspace-runs/${id}/context/web` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>/context/web` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workspace-runs/${route.runId} (worca-ui/app/main.js:5714)
`worca-ui/app/main.js:5714` calls `GET /api/workspace-runs/${route.runId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workspace-runs/${wsId} (worca-ui/e2e/workspaces.spec.js:386)
`worca-ui/e2e/workspaces.spec.js:386` calls `GET /api/workspace-runs/${wsId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workspace-runs/${wsId} (worca-ui/e2e/workspaces.spec.js:828)
`worca-ui/e2e/workspaces.spec.js:828` calls `GET /api/workspace-runs/${wsId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workspace-runs/${wsId}/guide (worca-ui/e2e/workspaces.spec.js:405)
`worca-ui/e2e/workspaces.spec.js:405` calls `GET /api/workspace-runs/${wsId}/guide` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>/guide` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workspaces (worca-ui/app/main.js:1495)
`worca-ui/app/main.js:1495` calls `GET /api/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces` 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/workspaces (worca-ui/app/main.js:3768)
`worca-ui/app/main.js:3768` calls `GET /api/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces` 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/workspaces (worca-ui/e2e/workspaces.spec.js:253)
`worca-ui/e2e/workspaces.spec.js:253` calls `GET /api/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces` 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/workspaces (worca-ui/e2e/workspaces.spec.js:307)
`worca-ui/e2e/workspaces.spec.js:307` calls `GET /api/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces` 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/workspaces/${encodeURIComponent(name)} (worca-ui/app/views/workspace-edit.js:106)
`worca-ui/app/views/workspace-edit.js:106` calls `GET /api/workspaces/${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces/<p>` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workspaces/edit-ws (worca-ui/e2e/workspaces.spec.js:776)
`worca-ui/e2e/workspaces.spec.js:776` calls `GET /api/workspaces/edit-ws` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces/edit-ws` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${path} (worca-ui/server/project-routes-beads-enrichment.test.js:60)
`worca-ui/server/project-routes-beads-enrichment.test.js:60` calls `GET http://127.0.0.1:${port}${path}` 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>/<p>` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${path} (worca-ui/server/templates-routes.test.js:83)
`worca-ui/server/templates-routes.test.js:83` calls `GET http://127.0.0.1:${port}${path}` 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>/<p>` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/ (worca-ui/test/server-e2e.test.js:103)
`worca-ui/test/server-e2e.test.js:103` 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 m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/ (worca-ui/test/server-e2e.test.js:137)
`worca-ui/test/server-e2e.test.js:137` 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 m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/costs (worca-ui/server/test/costs-api.test.js:155)
`worca-ui/server/test/costs-api.test.js:155` calls `GET http://127.0.0.1:${port}/api/costs` 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/costs` 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:${port}/api/costs (worca-ui/server/test/costs-api.test.js:168)
`worca-ui/server/test/costs-api.test.js:168` calls `GET http://127.0.0.1:${port}/api/costs` 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/costs` 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:${port}/api/costs (worca-ui/server/test/costs-api.test.js:181)
`worca-ui/server/test/costs-api.test.js:181` calls `GET http://127.0.0.1:${port}/api/costs` 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/costs` 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:${port}/api/costs (worca-ui/server/test/costs-api.test.js:208)
`worca-ui/server/test/costs-api.test.js:208` calls `GET http://127.0.0.1:${port}/api/costs` 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/costs` 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:${port}/api/costs (worca-ui/server/test/costs-api.test.js:233)
`worca-ui/server/test/costs-api.test.js:233` calls `GET http://127.0.0.1:${port}/api/costs` 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/costs` 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:${port}/api/costs (worca-ui/server/test/costs-api.test.js:260)
`worca-ui/server/test/costs-api.test.js:260` calls `GET http://127.0.0.1:${port}/api/costs` 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/costs` 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:${port}/api/costs (worca-ui/server/test/costs-api.test.js:284)
`worca-ui/server/test/costs-api.test.js:284` calls `GET http://127.0.0.1:${port}/api/costs` 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/costs` 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:${port}/api/costs (worca-ui/server/test/costs-api.test.js:64)
`worca-ui/server/test/costs-api.test.js:64` calls `GET http://127.0.0.1:${port}/api/costs` 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/costs` 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:${port}/api/costs (worca-ui/server/test/costs-api.test.js:90)
`worca-ui/server/test/costs-api.test.js:90` calls `GET http://127.0.0.1:${port}/api/costs` 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/costs` 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:${port}/api/status/runs-count (worca-ui/server/status-routes.test.js:111)
`worca-ui/server/status-routes.test.js:111` calls `GET http://127.0.0.1:${port}/api/status/runs-count` 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/status/runs-count` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/some/unknown/path (worca-ui/test/server-e2e.test.js:115)
`worca-ui/test/server-e2e.test.js:115` calls `GET http://127.0.0.1:${port}/some/unknown/path` 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>/some/unknown/path` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/styles.css (worca-ui/test/server-e2e.test.js:109)
`worca-ui/test/server-e2e.test.js:109` calls `GET http://127.0.0.1:${port}/styles.css` 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>/styles.css` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/integrations/status (worca-ui/server/app-integrations-status.test.js:22)
`worca-ui/server/app-integrations-status.test.js:22` calls `GET http://localhost:${port}/api/integrations/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/integrations/status` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/integrations/status (worca-ui/server/app-integrations-status.test.js:53)
`worca-ui/server/app-integrations-status.test.js:53` calls `GET http://localhost:${port}/api/integrations/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/integrations/status` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/integrations/status (worca-ui/server/app-integrations-status.test.js:69)
`worca-ui/server/app-integrations-status.test.js:69` calls `GET http://localhost:${port}/api/integrations/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/integrations/status` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/skills (worca-ui/server/app-tools-skills.test.js:71)
`worca-ui/server/app-tools-skills.test.js:71` calls `GET http://localhost:${port}/api/skills` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/skills` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/skills (worca-ui/server/app-tools-skills.test.js:80)
`worca-ui/server/app-tools-skills.test.js:80` calls `GET http://localhost:${port}/api/skills` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/skills` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/skills (worca-ui/server/app-tools-skills.test.js:89)
`worca-ui/server/app-tools-skills.test.js:89` calls `GET http://localhost:${port}/api/skills` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/skills` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/skills (worca-ui/server/app-tools-skills.test.js:98)
`worca-ui/server/app-tools-skills.test.js:98` calls `GET http://localhost:${port}/api/skills` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/skills` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/subagents (worca-ui/server/test/subagents-api.test.js:115)
`worca-ui/server/test/subagents-api.test.js:115` calls `GET http://localhost:${port}/api/subagents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/subagents` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/subagents (worca-ui/server/test/subagents-api.test.js:135)
`worca-ui/server/test/subagents-api.test.js:135` calls `GET http://localhost:${port}/api/subagents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/subagents` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/subagents (worca-ui/server/test/subagents-api.test.js:53)
`worca-ui/server/test/subagents-api.test.js:53` calls `GET http://localhost:${port}/api/subagents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/subagents` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/subagents (worca-ui/server/test/subagents-api.test.js:72)
`worca-ui/server/test/subagents-api.test.js:72` calls `GET http://localhost:${port}/api/subagents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/subagents` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/subagents (worca-ui/server/test/subagents-api.test.js:91)
`worca-ui/server/test/subagents-api.test.js:91` calls `GET http://localhost:${port}/api/subagents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/subagents` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/tools (worca-ui/server/app-tools-skills.test.js:28)
`worca-ui/server/app-tools-skills.test.js:28` calls `GET http://localhost:${port}/api/tools` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/tools` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/tools (worca-ui/server/app-tools-skills.test.js:37)
`worca-ui/server/app-tools-skills.test.js:37` calls `GET http://localhost:${port}/api/tools` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/tools` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/tools (worca-ui/server/app-tools-skills.test.js:51)
`worca-ui/server/app-tools-skills.test.js:51` calls `GET http://localhost:${port}/api/tools` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/tools` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/tools (worca-ui/server/app-tools-skills.test.js:60)
`worca-ui/server/app-tools-skills.test.js:60` calls `GET http://localhost:${port}/api/tools` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/tools` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.telegram.org/bot${token}/getMe (worca-ui/server/app.js:947)
`worca-ui/server/app.js:947` calls `GET https://api.telegram.org/bot${token}/getMe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/getme` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://pypi.org/pypi/${packageName}/json (worca-ui/server/versions.js:127)
`worca-ui/server/versions.js:127` calls `GET https://pypi.org/pypi/${packageName}/json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/pypi.org/pypi/<p>/json` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/${packageName} (worca-ui/server/versions.js:65)
`worca-ui/server/versions.js:65` calls `GET https://registry.npmjs.org/${packageName}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/registry.npmjs.org/<p>` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/crg/recheck${q} (worca-ui/app/views/project-setup-wizard.js:425)
`worca-ui/app/views/project-setup-wizard.js:425` calls `POST /api/crg/recheck${q}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crg/recheck/<p>` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/fleet-runs/${fleetId}/pause (worca-ui/app/main.js:3583)
`worca-ui/app/main.js:3583` calls `POST /api/fleet-runs/${fleetId}/pause` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fleet-runs/<p>/pause` 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: POST /api/fleet-runs/${fleetId}/resume (worca-ui/app/main.js:3526)
`worca-ui/app/main.js:3526` calls `POST /api/fleet-runs/${fleetId}/resume` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fleet-runs/<p>/resume` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/fleet-runs/${fleetId}/stop (worca-ui/app/main.js:3613)
`worca-ui/app/main.js:3613` calls `POST /api/fleet-runs/${fleetId}/stop` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fleet-runs/<p>/stop` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/fleet-runs/${fleetId}/unarchive (worca-ui/app/main.js:3841)
`worca-ui/app/main.js:3841` calls `POST /api/fleet-runs/${fleetId}/unarchive` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fleet-runs/<p>/unarchive` 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 /api/fleet-runs/validate-base (worca-ui/app/views/fleet-launcher.js:1094)
`worca-ui/app/views/fleet-launcher.js:1094` calls `POST /api/fleet-runs/validate-base` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fleet-runs/validate-base` 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/fleet-runs/validate-base (worca-ui/app/views/fleet-launcher.js:551)
`worca-ui/app/views/fleet-launcher.js:551` calls `POST /api/fleet-runs/validate-base` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fleet-runs/validate-base` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/graphify/recheck${q} (worca-ui/app/views/project-setup-wizard.js:424)
`worca-ui/app/views/project-setup-wizard.js:424` calls `POST /api/graphify/recheck${q}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/graphify/recheck/<p>` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/projects (worca-ui/app/views/add-project-dialog.js:227)
`worca-ui/app/views/add-project-dialog.js:227` calls `POST /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` 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: POST /api/projects/${encodeURIComponent(s.target)}/worca-setup (worca-ui/app/views/project-setup-wizard.js:382)
`worca-ui/app/views/project-setup-wizard.js:382` calls `POST /api/projects/${encodeURIComponent(s.target)}/worca-setup` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/<p>/worca-setup` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/projects/${item.name}/worca-setup (worca-ui/app/views/add-project-dialog.js:624)
`worca-ui/app/views/add-project-dialog.js:624` calls `POST /api/projects/${item.name}/worca-setup` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/<p>/worca-setup` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/projects/${projectName}/worca-setup (worca-ui/app/views/settings.js:3195)
`worca-ui/app/views/settings.js:3195` calls `POST /api/projects/${projectName}/worca-setup` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/<p>/worca-setup` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/projects/batch (worca-ui/app/views/add-project-dialog.js:178)
`worca-ui/app/views/add-project-dialog.js:178` calls `POST /api/projects/batch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/batch` 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: POST /api/workspace-runs/${id}/re-run-integration (worca-ui/e2e/workspaces.spec.js:964)
`worca-ui/e2e/workspaces.spec.js:964` calls `POST /api/workspace-runs/${id}/re-run-integration` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>/re-run-integration` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/workspace-runs/${id}/relaunch (worca-ui/e2e/workspaces.spec.js:1125)
`worca-ui/e2e/workspaces.spec.js:1125` calls `POST /api/workspace-runs/${id}/relaunch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>/relaunch` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/workspace-runs/${id}/resume (worca-ui/e2e/workspaces.spec.js:623)
`worca-ui/e2e/workspaces.spec.js:623` calls `POST /api/workspace-runs/${id}/resume` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>/resume` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/workspace-runs/validate-gh-auth (worca-ui/app/views/fleet-launcher.js:1048)
`worca-ui/app/views/fleet-launcher.js:1048` calls `POST /api/workspace-runs/validate-gh-auth` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/validate-gh-auth` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/workspaces (worca-ui/app/views/workspace-create.js:147)
`worca-ui/app/views/workspace-create.js:147` calls `POST /api/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/workspaces (worca-ui/e2e/workspaces.spec.js:1174)
`worca-ui/e2e/workspaces.spec.js:1174` calls `POST /api/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces` 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: POST /api/workspaces (worca-ui/e2e/workspaces.spec.js:279)
`worca-ui/e2e/workspaces.spec.js:279` calls `POST /api/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces` 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: POST /api/workspaces/scan (worca-ui/app/views/workspace-create.js:229)
`worca-ui/app/views/workspace-create.js:229` calls `POST /api/workspaces/scan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces/scan` 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: POST /api/workspaces/scan (worca-ui/app/views/workspace-edit.js:187)
`worca-ui/app/views/workspace-edit.js:187` calls `POST /api/workspaces/scan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces/scan` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/workspaces/scan (worca-ui/e2e/workspaces.spec.js:262)
`worca-ui/e2e/workspaces.spec.js:262` calls `POST /api/workspaces/scan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces/scan` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}${url} (worca-ui/server/app-integrations-send.test.js:59)
`worca-ui/server/app-integrations-send.test.js:59` calls `POST http://localhost:${port}${url}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/<p>` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/integrations/send (worca-ui/server/app-integrations-send.test.js:157)
`worca-ui/server/app-integrations-send.test.js:157` calls `POST http://localhost:${port}/api/integrations/send` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/integrations/send` If this poin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/integrations/send (worca-ui/server/app-integrations-send.test.js:204)
`worca-ui/server/app-integrations-send.test.js:204` calls `POST http://localhost:${port}/api/integrations/send` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/integrations/send` If this poin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/integrations/send (worca-ui/server/app-integrations-send.test.js:253)
`worca-ui/server/app-integrations-send.test.js:253` calls `POST http://localhost:${port}/api/integrations/send` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/integrations/send` If this poin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/projects/inbox (worca-ui/server/app-webhook-hints.test.js:29)
`worca-ui/server/app-webhook-hints.test.js:29` calls `POST http://localhost:${port}/api/projects/inbox` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/projects/inbox` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/projects/myproj/runs/run-002/pr (worca-ui/server/app.test.js:83)
`worca-ui/server/app.test.js:83` calls `POST http://localhost:${port}/api/projects/myproj/runs/run-002/pr` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/projects/myproj/runs/run-002/pr` If …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/inbox (worca-ui/server/app-inbox-strict.test.js:35)
`worca-ui/server/app-inbox-strict.test.js:35` calls `POST http://localhost:${port}/api/webhooks/inbox` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/inbox (worca-ui/server/app-inbox-strict.test.js:51)
`worca-ui/server/app-inbox-strict.test.js:51` calls `POST http://localhost:${port}/api/webhooks/inbox` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/inbox (worca-ui/server/app-inbox-strict.test.js:67)
`worca-ui/server/app-inbox-strict.test.js:67` calls `POST http://localhost:${port}/api/webhooks/inbox` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/inbox (worca-ui/server/app-inbox-unchanged.test.js:23)
`worca-ui/server/app-inbox-unchanged.test.js:23` calls `POST http://localhost:${port}/api/webhooks/inbox` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/inbox (worca-ui/server/app-inbox-unchanged.test.js:43)
`worca-ui/server/app-inbox-unchanged.test.js:43` calls `POST http://localhost:${port}/api/webhooks/inbox` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/inbox (worca-ui/server/app-inbox-unchanged.test.js:62)
`worca-ui/server/app-inbox-unchanged.test.js:62` calls `POST http://localhost:${port}/api/webhooks/inbox` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/inbox (worca-ui/server/app-inbox-unchanged.test.js:84)
`worca-ui/server/app-inbox-unchanged.test.js:84` calls `POST http://localhost:${port}/api/webhooks/inbox` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/inbox (worca-ui/server/integrations/integrations-pipeline.test.js:166)
`worca-ui/server/integrations/integrations-pipeline.test.js:166` calls `POST http://localhost:${port}/api/webhooks/inbox` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/inbox (worca-ui/server/integrations/integrations-pipeline.test.js:221)
`worca-ui/server/integrations/integrations-pipeline.test.js:221` calls `POST http://localhost:${port}/api/webhooks/inbox` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/test (worca-ui/server/app-webhooks.test.js:112)
`worca-ui/server/app-webhooks.test.js:112` calls `POST http://localhost:${port}/api/webhooks/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/test` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/test (worca-ui/server/app-webhooks.test.js:124)
`worca-ui/server/app-webhooks.test.js:124` calls `POST http://localhost:${port}/api/webhooks/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/test` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/test (worca-ui/server/app-webhooks.test.js:139)
`worca-ui/server/app-webhooks.test.js:139` calls `POST http://localhost:${port}/api/webhooks/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/test` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/test (worca-ui/server/app-webhooks.test.js:148)
`worca-ui/server/app-webhooks.test.js:148` calls `POST http://localhost:${port}/api/webhooks/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/test` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/test (worca-ui/server/app-webhooks.test.js:44)
`worca-ui/server/app-webhooks.test.js:44` calls `POST http://localhost:${port}/api/webhooks/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/test` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/test (worca-ui/server/app-webhooks.test.js:56)
`worca-ui/server/app-webhooks.test.js:56` calls `POST http://localhost:${port}/api/webhooks/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/test` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/test (worca-ui/server/app-webhooks.test.js:67)
`worca-ui/server/app-webhooks.test.js:67` calls `POST http://localhost:${port}/api/webhooks/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/test` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/test (worca-ui/server/app-webhooks.test.js:79)
`worca-ui/server/app-webhooks.test.js:79` calls `POST http://localhost:${port}/api/webhooks/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/test` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/api/webhooks/test (worca-ui/server/app-webhooks.test.js:92)
`worca-ui/server/app-webhooks.test.js:92` calls `POST http://localhost:${port}/api/webhooks/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/test` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/preferences (worca-ui/app/views/settings.js:816)
`worca-ui/app/views/settings.js:816` calls `PUT /api/preferences` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/preferences` 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: PUT /api/workspace-runs/${id}/plan (worca-ui/e2e/workspaces.spec.js:602)
`worca-ui/e2e/workspaces.spec.js:602` calls `PUT /api/workspace-runs/${id}/plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspace-runs/<p>/plan` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/workspaces/${encodeURIComponent(workspaceName)} (worca-ui/app/views/workspace-edit.js:263)
`worca-ui/app/views/workspace-edit.js:263` calls `PUT /api/workspaces/${encodeURIComponent(workspaceName)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces/<p>` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/workspaces/active-ws (worca-ui/e2e/workspaces.spec.js:1282)
`worca-ui/e2e/workspaces.spec.js:1282` calls `PUT /api/workspaces/active-ws` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces/active-ws` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/workspaces/cycle-edit-ws (worca-ui/e2e/workspaces.spec.js:1211)
`worca-ui/e2e/workspaces.spec.js:1211` calls `PUT /api/workspaces/cycle-edit-ws` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces/cycle-edit-ws` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/workspaces/edit-ws (worca-ui/e2e/workspaces.spec.js:785)
`worca-ui/e2e/workspaces.spec.js:785` calls `PUT /api/workspaces/edit-ws` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workspaces/edit-ws` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT http://localhost:${port}/api/webhooks/inbox/control (worca-ui/server/app-inbox-control-strict.test.js:35)
`worca-ui/server/app-inbox-control-strict.test.js:35` calls `PUT http://localhost:${port}/api/webhooks/inbox/control` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox/control` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT http://localhost:${port}/api/webhooks/inbox/control (worca-ui/server/app-inbox-control-strict.test.js:54)
`worca-ui/server/app-inbox-control-strict.test.js:54` calls `PUT http://localhost:${port}/api/webhooks/inbox/control` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox/control` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT http://localhost:${port}/api/webhooks/inbox/control (worca-ui/server/app-inbox-control-strict.test.js:73)
`worca-ui/server/app-inbox-control-strict.test.js:73` calls `PUT http://localhost:${port}/api/webhooks/inbox/control` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/webhooks/inbox/control` I…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs-site/worker/index.ts:15
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 — videos/scripts/generate-voiceover.ts:201
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 — worca-ui/app/main-default-branch.test.js:169
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 — worca-ui/app/main.js:825
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 — worca-ui/app/views/add-project-dialog-worca-setup.test.js:388
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 — worca-ui/app/views/add-project-dialog.js:56
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 — worca-ui/app/views/fleet-launcher.js:207
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 — worca-ui/app/views/new-run.js: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 — worca-ui/app/views/pipelines-editor.js:736
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 — worca-ui/app/views/pipelines.js: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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worca-ui/app/views/project-setup-wizard.js:424
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 — worca-ui/app/views/workspace-detail.js:607
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 — worca-ui/e2e/graphify-settings.spec.js:176
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 — worca-ui/e2e/pipelines-templates.spec.js:871
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 — worca-ui/e2e/test-fixture-templates.js: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 — worca-ui/e2e/workspaces.spec.js:253
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 — worca-ui/server/app-inbox-control-strict.test.js:35
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 — worca-ui/server/app-inbox-strict.test.js:35
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 — worca-ui/server/app-inbox-unchanged.test.js:23
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 — worca-ui/server/app-integrations-config.test.js:32
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 — worca-ui/server/app-integrations-send.test.js:59
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 — worca-ui/server/app-integrations-status.test.js:22
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 — worca-ui/server/app-tools-skills.test.js:28
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 — worca-ui/server/app-webhook-hints.test.js:29
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 — worca-ui/server/app-webhooks.test.js:44
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 — worca-ui/server/app.js:951
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 — worca-ui/server/app.test.js:39
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 — worca-ui/server/code-review-graph-status.test.js:465
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 — worca-ui/server/fleet-routes-guide-upload.test.js:56
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 — worca-ui/server/fleet-routes.test.js:92
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 — worca-ui/server/graphify-status.test.js:360
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 — worca-ui/server/integrations/integrations-pipeline.test.js:166
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 — worca-ui/server/integrations/rest_client.js:5
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 — worca-ui/server/model-env-routes.test.js:58
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 — worca-ui/server/models-routes.test.js:68
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 — worca-ui/server/preferences-routes.test.js:38
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 — worca-ui/server/project-routes-settings-split.test.js:36
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 — worca-ui/server/project-routes-setup-preflight.test.js:39
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 — worca-ui/server/project-routes-template.test.js: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 — worca-ui/server/project-routes-worktree-control.test.js:37
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 — worca-ui/server/project-routes.test.js:81
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 — worca-ui/server/status-routes.test.js:51
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 — worca-ui/server/test/app-run-control-action.test.js:85
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 — worca-ui/server/test/app-run-controls.test.js:107
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 — worca-ui/server/test/archive-api.test.js:104
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 — worca-ui/server/test/cap-enforcement.test.js:62
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worca-ui/server/test/costs-api.test.js:8
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 — worca-ui/server/test/delete-route-removed.test.js:64
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 — worca-ui/server/test/error-isolation.test.js:30
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 — worca-ui/server/test/learn-api.test.js:68
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 — worca-ui/server/test/max-beads-launch.test.js:50
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 — worca-ui/server/test/multi-pipeline-route-removed.test.js:69
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 — worca-ui/server/test/multi-project-api.test.js:29
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 — worca-ui/server/test/project-routes-cancel.test.js:90
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 — worca-ui/server/test/project-routes-delete.test.js:91
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 — worca-ui/server/test/project-routes-stop-409.test.js:80
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 — worca-ui/server/test/projects-batch.test.js:35
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 — worca-ui/server/test/runs-api.test.js:62
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worca-ui/server/test/scan-directory.test.js: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 — worca-ui/server/test/settings-api.test.js:75
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 — worca-ui/server/test/settings-strip-on-save.test.js:51
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 — worca-ui/server/test/subagents-api.test.js:53
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 — worca-ui/server/test/worca-status.test.js: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 — worca-ui/server/workspace-routes-guide-upload.test.js:124
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 — worca-ui/server/workspace-routes-plan-upload.test.js:161
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 — worca-ui/server/workspace-routes-setup.test.js:86
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 — worca-ui/server/workspace-routes.test.js:146
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 — worca-ui/server/worktrees-routes.test.js:126
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 — worca-ui/test/server-e2e.test.js:11
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 authority lacks a verifier contract: .claude/skills/worca-rc/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/worca-rc/SKILL.md VerificationClaude instruction
medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: .claude/skills/worca-rc/SKILL.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
.claude/skills/worca-rc/SKILL.md:87 Supply chainClaude instruction
medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: .claude/skills/worca-release/SKILL.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
.claude/skills/worca-release/SKILL.md:210 Supply chainClaude instruction
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 GitHub Action is tag-pinned rather than SHA-pinned
pypa/gh-action-pypi-publish@release/v1 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/release-pypi.yml:65 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/release-npm.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/release-pypi.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in worca-ui/app/views/run-timeline.js:238
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
worca-ui/app/views/run-timeline.js:238 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in videos/scripts/generate-posters.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
videos/scripts/generate-posters.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in videos/scripts/render-all.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
videos/scripts/render-all.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/scripts/build-frontend.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/scripts/build-frontend.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/app.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/app.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/bd-daemon.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/bd-daemon.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/beads-reader.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/beads-reader.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/code-review-graph-status.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/code-review-graph-status.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/dispatch-external.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/dispatch-external.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/fleet-routes.js:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/fleet-routes.js:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/git-helpers.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/git-helpers.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/graphify-status.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/graphify-status.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/process-manager.js:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/process-manager.js:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/project-routes.js:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/project-routes.js:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/version-check.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/version-check.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/versions.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/versions.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/worca-setup.js:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/worca-setup.js:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/workspace-routes.js:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/workspace-routes.js:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in worca-ui/server/worktree-ops.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
worca-ui/server/worktree-ops.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in src/worca/orchestrator/events.py:66
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
src/worca/orchestrator/events.py:66 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/coverage.py:109
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/pr_stage_harness.py:48
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/cli/pr.py:186
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/cli/run_pipeline.py:100
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/cli/templates.py:1017
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/hooks/session.py:26
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/hooks/tracking.py:338
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/orchestrator/bundle.py:708
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/orchestrator/fleet_lifecycle.py:228
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/orchestrator/runner.py:2197
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/orchestrator/work_request.py:231
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/scripts/run_fleet.py:68
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/scripts/run_parallel.py:41
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/scripts/run_workspace.py:764
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/scripts/run_worktree.py:414
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/scripts/sync_commit.py:32
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/scripts/sync_pr.py:50
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/utils/beads.py:59
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/utils/gh_pr.py:135
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/utils/git.py:14
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/workspace/dag_executor.py:153
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/workspace/integration_test.py:39
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/worca/workspace/pr_linker.py:49
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 139 placeholder/mock markers across 47 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Maintenance conf 1.00 32 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 597 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 28 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-node@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
4 files, 28 locations
.github/workflows/test.yml:25, 31, 36, 60, 66, 76, 107, 119, +11 more (19 hits)
.github/workflows/release-pypi.yml:19, 46, 59, 76 (4 hits)
.github/workflows/test-e2e.yml:20, 30, 47 (3 hits)
.github/workflows/release-npm.yml:21, 54 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 10 places
Functions with the same first-5-line body hash: src/worca/orchestrator/executor.py:post_dispatch, src/worca/orchestrator/executor.py:post_dispatch, src/worca/orchestrator/executor.py:post_dispatch, src/worca/orchestrator/executor.py:post_dispatch This is *the* AI-coder failure mode (4× more duplic…
duplicatesduplication
low System graph quality Integrity conf 1.00 12 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: src/worca/events/types.py:workspace_plan_loaded_payload, src/worca/events/types.py:workspace_plan_partial_payload This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docume…
12 occurrences
repo-level (12 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: src/worca/cli/cleanup.py:list_eligible, src/worca/cli/cleanup.py:list_eligible, src/worca/cli/cleanup.py:list_eligible This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or d…
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 9 places
Functions with the same first-5-line body hash: src/worca/cli/graphify_cmd.py:cmd_graphify_status, src/worca/cli/graphify_cmd.py:cmd_graphify_recommend, src/worca/cli/graphify_cmd.py:cmd_graphify_update, src/worca/cli/graphify_cmd.py:cmd_graphify_gc This is *the* AI-coder failure mode (4× more dup…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_dispatch_legacy` in src/worca/cli/init.py:246
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 `_dispatch_legacy` in tests/test_denylist_sync.py:140
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 `_dispatch_legacy` in tests/test_init_migration.py:168
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 `_dispatch_legacy` in worca-ui/server/dispatch-migration.js:261
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 `_dispatch_legacy` in worca-ui/server/dispatch-migration.test.js:92
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 `base_copy` in tests/test_settings.py:60
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 `context_copy` in src/worca/orchestrator/prompt_builder.py:215
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 `current_copy` in tests/test_templates.py:330
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 `eleven_multilingual_v2` in videos/scripts/generate-voiceover.ts:50
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 `fake_copy` in tests/test_run_parallel.py:167
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 `posActiveOld` in worca-ui/app/views/beads-panel.test.js:171
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 `redacted_manifest_copy` in src/worca/orchestrator/bundle.py:293
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 `test_cli_present_incompatible_version_too_old` in tests/test_graphify_detect.py:45
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 `test_crg_preflight_builds_and_seeds_run_copy` in tests/integration/test_crg_pipeline.py:110
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 `test_detect_crg_fastmcp_too_old` in tests/test_crg_detect.py:50
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 `test_no_profile_returns_base_copy` in tests/test_graphify_settings.py:343
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 `test_older_than_filter_includes_old` in tests/test_cli_cleanup.py:177
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 `test_restore_loop_counters_returns_copy` in tests/test_iteration_resume.py:139
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 `test_wal_checkpoint_runs_before_copy` in tests/test_crg_preflight.py:181
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 `test_zip_without_models_json_synthesizes_v2` in tests/test_bundle.py:1160
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 software Dead code conf 1.00 Possibly dead Python function: cmd_combine
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/coverage.py:210
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_compare
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/coverage.py:226
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_report
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/coverage.py:214
low System graph software Dead code conf 1.00 Possibly dead Python function: ignore_patterns
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/worca/cli/init.py:841
low System graph software Dead code conf 1.00 7 occurrences Possibly dead Python function: register_subcommand
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
7 files, 7 locations
src/worca/cli/cleanup.py:553
src/worca/cli/crg_cmd.py:200
src/worca/cli/graphify_cmd.py:332
src/worca/cli/models_cmd.py:55
src/worca/cli/pr.py:300
src/worca/cli/templates.py:180
src/worca/cli/workspace.py:139
low System graph software Dead code conf 1.00 Possibly dead Python function: resolve_and_materialize
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/worca/utils/claude_md.py:167
low System graph software Dead code conf 1.00 Possibly dead Python function: workspace_runs_dir
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/worca/utils/paths.py:66
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 — videos/scripts/generate-posters.ts:50
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 — videos/scripts/generate-srt.ts:73
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 — videos/scripts/generate-voiceover.ts:317
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 — videos/scripts/publish-to-docs.ts:55
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 — videos/scripts/render-all.ts:51
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 — worca-ui/app/utils/logging.js: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 — worca-ui/app/views/pipelines-editor.js:1310
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 — worca-ui/e2e/test-fixture-templates.js:16
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 — worca-ui/scripts/build-frontend.js: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 — worca-ui/server/index.js:125
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 — worca-ui/server/test/strip-shebang-plugin.test.js:24
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 — worca-ui/server/ws-message-router.js:697
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 quality Integrity conf 1.00 Stub function `get_env` (body is just `pass`/`return`) — src/worca/hooks/session.py:18
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:id
`worca-ui/server/project-routes.js` 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 /:run_id
`worca-ui/server/worktrees-routes.js` declares `DELETE /:run_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

Showing first 300 of 374. Refine filters or use the findings page for deep search.

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/ca02c81b-f4a8-4740-bdb7-c8fb0fc11eb2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ca02c81b-f4a8-4740-bdb7-c8fb0fc11eb2/

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.