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

wlsdks/Muse

https://github.com/wlsdks/Muse · scanned 2026-06-16 00:59 UTC (2 months, 1 week ago)

594 raw signals (0 security + 594 graph)

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

Complete repo analysis

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

JSON
Combined
66.4
/100
Security checks
66
0 findings
System graph
66
100.0% cov · 594 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 6 Medium 82 Low 108 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 594 Crowd 0 Layer: Frontend 4 Security 55 Quality 480 Api 55
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 66.4/100 with 100.0% coverage. It contains 10048 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 594 findings — concentrated in quality (480), security (55), api (55). Risk profile is high: 0 critical, 6 high, 82 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 188 of 594 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: DELETE /calendars/${encodeURIComponent(this.options.calendarId)}/events/${encodeURIComponent(id)} (packages/calendar/src/google-provider.ts:158)
`packages/calendar/src/google-provider.ts:158` calls `DELETE /calendars/${encodeURIComponent(this.options.calendarId)}/events/${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/calend…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /calendars/${encodeURIComponent(this.options.calendarId)}/events?${params.toString()} (packages/calendar/src/google-provider.ts:131)
`packages/calendar/src/google-provider.ts:131` calls `GET /calendars/${encodeURIComponent(this.options.calendarId)}/events?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/calendars/<p>/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:11434/api/tags (scripts/dogfood-phase-d.mjs:41)
`scripts/dogfood-phase-d.mjs:41` calls `GET http://127.0.0.1:11434/api/tags` 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:11434/api/tags` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /calendars/${encodeURIComponent(this.options.calendarId)}/events/${encodeURIComponent(id)} (packages/calendar/src/google-provider.ts:150)
`packages/calendar/src/google-provider.ts:150` calls `PATCH /calendars/${encodeURIComponent(this.options.calendarId)}/events/${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/calenda…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /calendars/${encodeURIComponent(this.options.calendarId)}/events (packages/calendar/src/google-provider.ts:141)
`packages/calendar/src/google-provider.ts:141` calls `POST /calendars/${encodeURIComponent(this.options.calendarId)}/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/calendars/<p>/events` If this poin…
Dangling fetchHelper:request
high System graph security security conf 1.00 Insecure pattern 'eval_used' in .claude/skills/loop-creator/SKILL.md:92
Found a known-risky pattern (eval_used). Review and replace if possible.
.claude/skills/loop-creator/SKILL.md:92 Eval used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/web/src/components/markdown.tsx:7
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/api/src/compat-mcp-proxy.ts:3
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/cli/scripts/verify-council-self-abstention.mjs:54
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/cli/src/commands-feeds.test.ts:298
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/cli/src/commands-feeds.ts:256
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/cli/src/commands-voice.test.ts:74
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/web/src/api/client.ts:31
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/agent-core/src/agent-runtime-types.ts:103
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/agent-core/src/model-loop.ts:87
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/agent-core/test/cap-tool-output.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/autoconfigure/src/context-engineering-builders.ts:239
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/mcp/src/email-tool.ts:220
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/mcp/src/loopback-context.ts:7
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/mcp/src/loopback-web-read.ts:19
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/mcp/src/run-actuator-by-name.test.ts:111
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/memory/src/context-reference-store.ts:10
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/model/src/adapter-ollama.ts:298
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/dogfood-local-llm.mjs:70
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/smoke-broad-http.mjs:63
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/smoke-diagnostic-runtime.mjs:86
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/smoke-live-all-providers.mjs:137
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/smoke-live-llm.mjs:133
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/README.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/README.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skills/gh/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
skills/gh/SKILL.md VerificationSkill file
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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in scripts/eval-browser-agent.mjs:54
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
scripts/eval-browser-agent.mjs:54 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in scripts/smoke-browser.mjs:55
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
scripts/smoke-browser.mjs:55 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in scripts/smoke-browser.mjs:132
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
scripts/smoke-browser.mjs:132 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in apps/web/src/app/App.tsx:183
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
apps/web/src/app/App.tsx:183 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/api/src/os-idle.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/api/src/os-idle.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/api/src/power-state.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/api/src/power-state.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/scripts/eval.mjs:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/scripts/eval.mjs:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/scripts/verify-reasoning-efficacy.mjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/scripts/verify-reasoning-efficacy.mjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/scripts/verify-vision-agent.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/scripts/verify-vision-agent.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/scripts/verify-vision-grounding.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/scripts/verify-vision-grounding.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/chat-ink.ts:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/chat-ink.ts:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/clipboard-reader.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/clipboard-reader.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/commands-brief.ts:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/commands-brief.ts:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/commands-demo.ts:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/commands-demo.ts:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/commands-export.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/commands-export.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/commands-glance.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/commands-glance.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/commands-import.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/commands-import.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/commands-listen.ts:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/commands-listen.ts:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/commands-show.ts:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/commands-show.ts:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/voice-playback.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/voice-playback.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in harness/runner/run-project.mjs:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
harness/runner/run-project.mjs:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in harness/runner/run.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
harness/runner/run.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/browser/src/puppeteer-controller.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/browser/src/puppeteer-controller.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/calendar/src/macos-provider.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/calendar/src/macos-provider.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/macos/src/macos-exec.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/macos/src/macos-exec.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/mcp/src/macos-ambient-source.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/mcp/src/macos-ambient-source.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/mcp/src/notes-providers-apple.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/mcp/src/notes-providers-apple.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/mcp/src/tasks-providers-apple.ts:35
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/mcp/src/tasks-providers-apple.ts:35 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/messaging/src/linux-libnotify-provider.ts:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/messaging/src/linux-libnotify-provider.ts:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/messaging/src/macos-notification-provider.ts:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/messaging/src/macos-notification-provider.ts:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/tools/src/runner.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/tools/src/runner.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/voice/src/piper.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/voice/src/piper.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/voice/src/whisper-cpp.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/voice/src/whisper-cpp.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dashboard-server.mjs:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/dashboard-server.mjs:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/eval-agent.mjs:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/eval-agent.mjs:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/eval-self-improving.mjs:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/eval-self-improving.mjs:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/guard-immutable.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/guard-immutable.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/guard-writeback.mjs:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/guard-writeback.mjs:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/pick-evals.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/pick-evals.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/precheck-grounding.mjs:27
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/precheck-grounding.mjs:27 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/self-eval.mjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/self-eval.mjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/smoke-broad-http.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/smoke-broad-http.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/smoke-cli-binary.mjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/smoke-cli-binary.mjs:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/smoke-cli.mjs:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/smoke-cli.mjs:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/smoke-diagnostic-runtime.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/smoke-diagnostic-runtime.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/smoke-live-all-providers.mjs:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/smoke-live-all-providers.mjs:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/smoke-live-llm.mjs:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/smoke-live-llm.mjs:21 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 129 placeholder/mock markers across 77 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 quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Maintenance conf 1.00 32 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 420 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 quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/api/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/api/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/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.
apps/cli/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/a2a/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/a2a/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/agent-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/agent-core/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/auth/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/auth/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/autoconfigure/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/autoconfigure/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/browser/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/browser/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/cache/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/cache/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/calendar/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/calendar/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/db/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/db/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/macos/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/macos/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/mcp/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/mcp/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/memory/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/memory/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/messaging/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/messaging/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/model/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/model/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/multi-agent/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/multi-agent/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/observability/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/observability/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/policy/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/policy/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/recall/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/recall/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/resilience/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/resilience/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/runtime-settings/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/runtime-settings/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/runtime-state/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/runtime-state/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/scheduler/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/scheduler/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/skills/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/skills/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/tools/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/tools/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `fu_old` in packages/mcp/src/personal-followups-store.test.ts:131
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 `hallucinations_v1` in packages/agent-core/src/sentence-groundedness.ts:26
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 `pb_legacy` in packages/autoconfigure/test/playbook-provider-lifecycle.test.ts:49
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 `rem_old` in apps/cli/test/program.test.ts:2237
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 `ship_v1` in packages/memory/src/memory-auto-extract.ts:132
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 `ship_v1` in packages/memory/test/memory.test.ts:1247
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 React Flow edge with `label=` but no project-wide edge-label CSS override — packages/mcp/src/smart-home.ts:225
React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…
Fq edge label no bg
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/api/src/index.ts:19
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 /admin/cache
`apps/api/src/admin-routes.ts` declares `DELETE /admin/cache` 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/admin/agent-specs/:id
`apps/api/src/agent-compat-routes.ts` declares `DELETE /api/admin/agent-specs/: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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/calendar/events/:id
`apps/api/src/calendar-routes.ts` declares `DELETE /api/calendar/events/: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/notes
`apps/api/src/notes-routes.ts` declares `DELETE /api/notes` 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/sessions/:sessionId
`apps/api/src/session-compat-routes.ts` declares `DELETE /api/sessions/:sessionId` 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: GET /admin/cache
`apps/api/src/admin-routes.ts` declares `GET /admin/cache` 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 /admin/metrics
`apps/api/src/admin-routes.ts` declares `GET /admin/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: GET /admin/resilience/circuit-breakers
`apps/api/src/admin-routes.ts` declares `GET /admin/resilience/circuit-breakers` 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 /admin/telemetry/recent
`apps/api/src/admin-routes.ts` declares `GET /admin/telemetry/recent` 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 /admin/telemetry/summary
`apps/api/src/admin-routes.ts` declares `GET /admin/telemetry/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/active-context
`apps/api/src/active-context-routes.ts` declares `GET /api/active-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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/agent-specs
`apps/api/src/agent-compat-routes.ts` declares `GET /api/admin/agent-specs` 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/admin/agent-specs/:id
`apps/api/src/agent-compat-routes.ts` declares `GET /api/admin/agent-specs/: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/admin/agent-specs/:id/system-prompt
`apps/api/src/agent-compat-routes.ts` declares `GET /api/admin/agent-specs/:id/system-prompt` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/debug/replay
`apps/api/src/admin-analytics-compat-routes.ts` declares `GET /api/admin/debug/replay` 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: GET /api/admin/debug/replay/:id
`apps/api/src/admin-analytics-compat-routes.ts` declares `GET /api/admin/debug/replay/: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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/metrics/latency/summary
`apps/api/src/admin-analytics-compat-routes.ts` declares `GET /api/admin/metrics/latency/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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/metrics/latency/timeseries
`apps/api/src/admin-analytics-compat-routes.ts` declares `GET /api/admin/metrics/latency/timeseries` 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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/muse/snapshot
`apps/api/src/admin-analytics-compat-routes.ts` declares `GET /api/admin/muse/snapshot` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/tools/accuracy
`apps/api/src/admin-analytics-compat-routes.ts` declares `GET /api/admin/tools/accuracy` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/tools/stats
`apps/api/src/admin-analytics-compat-routes.ts` declares `GET /api/admin/tools/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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/agent-notices/stream
`apps/api/src/agent-notices-routes.ts` declares `GET /api/agent-notices/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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/calendar/events
`apps/api/src/calendar-routes.ts` declares `GET /api/calendar/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: GET /api/calendar/providers
`apps/api/src/calendar-routes.ts` declares `GET /api/calendar/providers` 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/models
`apps/api/src/session-compat-routes.ts` declares `GET /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: GET /api/multi-agent/orchestrations
`apps/api/src/multi-agent-routes.ts` declares `GET /api/multi-agent/orchestrations` 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/multi-agent/orchestrations/:runId
`apps/api/src/multi-agent-routes.ts` declares `GET /api/multi-agent/orchestrations/:runId` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/multi-agent/orchestrations/stats
`apps/api/src/multi-agent-routes.ts` declares `GET /api/multi-agent/orchestrations/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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/notes/list
`apps/api/src/notes-routes.ts` declares `GET /api/notes/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/notes/providers
`apps/api/src/notes-routes.ts` declares `GET /api/notes/providers` 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/notes/read
`apps/api/src/notes-routes.ts` declares `GET /api/notes/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: GET /api/notes/search
`apps/api/src/notes-routes.ts` declares `GET /api/notes/search` 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/proactive/history
`apps/api/src/proactive-routes.ts` declares `GET /api/proactive/history` 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/sessions
`apps/api/src/session-compat-routes.ts` declares `GET /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: GET /api/sessions/:sessionId
`apps/api/src/session-compat-routes.ts` declares `GET /api/sessions/:sessionId` 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/sessions/:sessionId/export
`apps/api/src/session-compat-routes.ts` declares `GET /api/sessions/:sessionId/export` 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: GET /api/voice/providers
`apps/api/src/voice-routes.ts` declares `GET /api/voice/providers` 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 /admin/resilience/circuit-breakers/:name/reset
`apps/api/src/admin-routes.ts` declares `POST /admin/resilience/circuit-breakers/:name/reset` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/resilience/circuit-breakers/reset
`apps/api/src/admin-routes.ts` declares `POST /admin/resilience/circuit-breakers/reset` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/agent-specs
`apps/api/src/agent-compat-routes.ts` declares `POST /api/admin/agent-specs` 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/admin/task-memory/maintenance/purge-expired
`apps/api/src/admin-analytics-compat-routes.ts` declares `POST /api/admin/task-memory/maintenance/purge-expired` 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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/task-memory/maintenance/purge-terminal
`apps/api/src/admin-analytics-compat-routes.ts` declares `POST /api/admin/task-memory/maintenance/purge-terminal` 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 remov…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/calendar/events
`apps/api/src/calendar-routes.ts` declares `POST /api/calendar/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: POST /api/multi-agent/orchestrate
`apps/api/src/multi-agent-routes.ts` declares `POST /api/multi-agent/orchestrate` 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/multi-agent/orchestrate/stream
`apps/api/src/multi-agent-routes.ts` declares `POST /api/multi-agent/orchestrate/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 documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/notes/append
`apps/api/src/notes-routes.ts` declares `POST /api/notes/append` 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/notes/save
`apps/api/src/notes-routes.ts` declares `POST /api/notes/save` 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/voice/stt
`apps/api/src/voice-routes.ts` declares `POST /api/voice/stt` 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/voice/tts
`apps/api/src/voice-routes.ts` declares `POST /api/voice/tts` 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/admin/agent-specs/:id
`apps/api/src/agent-compat-routes.ts` declares `PUT /api/admin/agent-specs/: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/cli/src/chat-ink.ts (1516 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/cli/src/commands-ask.ts (2740 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/cli/src/commands-daemon.test.ts (1420 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/cli/src/commands-daemon.ts (1245 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/cli/src/commands-today.ts (1240 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/cli/test/program.test.ts (9057 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/agent-core/src/council.test.ts (1076 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/agent-core/src/knowledge-recall.ts (1963 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/agent-core/test/agent-runtime.test.ts (3347 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/agent-core/test/playbook.test.ts (1315 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/autoconfigure/src/index.ts (1218 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/autoconfigure/test/autoconfigure.test.ts (1301 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/mcp/test/mcp.test.ts (9338 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/memory/test/memory.test.ts (1458 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/messaging/test/messaging.test.ts (1411 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/model/test/model.test.ts (2138 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/observability/test/observability.test.ts (1484 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/tools/test/tools.test.ts (1568 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/eval-tool-selection.mjs (1391 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/smoke-broad-http.mjs (1110 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/f29698de-a3d7-4c1f-8403-d0cdd611fac9/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f29698de-a3d7-4c1f-8403-d0cdd611fac9/

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.