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
128 of your 247 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 62.99s for a 185.3 MB repo slow.
  • Repobility's analysis ran in 67.95s after the clone landed.

openclaw/openclaw

https://github.com/openclaw/openclaw · scanned 2026-06-05 04:24 UTC (10 hours, 42 minutes ago) · 10 languages

5760 findings (222 legacy + 5538 scanner) 11/13 scanners ran 90th percentile · Typescript · huge (>500K LoC) Scanner says 56 (higher by 36)

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

Complete repo analysis

Last scanned 10 hours, 42 minutes ago · v3 · 2068 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
74.1
/100
Repobility
92
222 legacy
9-layer
56
100.0% cov · 1846 gaps
Critical
158
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 95.0 0.20 19.00
documentation_score 100.0 0.15 15.00
practices_score 91.0 0.15 13.65
code_quality 65.0 0.10 6.50
Overall 1.00 91.9
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: layer: api × excluding tests × Reset all
Severity: Critical 158 High 276 Medium 154 Low 1030 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 222 9-layer 1846 Crowd 0 Layer: Software 150 Quality 1106 Security 172 Cicd 290 Frontend 160 Network 5 Hardware 4 Api 181
Scan summary Repository scanned at 55.8/100 with 100.0% coverage. It contains 105972 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 1846 findings — concentrated in quality (1006), cicd (268), api (181). Risk profile is high: 133 critical, 162 high, 122 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 181 of 2068 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high 9-layer api wiring conf 1.00 Dangling fetch: DELETE /anything (extensions/mattermost/src/mattermost/client.test.ts:164)
`extensions/mattermost/src/mattermost/client.test.ts:164` calls `DELETE /anything` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/anything` If this points at an external API, prefix it with `https://` so th…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: DELETE /posts/${postId} (extensions/mattermost/src/mattermost/client.ts:561)
`extensions/mattermost/src/mattermost/client.ts:561` calls `DELETE /posts/${postId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/posts/<p>` If this points at an external API, prefix it with `https://` so…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /api/me (extensions/clickclack/src/http-client.ts:48)
`extensions/clickclack/src/http-client.ts:48` calls `GET /api/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /api/workspaces (extensions/clickclack/src/http-client.ts:52)
`extensions/clickclack/src/http-client.ts:52` calls `GET /api/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/workspaces` If this points at an external API, prefix it with `https://` so the match…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /channels/${channelId} (extensions/mattermost/src/mattermost/client.ts:190)
`extensions/mattermost/src/mattermost/client.ts:190` calls `GET /channels/${channelId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/channels/<p>` If this points at an external API, prefix it with `https:…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /missing (extensions/mattermost/src/mattermost/client.test.ts:152)
`extensions/mattermost/src/mattermost/client.test.ts:152` calls `GET /missing` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/missing` If this points at an external API, prefix it with `https://` so the mat…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /posts/${payload.post_id} (extensions/mattermost/src/mattermost/interactions.ts:511)
`extensions/mattermost/src/mattermost/interactions.ts:511` calls `GET /posts/${payload.post_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/posts/<p>` If this points at an external API, prefix it with `…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /repos/openclaw/openclaw (test/scripts/dependency-guard-script.test.ts:663)
`test/scripts/dependency-guard-script.test.ts:663` calls `GET /repos/openclaw/openclaw` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/repos/openclaw/openclaw` If this points at an external API, prefix it w…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /repos/openclaw/openclaw (test/scripts/dependency-guard-script.test.ts:687)
`test/scripts/dependency-guard-script.test.ts:687` calls `GET /repos/openclaw/openclaw` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/repos/openclaw/openclaw` If this points at an external API, prefix it w…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /repos/openclaw/openclaw (test/scripts/dependency-guard-script.test.ts:721)
`test/scripts/dependency-guard-script.test.ts:721` calls `GET /repos/openclaw/openclaw` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/repos/openclaw/openclaw` If this points at an external API, prefix it w…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /users/${userId} (extensions/mattermost/src/mattermost/client.ts:176)
`extensions/mattermost/src/mattermost/client.ts:176` calls `GET /users/${userId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/<p>` If this points at an external API, prefix it with `https://` so th…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /users/${userId}/teams (extensions/mattermost/src/mattermost/client.ts:533)
`extensions/mattermost/src/mattermost/client.ts:533` calls `GET /users/${userId}/teams` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/<p>/teams` If this points at an external API, prefix it with `htt…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /users/me (extensions/mattermost/src/mattermost/client.test.ts:125)
`extensions/mattermost/src/mattermost/client.test.ts:125` calls `GET /users/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/me` If this points at an external API, prefix it with `https://` so the m…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /users/me (extensions/mattermost/src/mattermost/client.ts:169)
`extensions/mattermost/src/mattermost/client.ts:169` calls `GET /users/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/me` If this points at an external API, prefix it with `https://` so the matche…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /users/me/teams (extensions/mattermost/src/mattermost/directory.ts:139)
`extensions/mattermost/src/mattermost/directory.ts:139` calls `GET /users/me/teams` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/me/teams` If this points at an external API, prefix it with `https://…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET /users/username/${encodeURIComponent(username)} (extensions/mattermost/src/mattermost/client.ts:183)
`extensions/mattermost/src/mattermost/client.ts:183` calls `GET /users/username/${encodeURIComponent(username)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/username/<p>` If this points at an exter…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${enabledPort}${pathname} (src/gateway/models-http.test.ts:31)
`src/gateway/models-http.test.ts:31` calls `GET http://127.0.0.1:${enabledPort}${pathname}` 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 …
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${MOCK_PORT}/health (test/scripts/docker-build-helper.test.ts:2303)
`test/scripts/docker-build-helper.test.ts:2303` calls `GET http://127.0.0.1:${MOCK_PORT}/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/health` If this points at an external API, prefix …
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${mock_port}/health (test/scripts/rtt-harness.test.ts:215)
`test/scripts/rtt-harness.test.ts:215` calls `GET http://127.0.0.1:${mock_port}/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/health` If this points at an external API, prefix it with `…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/ (src/gateway/server.control-ui-root.test.ts:40)
`src/gateway/server.control-ui-root.test.ts:40` 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://`…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/callback?code=code-1&state=state-1 (src/plugin-sdk/provider-auth-runtime.test.ts:116)
`src/plugin-sdk/provider-auth-runtime.test.ts:116` calls `GET http://127.0.0.1:${port}/callback?code=code-1&state=state-1` 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>/callback` If this points…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/callback?code=code-1&state=state-1 (src/plugin-sdk/provider-auth-runtime.test.ts:151)
`src/plugin-sdk/provider-auth-runtime.test.ts:151` calls `GET http://127.0.0.1:${port}/callback?code=code-1&state=state-1` 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>/callback` If this points…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/callback?code=code-1&state=state-1 (src/plugin-sdk/provider-auth-runtime.test.ts:175)
`src/plugin-sdk/provider-auth-runtime.test.ts:175` calls `GET http://127.0.0.1:${port}/callback?code=code-1&state=state-1` 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>/callback` If this points…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/callback?code=code-1&state=state-1 (src/plugin-sdk/provider-auth-runtime.test.ts:76)
`src/plugin-sdk/provider-auth-runtime.test.ts:76` calls `GET http://127.0.0.1:${port}/callback?code=code-1&state=state-1` 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>/callback` If this points …
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/fixture/inbound (test/scripts/e2e-helper-env-limits.test.ts:148)
`test/scripts/e2e-helper-env-limits.test.ts:148` calls `GET http://127.0.0.1:${port}/fixture/inbound` 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>/fixture/inbound` If this points at an externa…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/healthz (extensions/telegram/src/webhook.test.ts:481)
`extensions/telegram/src/webhook.test.ts:481` calls `GET http://127.0.0.1:${port}/healthz` 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>/healthz` If this points at an external API, prefix it wi…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/healthz (extensions/telegram/src/webhook.test.ts:528)
`extensions/telegram/src/webhook.test.ts:528` calls `GET http://127.0.0.1:${port}/healthz` 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>/healthz` If this points at an external API, prefix it wi…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/hook (src/gateway/server-http.request-trace.test.ts:78)
`src/gateway/server-http.request-trace.test.ts:78` calls `GET http://127.0.0.1:${port}/hook` 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>/hook` If this points at an external API, prefix it wit…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/hooks/wake (src/gateway/server.hooks.test.ts:1007)
`src/gateway/server.hooks.test.ts:1007` calls `GET http://127.0.0.1:${port}/hooks/wake` 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>/hooks/wake` If this points at an external API, prefix it wi…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/hooks/wake (src/gateway/server.hooks.test.ts:278)
`src/gateway/server.hooks.test.ts:278` calls `GET http://127.0.0.1:${port}/hooks/wake` 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>/hooks/wake` If this points at an external API, prefix it wit…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/chat/completions (src/gateway/openai-http.test.ts:191)
`src/gateway/openai-http.test.ts:191` calls `GET http://127.0.0.1:${port}/v1/chat/completions` 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>/v1/chat/completions` If this points at an external A…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/models (src/gateway/models-http.test.ts:120)
`src/gateway/models-http.test.ts:120` calls `GET http://127.0.0.1:${port}/v1/models` 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>/v1/models` If this points at an external API, prefix it with `…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/models (src/gateway/models-http.test.ts:138)
`src/gateway/models-http.test.ts:138` calls `GET http://127.0.0.1:${port}/v1/models` 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>/v1/models` If this points at an external API, prefix it with `…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/responses (src/gateway/openresponses-http.test.ts:266)
`src/gateway/openresponses-http.test.ts:266` calls `GET http://127.0.0.1:${port}/v1/responses` 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>/v1/responses` If this points at an external API, pre…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${QA_LAB_INTERNAL_PORT}/healthz (extensions/qa-lab/src/docker-harness.ts:85)
`extensions/qa-lab/src/docker-harness.ts:85` calls `GET http://127.0.0.1:${QA_LAB_INTERNAL_PORT}/healthz` 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>/healthz` If this points at an external AP…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:18789/healthz (extensions/qa-lab/src/docker-harness.test.ts:56)
`extensions/qa-lab/src/docker-harness.test.ts:56` calls `GET http://127.0.0.1:18789/healthz` 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:18789/healthz` If this points at an external API, prefix it…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:18789/healthz (extensions/qa-lab/src/docker-harness.ts:126)
`extensions/qa-lab/src/docker-harness.ts:126` calls `GET http://127.0.0.1:18789/healthz` 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:18789/healthz` If this points at an external API, prefix it wit…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:44080/healthz (extensions/qa-lab/src/docker-harness.ts:58)
`extensions/qa-lab/src/docker-harness.ts:58` calls `GET http://127.0.0.1:44080/healthz` 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:44080/healthz` If this points at an external API, prefix it with…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://api.example.com/data (src/skills/security/scanner.test.ts:312)
`src/skills/security/scanner.test.ts:312` calls `GET https://api.example.com/data` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.example.com/data` If this points at an external API, prefix it with `https…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://api.telegram.org/botTOKEN/getMe (extensions/telegram/src/fetch.test.ts:531)
`extensions/telegram/src/fetch.test.ts:531` calls `GET https://api.telegram.org/botTOKEN/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/bottoken/getme` If this points at an external AP…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://api.telegram.org/botTOKEN/getMe (extensions/telegram/src/fetch.test.ts:562)
`extensions/telegram/src/fetch.test.ts:562` calls `GET https://api.telegram.org/botTOKEN/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/bottoken/getme` If this points at an external AP…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://api.telegram.org/botx/getMe (extensions/telegram/src/fetch.test.ts:1255)
`extensions/telegram/src/fetch.test.ts:1255` calls `GET https://api.telegram.org/botx/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/botx/getme` If this points at an external API, pref…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://auth.example.com/token (src/agents/mcp-http-fetch.test.ts:131)
`src/agents/mcp-http-fetch.test.ts:131` calls `GET https://auth.example.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth.example.com/token` If this points at an external API, prefix it with `htt…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://auth.example.com/token (src/agents/mcp-http-fetch.test.ts:192)
`src/agents/mcp-http-fetch.test.ts:192` calls `GET https://auth.example.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth.example.com/token` If this points at an external API, prefix it with `htt…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://auth.example.com/token (src/agents/mcp-http-fetch.test.ts:99)
`src/agents/mcp-http-fetch.test.ts:99` calls `GET https://auth.example.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/auth.example.com/token` If this points at an external API, prefix it with `http…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/oauth2/applications/@me (extensions/discord/src/monitor/provider.rest-proxy.test.ts:177)
`extensions/discord/src/monitor/provider.rest-proxy.test.ts:177` calls `GET https://discord.com/api/v10/oauth2/applications/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/discord.com/api/v10/oau…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/oauth2/applications/@me (extensions/discord/src/monitor/provider.rest-proxy.test.ts:207)
`extensions/discord/src/monitor/provider.rest-proxy.test.ts:207` calls `GET https://discord.com/api/v10/oauth2/applications/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/discord.com/api/v10/oau…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/oauth2/applications/@me (extensions/discord/src/monitor/provider.rest-proxy.test.ts:256)
`extensions/discord/src/monitor/provider.rest-proxy.test.ts:256` calls `GET https://discord.com/api/v10/oauth2/applications/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/discord.com/api/v10/oau…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/oauth2/applications/@me (extensions/discord/src/monitor/provider.rest-proxy.test.ts:273)
`extensions/discord/src/monitor/provider.rest-proxy.test.ts:273` calls `GET https://discord.com/api/v10/oauth2/applications/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/discord.com/api/v10/oau…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/oauth2/applications/@me (extensions/discord/src/monitor/provider.rest-proxy.test.ts:307)
`extensions/discord/src/monitor/provider.rest-proxy.test.ts:307` calls `GET https://discord.com/api/v10/oauth2/applications/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/discord.com/api/v10/oau…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/oauth2/applications/@me (extensions/discord/src/monitor/provider.rest-proxy.test.ts:334)
`extensions/discord/src/monitor/provider.rest-proxy.test.ts:334` calls `GET https://discord.com/api/v10/oauth2/applications/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/discord.com/api/v10/oau…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/oauth2/applications/@me (extensions/discord/src/monitor/provider.rest-proxy.test.ts:356)
`extensions/discord/src/monitor/provider.rest-proxy.test.ts:356` calls `GET https://discord.com/api/v10/oauth2/applications/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/discord.com/api/v10/oau…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://example.invalid (src/skills/security/scanner.test.ts:290)
`src/skills/security/scanner.test.ts:290` calls `GET https://example.invalid` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.invalid` If this points at an external API, prefix it with `https://` so th…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://github.com/${login}.png?size=${AVATAR_PROBE_SIZE} (scripts/update-clawtributors.ts:457)
`scripts/update-clawtributors.ts:457` calls `GET https://github.com/${login}.png?size=${AVATAR_PROBE_SIZE}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/github.com/<p>.png` If this points at an external API…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://mcp.example.com/.well-known/oauth-protected-resource (src/agents/mcp-http-fetch.test.ts:189)
`src/agents/mcp-http-fetch.test.ts:189` calls `GET https://mcp.example.com/.well-known/oauth-protected-resource` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/mcp.example.com/.well-known/oauth-protected-reso…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://mcp.example.com/token (src/agents/mcp-http-fetch.test.ts:117)
`src/agents/mcp-http-fetch.test.ts:117` calls `GET https://mcp.example.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/mcp.example.com/token` If this points at an external API, prefix it with `https…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://mcp.example.com/token (src/agents/mcp-http-fetch.test.ts:130)
`src/agents/mcp-http-fetch.test.ts:130` calls `GET https://mcp.example.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/mcp.example.com/token` If this points at an external API, prefix it with `https…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://mcp.example.com/token (src/agents/mcp-http-fetch.test.ts:158)
`src/agents/mcp-http-fetch.test.ts:158` calls `GET https://mcp.example.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/mcp.example.com/token` If this points at an external API, prefix it with `https…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: GET https://mcp.example.com/token (src/agents/mcp-http-fetch.test.ts:98)
`src/agents/mcp-http-fetch.test.ts:98` calls `GET https://mcp.example.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/mcp.example.com/token` If this points at an external API, prefix it with `https:…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${port}/callback (src/plugin-sdk/provider-auth-runtime.test.ts:100)
`src/plugin-sdk/provider-auth-runtime.test.ts:100` calls `OPTIONS http://127.0.0.1:${port}/callback` 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>/callback` If this points at an external API, p…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${port}/callback (src/plugin-sdk/provider-auth-runtime.test.ts:139)
`src/plugin-sdk/provider-auth-runtime.test.ts:139` calls `OPTIONS http://127.0.0.1:${port}/callback` 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>/callback` If this points at an external API, p…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${port}/callback (src/plugin-sdk/provider-auth-runtime.test.ts:61)
`src/plugin-sdk/provider-auth-runtime.test.ts:61` calls `OPTIONS http://127.0.0.1:${port}/callback` 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>/callback` If this points at an external API, pr…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST /api/channels/${encodeURIComponent(channelId)}/messages (extensions/clickclack/src/http-client.ts:88)
`extensions/clickclack/src/http-client.ts:88` calls `POST /api/channels/${encodeURIComponent(channelId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/channels/<p>/messages` If this points at an …
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: POST /api/dms (extensions/clickclack/src/http-client.ts:105)
`extensions/clickclack/src/http-client.ts:105` calls `POST /api/dms` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dms` If this points at an external API, prefix it with `https://` so the matcher skips it.
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: POST /api/dms/${encodeURIComponent(conversationId)}/messages (extensions/clickclack/src/http-client.ts:115)
`extensions/clickclack/src/http-client.ts:115` calls `POST /api/dms/${encodeURIComponent(conversationId)}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dms/<p>/messages` If this points at an exte…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: POST /api/messages/${encodeURIComponent(messageId)}/thread/replies (extensions/clickclack/src/http-client.ts:95)
`extensions/clickclack/src/http-client.ts:95` calls `POST /api/messages/${encodeURIComponent(messageId)}/thread/replies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/messages/<p>/thread/replies` If this p…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: POST /channels/direct (extensions/mattermost/src/mattermost/client.ts:225)
`extensions/mattermost/src/mattermost/client.ts:225` calls `POST /channels/direct` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/channels/direct` If this points at an external API, prefix it with `https://…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: POST /commands (extensions/mattermost/src/mattermost/slash-commands.ts:214)
`extensions/mattermost/src/mattermost/slash-commands.ts:214` calls `POST /commands` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/commands` If this points at an external API, prefix it with `https://` so t…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: POST /posts (extensions/mattermost/src/mattermost/client.test.ts:137)
`extensions/mattermost/src/mattermost/client.test.ts:137` calls `POST /posts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/posts` If this points at an external API, prefix it with `https://` so the matche…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: POST /posts (extensions/mattermost/src/mattermost/client.ts:517)
`extensions/mattermost/src/mattermost/client.ts:517` calls `POST /posts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/posts` If this points at an external API, prefix it with `https://` so the matcher ski…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: POST /users/ids (extensions/mattermost/src/mattermost/directory.ts:161)
`extensions/mattermost/src/mattermost/directory.ts:161` calls `POST /users/ids` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/ids` If this points at an external API, prefix it with `https://` so the …
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: POST /users/search (extensions/mattermost/src/mattermost/directory.ts:149)
`extensions/mattermost/src/mattermost/directory.ts:149` calls `POST /users/search` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/search` If this points at an external API, prefix it with `https://` s…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://10.0.0.5:11434/api/chat (src/agents/provider-transport-fetch.test.ts:895)
`src/agents/provider-transport-fetch.test.ts:895` calls `POST http://10.0.0.5:11434/api/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/10.0.0.5:11434/api/chat` If this points at an external API,…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://10.0.0.5:1234/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:702)
`src/agents/provider-transport-fetch.test.ts:702` calls `POST http://10.0.0.5:1234/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/10.0.0.5:1234/v1/chat/completions` If this points…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://10.0.0.5:1234/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:747)
`src/agents/provider-transport-fetch.test.ts:747` calls `POST http://10.0.0.5:1234/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/10.0.0.5:1234/v1/chat/completions` If this points…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://10.0.0.5:1234/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:806)
`src/agents/provider-transport-fetch.test.ts:806` calls `POST http://10.0.0.5:1234/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/10.0.0.5:1234/v1/chat/completions` If this points…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://10.0.0.5:4321/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:787)
`src/agents/provider-transport-fetch.test.ts:787` calls `POST http://10.0.0.5:4321/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/10.0.0.5:4321/v1/chat/completions` If this points…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${enabledPort}/v1/embeddings (src/gateway/embeddings-http.test.ts:144)
`src/gateway/embeddings-http.test.ts:144` calls `POST http://127.0.0.1:${enabledPort}/v1/embeddings` 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>/v1/embeddings` If this points at an external A…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${enabledPort}/v1/embeddings (src/gateway/embeddings-http.test.ts:320)
`src/gateway/embeddings-http.test.ts:320` calls `POST http://127.0.0.1:${enabledPort}/v1/embeddings` 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>/v1/embeddings` If this points at an external A…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${params.port}/mcp (src/gateway/mcp-http.test.ts:120)
`src/gateway/mcp-http.test.ts:120` calls `POST http://127.0.0.1:${params.port}/mcp` 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>/mcp` If this points at an external API, prefix it with `https:/…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${params.port}/tools/invoke (src/gateway/tools-invoke-http.test.ts:313)
`src/gateway/tools-invoke-http.test.ts:313` calls `POST http://127.0.0.1:${params.port}/tools/invoke` 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>/tools/invoke` If this points at an external A…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}${pathLocal} (src/gateway/server.hooks.test.ts:61)
`src/gateway/server.hooks.test.ts:61` calls `POST http://127.0.0.1:${port}${pathLocal}` 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 `htt…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}${pathname} (src/gateway/session-kill-http.test.ts:116)
`src/gateway/session-kill-http.test.ts:116` calls `POST http://127.0.0.1:${port}${pathname}` 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…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/hooks/agent (src/gateway/server.hooks.test.ts:499)
`src/gateway/server.hooks.test.ts:499` calls `POST http://127.0.0.1:${port}/hooks/agent` 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>/hooks/agent` If this points at an external API, prefix it …
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/hooks/mapped-ok (src/gateway/server.hooks.test.ts:515)
`src/gateway/server.hooks.test.ts:515` calls `POST http://127.0.0.1:${port}/hooks/mapped-ok` 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>/hooks/mapped-ok` If this points at an external API, pr…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/tools/invoke (src/gateway/gateway.test.ts:310)
`src/gateway/gateway.test.ts:310` calls `POST http://127.0.0.1:${port}/tools/invoke` 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>/tools/invoke` If this points at an external API, prefix it wit…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/tools/invoke (src/gateway/tools-invoke-http.cron-regression.test.ts:124)
`src/gateway/tools-invoke-http.cron-regression.test.ts:124` calls `POST http://127.0.0.1:${port}/tools/invoke` 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>/tools/invoke` If this points at an e…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/chat/completions (src/gateway/openai-http.test.ts:1757)
`src/gateway/openai-http.test.ts:1757` calls `POST http://127.0.0.1:${port}/v1/chat/completions` 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>/v1/chat/completions` If this points at an external…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/chat/completions (src/gateway/openai-http.test.ts:1764)
`src/gateway/openai-http.test.ts:1764` calls `POST http://127.0.0.1:${port}/v1/chat/completions` 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>/v1/chat/completions` If this points at an external…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/chat/completions (src/gateway/openai-http.test.ts:201)
`src/gateway/openai-http.test.ts:201` calls `POST http://127.0.0.1:${port}/v1/chat/completions` 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>/v1/chat/completions` If this points at an external …
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/chat/completions (src/gateway/openai-http.test.ts:2476)
`src/gateway/openai-http.test.ts:2476` calls `POST http://127.0.0.1:${port}/v1/chat/completions` 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>/v1/chat/completions` If this points at an external…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/chat/completions (src/gateway/openai-http.test.ts:80)
`src/gateway/openai-http.test.ts:80` calls `POST http://127.0.0.1:${port}/v1/chat/completions` 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>/v1/chat/completions` If this points at an external A…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/responses (src/gateway/openresponses-http.test.ts:104)
`src/gateway/openresponses-http.test.ts:104` calls `POST http://127.0.0.1:${port}/v1/responses` 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>/v1/responses` If this points at an external API, pr…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/responses (src/gateway/openresponses-http.test.ts:273)
`src/gateway/openresponses-http.test.ts:273` calls `POST http://127.0.0.1:${port}/v1/responses` 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>/v1/responses` If this points at an external API, pr…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/responses (src/gateway/openresponses-http.test.ts:978)
`src/gateway/openresponses-http.test.ts:978` calls `POST http://127.0.0.1:${port}/v1/responses` 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>/v1/responses` If this points at an external API, pr…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/traces (test/scripts/qa-otel-smoke.test.ts:108)
`test/scripts/qa-otel-smoke.test.ts:108` calls `POST http://127.0.0.1:${port}/v1/traces` 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>/v1/traces` If this points at an external API, prefix it wi…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/traces (test/scripts/qa-otel-smoke.test.ts:142)
`test/scripts/qa-otel-smoke.test.ts:142` calls `POST http://127.0.0.1:${port}/v1/traces` 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>/v1/traces` If this points at an external API, prefix it wi…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${runtime.port}/mcp (src/gateway/gateway-cli-backend.live-probe-helpers.ts:223)
`src/gateway/gateway-cli-backend.live-probe-helpers.ts:223` calls `POST http://127.0.0.1:${runtime.port}/mcp` 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>/mcp` If this points at an external AP…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:11434/api/chat (src/agents/provider-transport-fetch.test.ts:974)
`src/agents/provider-transport-fetch.test.ts:974` calls `POST http://127.0.0.1:11434/api/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:11434/api/chat` If this points at an external AP…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:11434/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:990)
`src/agents/provider-transport-fetch.test.ts:990` calls `POST http://127.0.0.1:11434/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:11434/v1/chat/completions` If this po…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:1234/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:766)
`src/agents/provider-transport-fetch.test.ts:766` calls `POST http://127.0.0.1:1234/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:1234/v1/chat/completions` If this poin…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:18000/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:414)
`src/agents/provider-transport-fetch.test.ts:414` calls `POST http://127.0.0.1:18000/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:18000/v1/chat/completions` If this po…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:18000/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:478)
`src/agents/provider-transport-fetch.test.ts:478` calls `POST http://127.0.0.1:18000/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:18000/v1/chat/completions` If this po…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:18000/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:497)
`src/agents/provider-transport-fetch.test.ts:497` calls `POST http://127.0.0.1:18000/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:18000/v1/chat/completions` If this po…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:18000/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:522)
`src/agents/provider-transport-fetch.test.ts:522` calls `POST http://127.0.0.1:18000/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:18000/v1/chat/completions` If this po…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:18000/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:554)
`src/agents/provider-transport-fetch.test.ts:554` calls `POST http://127.0.0.1:18000/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:18000/v1/chat/completions` If this po…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:18000/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:583)
`src/agents/provider-transport-fetch.test.ts:583` calls `POST http://127.0.0.1:18000/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:18000/v1/chat/completions` If this po…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:18000/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:611)
`src/agents/provider-transport-fetch.test.ts:611` calls `POST http://127.0.0.1:18000/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:18000/v1/chat/completions` If this po…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:18000/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:647)
`src/agents/provider-transport-fetch.test.ts:647` calls `POST http://127.0.0.1:18000/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/http:/127.0.0.1:18000/v1/chat/completions` If this po…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://10.0.0.5:1234/v1/chat/completions (src/agents/provider-transport-fetch.test.ts:725)
`src/agents/provider-transport-fetch.test.ts:725` calls `POST https://10.0.0.5:1234/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/10.0.0.5:1234/v1/chat/completions` If this poin…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (src/agents/embedded-agent-runner-extraparams.live.test.ts:130)
`src/agents/embedded-agent-runner-extraparams.live.test.ts:130` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points …
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (src/agents/provider-headers.live.test.ts:73)
`src/agents/provider-headers.live.test.ts:73` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (src/agents/provider-transport-fetch.test.ts:448)
`src/agents/provider-transport-fetch.test.ts:448` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.example.com/messages (src/proxy-capture/runtime.test.ts:103)
`src/proxy-capture/runtime.test.ts:103` calls `POST https://api.example.com/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.example.com/messages` If this points at an external API, prefix it with…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.minimax.io/anthropic/messages (src/proxy-capture/runtime.test.ts:68)
`src/proxy-capture/runtime.test.ts:68` calls `POST https://api.minimax.io/anthropic/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.minimax.io/anthropic/messages` If this points at an external AP…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/realtime/calls (scripts/dev/realtime-talk-live-smoke.ts:333)
`scripts/dev/realtime-talk-live-smoke.ts:333` calls `POST https://api.openai.com/v1/realtime/calls` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/realtime/calls` If this points at an extern…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/responses (src/agents/embedded-agent-runner-extraparams.live.test.ts:92)
`src/agents/embedded-agent-runner-extraparams.live.test.ts:92` calls `POST https://api.openai.com/v1/responses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/responses` If this points at an…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/responses (src/agents/provider-headers.live.test.ts:28)
`src/agents/provider-headers.live.test.ts:28` calls `POST https://api.openai.com/v1/responses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/responses` If this points at an external API, pr…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/responses (src/agents/provider-transport-fetch.test.ts:189)
`src/agents/provider-transport-fetch.test.ts:189` calls `POST https://api.openai.com/v1/responses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/api.openai.com/v1/responses` If this points at an ext…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/responses (src/agents/provider-transport-fetch.test.ts:661)
`src/agents/provider-transport-fetch.test.ts:661` calls `POST https://api.openai.com/v1/responses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/api.openai.com/v1/responses` If this points at an ext…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/responses (src/agents/provider-transport-fetch.test.ts:914)
`src/agents/provider-transport-fetch.test.ts:914` calls `POST https://api.openai.com/v1/responses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/api.openai.com/v1/responses` If this points at an ext…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/responses (src/agents/provider-transport-fetch.test.ts:944)
`src/agents/provider-transport-fetch.test.ts:944` calls `POST https://api.openai.com/v1/responses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/api.openai.com/v1/responses` If this points at an ext…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/responses (src/agents/provider-transport-fetch.test.ts:959)
`src/agents/provider-transport-fetch.test.ts:959` calls `POST https://api.openai.com/v1/responses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/api.openai.com/v1/responses` If this points at an ext…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://evil.com/collect (src/skills/security/scanner.test.ts:209)
`src/skills/security/scanner.test.ts:209` calls `POST https://evil.com/collect` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/evil.com/collect` If this points at an external API, prefix it with `https://` so…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://evil.com/harvest (src/skills/security/scanner.test.ts:245)
`src/skills/security/scanner.test.ts:245` calls `POST https://evil.com/harvest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/evil.com/harvest` If this points at an external API, prefix it with `https://` so…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://evil.example/harvest (src/plugins/install.test.ts:1689)
`src/plugins/install.test.ts:1689` calls `POST https://evil.example/harvest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/evil.example/harvest` If this points at an external API, prefix it with `https://` s…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://evil.example/harvest (src/plugins/install.test.ts:1894)
`src/plugins/install.test.ts:1894` calls `POST https://evil.example/harvest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/evil.example/harvest` If this points at an external API, prefix it with `https://` s…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://evil.example/harvest (src/skills/security/scanner.test.ts:350)
`src/skills/security/scanner.test.ts:350` calls `POST https://evil.example/harvest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/evil.example/harvest` If this points at an external API, prefix it with `http…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://evil.example/harvest (src/skills/security/scanner.test.ts:436)
`src/skills/security/scanner.test.ts:436` calls `POST https://evil.example/harvest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/evil.example/harvest` If this points at an external API, prefix it with `http…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://example.invalid (src/plugins/install.test.ts:1714)
`src/plugins/install.test.ts:1714` calls `POST https://example.invalid` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.invalid` If this points at an external API, prefix it with `https://` so the matc…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://example.invalid/media-image (src/agents/tools/image-tool.test.ts:570)
`src/agents/tools/image-tool.test.ts:570` calls `POST https://example.invalid/media-image` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.invalid/media-image` If this points at an external API, prefix…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://example.invalid/media-images (src/agents/tools/image-tool.test.ts:586)
`src/agents/tools/image-tool.test.ts:586` calls `POST https://example.invalid/media-images` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.invalid/media-images` If this points at an external API, pref…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://slack.com/api/auth.test (extensions/qa-lab/src/mantis/slack-desktop-smoke.runtime.ts:640)
`extensions/qa-lab/src/mantis/slack-desktop-smoke.runtime.ts:640` calls `POST https://slack.com/api/auth.test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/slack.com/api/auth.test` If this points at an exte…
wiringdangling-fetchfetch
high 9-layer api wiring conf 1.00 Dangling fetch: POST https://uploads.openai.com/v1/files (src/agents/provider-transport-fetch.test.ts:683)
`src/agents/provider-transport-fetch.test.ts:683` calls `POST https://uploads.openai.com/v1/files` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:fetcher Normalized path used for matching: `/https:/uploads.openai.com/v1/files` If this points at an ext…
wiringdangling-fetchhelper:fetcher
high 9-layer api wiring conf 1.00 Dangling fetch: PUT /commands/${encodeURIComponent(params.id)} (extensions/mattermost/src/mattermost/slash-commands.ts:236)
`extensions/mattermost/src/mattermost/slash-commands.ts:236` calls `PUT /commands/${encodeURIComponent(params.id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/commands/<p>` If this points at an external…
wiringdangling-fetchhelper:request
high 9-layer api wiring conf 1.00 Dangling fetch: PUT /posts/${postId} (extensions/mattermost/src/mattermost/client.ts:551)
`extensions/mattermost/src/mattermost/client.ts:551` calls `PUT /posts/${postId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/posts/<p>` If this points at an external API, prefix it with `https://` so th…
wiringdangling-fetchhelper:request
low 9-layer api wiring conf 1.00 Unused endpoint: DELETE /profiles/:name
`extensions/browser/src/browser/routes/basic.ts` declares `DELETE /profiles/:name` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: DELETE /tabs/:targetId
`extensions/browser/src/browser/routes/tabs.ts` declares `DELETE /tabs/:targetId` 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 …
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /
`extensions/browser/src/browser/bridge-server.ts` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /console
`extensions/browser/src/browser/routes/agent.debug.ts` declares `GET /console` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /cookies
`extensions/browser/src/browser/routes/agent.storage.ts` declares `GET /cookies` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /dialogs
`extensions/browser/src/browser/routes/agent.debug.ts` declares `GET /dialogs` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /doctor
`extensions/browser/src/browser/routes/basic.ts` declares `GET /doctor` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /errors
`extensions/browser/src/browser/routes/agent.debug.ts` declares `GET /errors` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /profiles
`extensions/browser/src/browser/routes/basic.ts` declares `GET /profiles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /requests
`extensions/browser/src/browser/routes/agent.debug.ts` declares `GET /requests` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /sandbox/novnc
`extensions/browser/src/browser/bridge-server.ts` declares `GET /sandbox/novnc` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /snapshot
`extensions/browser/src/browser/routes/agent.snapshot.ts` declares `GET /snapshot` 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…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /storage/:kind
`extensions/browser/src/browser/routes/agent.storage.ts` declares `GET /storage/:kind` 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 cons…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: GET /tabs
`extensions/browser/src/browser/routes/tabs.ts` declares `GET /tabs` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /act
`extensions/browser/src/browser/routes/agent.act.ts` declares `POST /act` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /api/messages
`extensions/msteams/src/monitor.ts` declares `POST /api/messages` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /cookies/clear
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /cookies/clear` 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 con…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /cookies/set
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /cookies/set` 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 consu…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /download
`extensions/browser/src/browser/routes/agent.act.download.ts` declares `POST /download` 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 con…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /highlight
`extensions/browser/src/browser/routes/agent.act.ts` declares `POST /highlight` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /hooks/dialog
`extensions/browser/src/browser/routes/agent.act.hooks.ts` declares `POST /hooks/dialog` 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 co…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /hooks/file-chooser
`extensions/browser/src/browser/routes/agent.act.hooks.ts` declares `POST /hooks/file-chooser` 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 …
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /navigate
`extensions/browser/src/browser/routes/agent.snapshot.ts` declares `POST /navigate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /pdf
`extensions/browser/src/browser/routes/agent.snapshot.ts` declares `POST /pdf` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /permissions/grant
`extensions/browser/src/browser/routes/permissions.ts` declares `POST /permissions/grant` 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 c…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /profiles/create
`extensions/browser/src/browser/routes/basic.ts` declares `POST /profiles/create` 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 …
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /response/body
`extensions/browser/src/browser/routes/agent.act.ts` declares `POST /response/body` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /screenshot
`extensions/browser/src/browser/routes/agent.snapshot.ts` declares `POST /screenshot` 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 consu…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /set/credentials
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /set/credentials` 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 c…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /set/device
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /set/device` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /set/geolocation
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /set/geolocation` 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 c…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /set/headers
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /set/headers` 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 consu…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /set/locale
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /set/locale` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /set/media
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /set/media` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /set/offline
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /set/offline` 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 consu…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /set/timezone
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /set/timezone` 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 cons…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /storage/:kind/clear
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /storage/:kind/clear` 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 w…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /storage/:kind/set
`extensions/browser/src/browser/routes/agent.storage.ts` declares `POST /storage/:kind/set` 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…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /tabs/action
`extensions/browser/src/browser/routes/tabs.ts` declares `POST /tabs/action` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /tabs/focus
`extensions/browser/src/browser/routes/tabs.ts` declares `POST /tabs/focus` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /tabs/open
`extensions/browser/src/browser/routes/tabs.ts` declares `POST /tabs/open` 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.
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /trace/start
`extensions/browser/src/browser/routes/agent.debug.ts` declares `POST /trace/start` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /trace/stop
`extensions/browser/src/browser/routes/agent.debug.ts` declares `POST /trace/stop` 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…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: POST /wait/download
`extensions/browser/src/browser/routes/agent.act.download.ts` declares `POST /wait/download` 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 wh…
wiringunused-endpoint
low 9-layer api wiring conf 1.00 Unused endpoint: USE /__openclaw/control-ui-config.json
`ui/vite.config.ts` declares `USE /__openclaw/control-ui-config.json` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
wiringunused-endpoint
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/133fe0c7-218e-4742-847e-cbe2f5a1fb4f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/133fe0c7-218e-4742-847e-cbe2f5a1fb4f/

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.