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

darkhtk/deskrelay

https://github.com/darkhtk/deskrelay · scanned 2026-06-17 01:53 UTC (1 month, 1 week ago)

133 raw signals (0 security + 133 graph)

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

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -28.9 (diff) · 133 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
47.8
/100
Security checks
48
0 findings
System graph
48
66.7% cov · 133 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 1 Medium 26 Low 68 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 133 Crowd 0 Layer: Frontend 11 Security 14 Quality 70 Api 38
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 47.8/100 with 66.7% coverage. It contains 1651 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 133 findings — concentrated in quality (70), api (38), security (14). Risk profile is high: 0 critical, 1 high, 26 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 95 of 133 actionable findings. 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: GET https://api.anthropic.com/api/oauth/usage (packages/behaviors/remote-claude/src/index.ts:1056)
`packages/behaviors/remote-claude/src/index.ts:1056` calls `GET https://api.anthropic.com/api/oauth/usage` 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/api/oauth/usage` If this points at a…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/pc-connector-cli/src/client.ts:113
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/pc-connector-daemon/src/behavior-fetcher.ts:32
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/pc-connector-daemon/src/device-identity.ts:140
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/pc-connector-daemon/src/site-ws-client.ts:688
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/pc-connector-daemon/test/daemon.e2e.test.ts:123
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/site-backend/src/app.ts:52
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/site-backend/test/announcement.test.ts:30
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/site-backend/test/app.test.ts:115
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/site-backend/test/full-chain.e2e.test.ts:2
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/site-frontend/src/api.ts:337
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/selfhost-virtual-e2e.ts:302
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/mobile-app/scripts/build-web.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/mobile-app/scripts/build-web.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/pc-connector-daemon/scripts/build-binary.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/pc-connector-daemon/scripts/build-binary.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/pc-connector-daemon/src/fs.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/pc-connector-daemon/src/fs.ts:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/pc-connector-daemon/src/git.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/pc-connector-daemon/src/git.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/pc-connector-daemon/src/login-task.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/pc-connector-daemon/src/login-task.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/pc-connector-daemon/src/self-register.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/pc-connector-daemon/src/self-register.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/pc-connector-daemon/src/self-update.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/pc-connector-daemon/src/self-update.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/shared/src/version.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/shared/src/version.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/site-backend/src/self-server-autostart.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/site-backend/src/self-server-autostart.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/site-backend/src/self-server-update.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/site-backend/src/self-server-update.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/site-backend/src/update-notice.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/site-backend/src/update-notice.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/selfhost-install-failure-smoke.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/selfhost-install-failure-smoke.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/selfhost-virtual-e2e.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/selfhost-virtual-e2e.ts:3 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 27 placeholder/mock markers across 11 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 54 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BUN_TARGET`, `CLAUDE_CODE_ACCOUNT_UUID`, `CLAUDE_CODE_OAUTH_TOKEN`, `CLAUDE_CODE_USER_EMAIL`, `CLAUDE_CONFIG_DIR`, `CLAUDE_PROJECTS_DIR`, `COMPUTERNAME`, `CR_CONNECTOR_APPROVALS` + 46 more. Add them (with a placeholder/comment) to .env.example so …
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: ci, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 33 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph security security conf 1.00 Insecure pattern 'document_write' in packages/site-frontend/src/conversation-export.ts:114
Found a known-risky pattern (document_write). Review and replace if possible.
packages/site-frontend/src/conversation-export.ts:114 Document write
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/behavior-sdk/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/behavior-sdk/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/behaviors/echo/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/behaviors/echo/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/behaviors/remote-claude/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/behaviors/remote-claude/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/core/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/core/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/mobile-app/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/mobile-app/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/pc-connector-cli/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/pc-connector-cli/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/pc-connector-daemon/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/pc-connector-daemon/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/site-backend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/site-backend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/site-frontend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/site-frontend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `apr_legacy` in packages/site-frontend/test/approval-modal.test.tsx:62
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `dev_old` in packages/pc-connector-daemon/test/self-register.test.ts:435
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `dev_old` in packages/site-backend/test/device-registry.test.ts:134
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/mobile-app/scripts/build-web.ts:28
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/mobile-app/scripts/sync-web.ts:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/pc-connector-daemon/scripts/build-binary.ts:40
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/pc-connector-daemon/src/bin.ts:520
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/site-backend/src/bin.ts:83
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packaging/brand/rasterize.ts:52
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/build-locales.ts:53
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/frontend-smoke.ts:114
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/selfhost-docs-forbidden-terms.ts:47
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/selfhost-install-failure-smoke.ts:79
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/selfhost-virtual-e2e.ts:68
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/devices
`packages/site-backend/src/app.ts` declares `DELETE /api/devices` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/devices/:id
`packages/site-backend/src/app.ts` declares `DELETE /api/devices/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/devices/:id/behaviors/:instance
`packages/site-backend/src/app.ts` declares `DELETE /api/devices/:id/behaviors/:instance` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/devices/:id/instructions/:scope
`packages/site-backend/src/app.ts` declares `DELETE /api/devices/:id/instructions/:scope` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/announcement
`packages/site-backend/src/app.ts` declares `GET /api/announcement` 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/devices
`packages/site-backend/src/app.ts` declares `GET /api/devices` 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/devices/:id/behaviors
`packages/site-backend/src/app.ts` declares `GET /api/devices/:id/behaviors` 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/devices/:id/diagnostics
`packages/site-backend/src/app.ts` declares `GET /api/devices/:id/diagnostics` 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/devices/:id/doctor
`packages/site-backend/src/app.ts` declares `GET /api/devices/:id/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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/devices/:id/events/spaces/:spaceId/stream
`packages/site-backend/src/app.ts` declares `GET /api/devices/:id/events/spaces/:spaceId/stream` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/devices/:id/files/preview
`packages/site-backend/src/app.ts` declares `GET /api/devices/:id/files/preview` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/devices/:id/fs/list
`packages/site-backend/src/app.ts` declares `GET /api/devices/:id/fs/list` 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/devices/:id/fs/roots
`packages/site-backend/src/app.ts` declares `GET /api/devices/:id/fs/roots` 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/devices/:id/git/status
`packages/site-backend/src/app.ts` declares `GET /api/devices/:id/git/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/devices/:id/instructions
`packages/site-backend/src/app.ts` declares `GET /api/devices/:id/instructions` 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/devices/update-queue
`packages/site-backend/src/app.ts` declares `GET /api/devices/update-queue` 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/self/autostart
`packages/site-backend/src/app.ts` declares `GET /api/self/autostart` 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/self/doctor
`packages/site-backend/src/app.ts` declares `GET /api/self/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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/self/install-reports
`packages/site-backend/src/app.ts` declares `GET /api/self/install-reports` 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/self/register-other-pc-command
`packages/site-backend/src/app.ts` declares `GET /api/self/register-other-pc-command` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/self/remove-other-pc-command
`packages/site-backend/src/app.ts` declares `GET /api/self/remove-other-pc-command` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/self/update/status
`packages/site-backend/src/app.ts` declares `GET /api/self/update/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/devices/:id
`packages/site-backend/src/app.ts` declares `PATCH /api/devices/: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: POST /api/devices
`packages/site-backend/src/app.ts` declares `POST /api/devices` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/devices/:id/approvals/respond
`packages/site-backend/src/app.ts` declares `POST /api/devices/:id/approvals/respond` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/devices/:id/approvals/simulate
`packages/site-backend/src/app.ts` declares `POST /api/devices/:id/approvals/simulate` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/devices/:id/behaviors/:instance/request
`packages/site-backend/src/app.ts` declares `POST /api/devices/:id/behaviors/:instance/request` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/devices/:id/behaviors/load
`packages/site-backend/src/app.ts` declares `POST /api/devices/:id/behaviors/load` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/devices/:id/fs/mkdir
`packages/site-backend/src/app.ts` declares `POST /api/devices/:id/fs/mkdir` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/devices/:id/system/update
`packages/site-backend/src/app.ts` declares `POST /api/devices/:id/system/update` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/self/install-reports
`packages/site-backend/src/app.ts` declares `POST /api/self/install-reports` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/self/update
`packages/site-backend/src/app.ts` declares `POST /api/self/update` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/devices/:id/instructions/:scope
`packages/site-backend/src/app.ts` declares `PUT /api/devices/:id/instructions/:scope` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/self/autostart
`packages/site-backend/src/app.ts` declares `PUT /api/self/autostart` 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 /__deskrelay/client-context
`packages/site-frontend/vite.config.ts` declares `USE /__deskrelay/client-context` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /__deskrelay/local-site-token
`packages/site-frontend/vite.config.ts` declares `USE /__deskrelay/local-site-token` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/*
`packages/site-backend/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 quality Complexity conf 1.00 Very large file: packages/site-backend/src/app.ts (1762 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/site-frontend/src/App.tsx (2309 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/site-frontend/src/components/ChatView.tsx (3990 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/site-frontend/test/chat-view-devices-refresh.test.tsx (2410 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/b8434bfe-682e-4c8a-9d48-7b49117daf4d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b8434bfe-682e-4c8a-9d48-7b49117daf4d/

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.