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

YOUSSEFELJAYAD/claude-fleet-portal

https://github.com/YOUSSEFELJAYAD/claude-fleet-portal · scanned 2026-06-16 01:08 UTC (2 months, 1 week ago)

182 raw signals (0 security + 182 graph)

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

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 182 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
46.5
/100
Security checks
47
0 findings
System graph
47
88.9% cov · 182 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 3 Medium 33 Low 70 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 182 Crowd 0 Layer: Frontend 39 Network 2 Security 22 Cicd 3 Quality 63 Api 53
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 46.5/100 with 88.9% coverage. It contains 2359 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 182 findings — concentrated in quality (63), api (53), frontend (39). Risk profile is high: 0 critical, 3 high, 33 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 106 of 182 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 http://127.0.0.1:${TEST_PORT}/health (apps/server/test/addons.test.ts:273)
`apps/server/test/addons.test.ts:273` calls `GET http://127.0.0.1:${TEST_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 `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${TEST_PORT}/health (apps/server/test/cov-addons.test.ts:516)
`apps/server/test/cov-addons.test.ts:516` calls `GET http://127.0.0.1:${TEST_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 wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/${slug}/releases?per_page=20 (apps/server/src/release.ts:137)
`apps/server/src/release.ts:137` calls `GET https://api.github.com/repos/${slug}/releases?per_page=20` 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.github.com/repos/<p>/releases` If this points…
Dangling fetchHelper:fetcher
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/web/app/history/page.tsx:245
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/web/components/ShikiCode.tsx:52
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/server/src/release.ts:89
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 — apps/server/test/notifier-channels.test.ts:191
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/pages.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in apps/web/app/history/page.tsx:245
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
apps/web/app/history/page.tsx:245 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in apps/web/components/ShikiCode.tsx:52
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
apps/web/components/ShikiCode.tsx:52 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/_lottie-preview.html:52
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/_lottie-preview.html:52 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/index.html:1470
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/index.html:1470 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/lab-hand-machine-agent.html:257
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/lab-hand-machine-agent.html:257 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/lab-laptop-agent.html:137
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/lab-laptop-agent.html:137 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/lab-orchestrator-flow.html:204
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/lab-orchestrator-flow.html:204 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in site/lab-laptop-agent.html:139
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
site/lab-laptop-agent.html:139 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/addons.ts:30
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/addons.ts:30 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/engines.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/engines.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/fileview.ts:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/fileview.ts:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/gh.ts:30
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/gh.ts:30 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/git.ts:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/git.ts:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/learner.ts:29
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/learner.ts:29 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/mcp.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/mcp.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/pm.ts:37
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/pm.ts:37 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/portbroker.ts:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/portbroker.ts:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/processManager.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/processManager.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/projects.ts:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/projects.ts:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/release.ts:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/release.ts:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/server/src/validation.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/server/src/validation.ts:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop/scripts/afterPack.cjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop/scripts/afterPack.cjs:13 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 146 placeholder/mock markers across 51 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 16 in use
Port 16 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.claude/homunculus/instincts/inherited/claude-fleet-portal-instincts.yaml Ports
medium System graph network Security conf 1.00 Privileged port 48 in use
Port 48 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.claude/homunculus/instincts/inherited/claude-fleet-portal-instincts.yaml Ports
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 15 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/deploy-pages@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/pages.yml:32 CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/app/benchmarks/page.tsx:125
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/components/LaunchModal.tsx:245
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/components/PlanModal.tsx:137
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/server/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.
apps/server/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/web/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.
apps/web/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/shared/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/shared/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/server/src/index.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 — apps/server/src/search.ts:55
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/server/test/addons.test.ts:20
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 — apps/server/test/cov-addons.test.ts:32
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/server/test/cov-search.test.ts:111
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/server/test/model-routing.test.ts:17
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 — apps/server/test/search.test.ts:45
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/agents/:id/tags/:tag
`apps/server/src/tags.ts` declares `DELETE /api/agents/:id/tags/:tag` 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/packs/:id
`apps/server/src/packs.ts` declares `DELETE /api/packs/: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/saved-searches/:id
`apps/server/src/tags.ts` declares `DELETE /api/saved-searches/: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/scores/:scoreId
`apps/server/src/scores.ts` declares `DELETE /api/scores/:scoreId` 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/triggers/:id
`apps/server/src/triggers.ts` declares `DELETE /api/triggers/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/addons
`apps/server/src/addons.ts` declares `GET /api/addons` 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/addons/:id
`apps/server/src/addons.ts` declares `GET /api/addons/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/addons/compression/stats
`apps/server/src/addons.ts` declares `GET /api/addons/compression/stats` 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/agents/:id/otel
`apps/server/src/otel.ts` declares `GET /api/agents/:id/otel` 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/agents/:id/scores
`apps/server/src/scores.ts` declares `GET /api/agents/:id/scores` 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/agents/:id/tags
`apps/server/src/tags.ts` declares `GET /api/agents/:id/tags` 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/learner
`apps/server/src/learner.ts` declares `GET /api/learner` 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/mcp
`apps/server/src/mcp.ts` declares `GET /api/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
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mcp/:name
`apps/server/src/mcp.ts` declares `GET /api/mcp/: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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/notifications
`apps/server/src/notifier.ts` declares `GET /api/notifications` 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/notifications/config
`apps/server/src/notifier.ts` declares `GET /api/notifications/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: GET /api/notifier/channels
`apps/server/src/notifier.ts` declares `GET /api/notifier/channels` 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/packs
`apps/server/src/packs.ts` declares `GET /api/packs` 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/plans/:id
`apps/server/src/planboard.ts` declares `GET /api/plans/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/projects/:pid/files/edit
`apps/server/src/fileedit.ts` declares `GET /api/projects/:pid/files/edit` 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/projects/:pid/plans
`apps/server/src/planboard.ts` declares `GET /api/projects/:pid/plans` 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/saved-searches
`apps/server/src/tags.ts` declares `GET /api/saved-searches` 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/scores/summary
`apps/server/src/scores.ts` declares `GET /api/scores/summary` 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/tags
`apps/server/src/tags.ts` declares `GET /api/tags` 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/triggers
`apps/server/src/triggers.ts` declares `GET /api/triggers` 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/addons/:id/disable
`apps/server/src/addons.ts` declares `POST /api/addons/:id/disable` 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/addons/:id/enable
`apps/server/src/addons.ts` declares `POST /api/addons/:id/enable` 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/addons/:id/install
`apps/server/src/addons.ts` declares `POST /api/addons/:id/install` 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/addons/:id/restart
`apps/server/src/addons.ts` declares `POST /api/addons/:id/restart` 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/addons/web-research/register-mcp
`apps/server/src/addons.ts` declares `POST /api/addons/web-research/register-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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/agents/:id/scores
`apps/server/src/scores.ts` declares `POST /api/agents/:id/scores` 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/agents/:id/tags
`apps/server/src/tags.ts` declares `POST /api/agents/:id/tags` 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/loops/generate
`apps/server/src/loopGen.ts` declares `POST /api/loops/generate` 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/notifications/read
`apps/server/src/notifier.ts` declares `POST /api/notifications/read` 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/notifications/test
`apps/server/src/notifier.ts` declares `POST /api/notifications/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: POST /api/notifier/channels/:id/test
`apps/server/src/notifier.ts` declares `POST /api/notifier/channels/:id/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: POST /api/packs
`apps/server/src/packs.ts` declares `POST /api/packs` 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/plans/:id/apply
`apps/server/src/planboard.ts` declares `POST /api/plans/:id/apply` 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/projects/:pid/files/commit
`apps/server/src/fileedit.ts` declares `POST /api/projects/:pid/files/commit` 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/projects/:pid/plan
`apps/server/src/planboard.ts` declares `POST /api/projects/:pid/plan` 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/saved-searches
`apps/server/src/tags.ts` declares `POST /api/saved-searches` 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/triggers
`apps/server/src/triggers.ts` declares `POST /api/triggers` 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/triggers/:id/poll
`apps/server/src/triggers.ts` declares `POST /api/triggers/:id/poll` 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 /v1/logs
`apps/server/src/otel.ts` declares `POST /v1/logs` 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 /v1/metrics
`apps/server/src/otel.ts` declares `POST /v1/metrics` 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/addons/:id/config
`apps/server/src/addons.ts` declares `PUT /api/addons/:id/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: PUT /api/notifications/config
`apps/server/src/notifier.ts` declares `PUT /api/notifications/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: PUT /api/notifier/channels
`apps/server/src/notifier.ts` declares `PUT /api/notifier/channels` 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/packs/:id
`apps/server/src/packs.ts` declares `PUT /api/packs/: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: PUT /api/triggers/:id
`apps/server/src/triggers.ts` declares `PUT /api/triggers/: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 quality Complexity conf 1.00 Very large file: apps/server/src/addons.ts (1465 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/server/src/pm.ts (1767 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/server/src/registry.ts (1275 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/shared/src/index.ts (1530 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/8f89e23f-f85c-4187-9d8f-744a6810b6bb/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8f89e23f-f85c-4187-9d8f-744a6810b6bb/

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.