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

dork-labs/dorkos

https://github.com/dork-labs/dorkos · scanned 2026-06-17 02:01 UTC (2 months, 3 weeks ago)

438 raw signals (0 security + 438 graph)

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

Complete repo analysis

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

JSON
Combined
43.2
/100
Security checks
43
0 findings
System graph
43
100.0% cov · 429 findings
Critical
4
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: layer: api × excluding tests × Reset all
Severity: Critical 4 High 29 Medium 101 Low 122 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 429 Crowd 0 Layer: Software 1 Frontend 125 Hardware 2 Security 42 Cicd 5 Quality 181 Api 73
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 43.2/100 with 100.0% coverage. It contains 10832 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 438 findings — concentrated in quality (181), frontend (125), api (73). Risk profile is high: 6 critical, 29 high, 106 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 73 of 429 actionable findings. 438 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/extensions/${extensionId}/secrets/${secret.key} (apps/client/src/layers/features/extensions/ui/ManifestSettingsPanel.tsx:280)
`apps/client/src/layers/features/extensions/ui/ManifestSettingsPanel.tsx:280` calls `DELETE /api/extensions/${extensionId}/secrets/${secret.key}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/secrets…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ext/${EXT_ID}/loop (examples/extensions/linear-issues/index.ts:104)
`examples/extensions/linear-issues/index.ts:104` calls `GET /api/ext/${EXT_ID}/loop` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ext/<p>/loop` 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 /api/extensions (apps/client/src/layers/features/extensions/api/queries.ts:32)
`apps/client/src/layers/features/extensions/api/queries.ts:32` calls `GET /api/extensions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions` 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/extensions (apps/client/src/layers/features/extensions/model/extension-loader.ts:19)
`apps/client/src/layers/features/extensions/model/extension-loader.ts:19` calls `GET /api/extensions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/extensions/${EXT_ID}/settings (examples/extensions/linear-issues/index.ts:105)
`examples/extensions/linear-issues/index.ts:105` calls `GET /api/extensions/${EXT_ID}/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/settings` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/extensions/${extensionId}/secrets (apps/client/src/layers/features/extensions/ui/ManifestSettingsPanel.tsx:101)
`apps/client/src/layers/features/extensions/ui/ManifestSettingsPanel.tsx:101` calls `GET /api/extensions/${extensionId}/secrets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/secrets` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/extensions/${extensionId}/settings (apps/client/src/layers/features/extensions/ui/ManifestSettingsPanel.tsx:104)
`apps/client/src/layers/features/extensions/ui/ManifestSettingsPanel.tsx:104` calls `GET /api/extensions/${extensionId}/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/settings` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/extensions/${extId}/data (apps/client/src/layers/features/extensions/model/extension-api-factory.ts:150)
`apps/client/src/layers/features/extensions/model/extension-api-factory.ts:150` calls `GET /api/extensions/${extId}/data` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/data` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/api/health (apps/desktop/src/server-entry.ts:14)
`apps/desktop/src/server-entry.ts:14` calls `GET http://localhost:${port}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/health` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.example.com/data (apps/server/src/services/extensions/extension-templates.ts:164)
`apps/server/src/services/extensions/extension-templates.ts:164` 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…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/dorkos/latest (apps/server/src/services/core/update-checker.ts:37)
`apps/server/src/services/core/update-checker.ts:37` calls `GET https://registry.npmjs.org/dorkos/latest` 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/dorkos/latest` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/dorkos/latest (packages/cli/src/update-check.ts:44)
`packages/cli/src/update-check.ts:44` calls `GET https://registry.npmjs.org/dorkos/latest` 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/dorkos/latest` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/extensions/${id}/disable (apps/client/src/layers/features/extensions/api/queries.ts:74)
`apps/client/src/layers/features/extensions/api/queries.ts:74` calls `POST /api/extensions/${id}/disable` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/disable` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/extensions/${id}/enable (apps/client/src/layers/features/extensions/api/queries.ts:53)
`apps/client/src/layers/features/extensions/api/queries.ts:53` calls `POST /api/extensions/${id}/enable` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/enable` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/extensions/${rec.id}/init-server (apps/client/src/layers/features/extensions/model/extension-loader.ts:51)
`apps/client/src/layers/features/extensions/model/extension-loader.ts:51` calls `POST /api/extensions/${rec.id}/init-server` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/init-server` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/extensions/cwd-changed (apps/client/src/layers/features/extensions/model/use-cwd-extension-sync.ts:33)
`apps/client/src/layers/features/extensions/model/use-cwd-extension-sync.ts:33` calls `POST /api/extensions/cwd-changed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/cwd-changed` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/extensions/reload (apps/client/src/layers/features/extensions/api/queries.ts:94)
`apps/client/src/layers/features/extensions/api/queries.ts:94` calls `POST /api/extensions/reload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/reload` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/extensions/${extensionId}/secrets/${secret.key} (apps/client/src/layers/features/extensions/ui/ManifestSettingsPanel.tsx:261)
`apps/client/src/layers/features/extensions/ui/ManifestSettingsPanel.tsx:261` calls `PUT /api/extensions/${extensionId}/secrets/${secret.key}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/secrets/<p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/extensions/${extensionId}/settings/${status.key} (apps/client/src/layers/features/extensions/ui/SettingFieldRenderers.tsx:110)
`apps/client/src/layers/features/extensions/ui/SettingFieldRenderers.tsx:110` calls `PUT /api/extensions/${extensionId}/settings/${status.key}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/settings/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/extensions/${extensionId}/settings/${status.key} (apps/client/src/layers/features/extensions/ui/SettingFieldRenderers.tsx:167)
`apps/client/src/layers/features/extensions/ui/SettingFieldRenderers.tsx:167` calls `PUT /api/extensions/${extensionId}/settings/${status.key}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/settings/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/extensions/${extensionId}/settings/${status.key} (apps/client/src/layers/features/extensions/ui/SettingFieldRenderers.tsx:212)
`apps/client/src/layers/features/extensions/ui/SettingFieldRenderers.tsx:212` calls `PUT /api/extensions/${extensionId}/settings/${status.key}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/settings/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/extensions/${extensionId}/settings/${status.key} (apps/client/src/layers/features/extensions/ui/SettingFieldRenderers.tsx:56)
`apps/client/src/layers/features/extensions/ui/SettingFieldRenderers.tsx:56` calls `PUT /api/extensions/${extensionId}/settings/${status.key}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/settings/<…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/extensions/${extId}/data (apps/client/src/layers/features/extensions/model/extension-api-factory.ts:157)
`apps/client/src/layers/features/extensions/model/extension-api-factory.ts:157` calls `PUT /api/extensions/${extId}/data` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/extensions/<p>/data` If this points at an exte…
Dangling fetchFetch
low System graph api Wiring conf 1.00 Unused endpoint: ALL /proxy/*
`apps/server/src/services/extensions/extension-proxy.ts` declares `ALL /proxy/*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /
`apps/server/src/routes/mcp.ts` declares `DELETE /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`apps/server/src/routes/subagents.ts` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:filename
`apps/server/src/routes/uploads.ts` declares `GET /:filename` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /agents/:id/card
`apps/server/src/routes/a2a.ts` declares `GET /agents/:id/card` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/openapi.json
`apps/server/src/app.ts` declares `GET /api/openapi.json` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /cached
`examples/extensions/linear-issues/server.ts` declares `GET /cached` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /current
`apps/server/src/routes/agents.ts` declares `GET /current` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /data
`apps/server/src/services/runtimes/claude-code/mcp-tools/extension-tools.ts` declares `GET /data` 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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /default
`apps/server/src/routes/directory.ts` declares `GET /default` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /issues
`examples/extensions/linear-issues/server.ts` declares `GET /issues` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /loop
`examples/extensions/linear-issues/server.ts` declares `GET /loop` 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: PATCH /current
`apps/server/src/routes/agents.ts` declares `PATCH /current` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`apps/server/src/routes/a2a.ts` declares `POST /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /create
`apps/server/src/routes/agents.ts` declares `POST /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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /current/migrate-persona
`apps/server/src/routes/agents.ts` declares `POST /current/migrate-persona` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /resolve
`apps/server/src/routes/agents.ts` declares `POST /resolve` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /scan
`apps/server/src/routes/discovery.ts` declares `POST /scan` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /scenario
`apps/server/src/routes/test-control.ts` declares `POST /scenario` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /a2a
`apps/server/src/index.ts` declares `USE /a2a` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api
`apps/server/src/app.ts` declares `USE /api` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/activity
`apps/server/src/index.ts` declares `USE /api/activity` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/admin
`apps/server/src/index.ts` declares `USE /api/admin` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/agents
`apps/server/src/index.ts` declares `USE /api/agents` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/capabilities
`apps/server/src/app.ts` declares `USE /api/capabilities` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/commands
`apps/server/src/app.ts` declares `USE /api/commands` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/config
`apps/server/src/app.ts` declares `USE /api/config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/directory
`apps/server/src/app.ts` declares `USE /api/directory` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/discovery
`apps/server/src/index.ts` declares `USE /api/discovery` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/docs
`apps/server/src/app.ts` declares `USE /api/docs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/events
`apps/server/src/app.ts` declares `USE /api/events` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/ext/:id
`apps/server/src/index.ts` declares `USE /api/ext/: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: USE /api/extensions
`apps/server/src/index.ts` declares `USE /api/extensions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/files
`apps/server/src/app.ts` declares `USE /api/files` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/git
`apps/server/src/app.ts` declares `USE /api/git` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/health
`apps/server/src/app.ts` declares `USE /api/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/marketplace
`apps/server/src/index.ts` declares `USE /api/marketplace` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/mcp-config
`apps/server/src/app.ts` declares `USE /api/mcp-config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/mesh
`apps/server/src/index.ts` declares `USE /api/mesh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/models
`apps/server/src/app.ts` declares `USE /api/models` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/relay
`apps/server/src/index.ts` declares `USE /api/relay` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/sessions
`apps/server/src/app.ts` declares `USE /api/sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/subagents
`apps/server/src/app.ts` declares `USE /api/subagents` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/system
`apps/server/src/app.ts` declares `USE /api/system` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/tasks
`apps/server/src/index.ts` declares `USE /api/tasks` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/templates
`apps/server/src/index.ts` declares `USE /api/templates` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/test
`apps/server/src/app.ts` declares `USE /api/test` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/tunnel
`apps/server/src/app.ts` declares `USE /api/tunnel` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/uploads
`apps/server/src/app.ts` declares `USE /api/uploads` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /mcp
`apps/server/src/index.ts` declares `USE /mcp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/50013d13-2b13-45b6-b039-688162b7d0d0/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/50013d13-2b13-45b6-b039-688162b7d0d0/

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.