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

yourpersonalagent/ypa

https://github.com/yourpersonalagent/ypa · scanned 2026-06-16 01:08 UTC (2 months, 1 week ago)

662 raw signals (0 security + 662 graph)

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

Complete repo analysis

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

JSON
Combined
61.0
/100
Security checks
61
0 findings
System graph
61
100.0% cov · 662 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 7 Medium 121 Low 112 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 662 Crowd 0 Layer: Software 15 Frontend 31 Network 1 Security 59 Quality 499 Api 57
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 61.0/100 with 100.0% coverage. It contains 6918 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 662 findings — concentrated in quality (499), security (59), api (57). Risk profile is high: 0 critical, 7 high, 121 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 240 of 662 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 /__rewind/api/edits?limit=1 (frontend/src/forge-bar/forge-state.ts:79)
`frontend/src/forge-bar/forge-state.ts:79` calls `GET /__rewind/api/edits?limit=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/__rewind/api/edits` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /__rewind/api/edits?limit=50 (frontend/src/layouts/full/code/panels/right-panels.tsx:59)
`frontend/src/layouts/full/code/panels/right-panels.tsx:59` calls `GET /__rewind/api/edits?limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/__rewind/api/edits` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/system-preview?${qs.toString()} (frontend/src/panels/GlobalContextPanel.tsx:214)
`frontend/src/panels/GlobalContextPanel.tsx:214` calls `GET /v1/system-preview?${qs.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/system-preview` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.llm-prices.com/current-v1.json (frontend/src/prefs/TabModels.tsx:717)
`frontend/src/prefs/TabModels.tsx:717` calls `GET https://www.llm-prices.com/current-v1.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.llm-prices.com/current-v1.json` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /__rewind/api/restore/${encodeURIComponent(id)} (frontend/src/forge-bar/forge-state.ts:114)
`frontend/src/forge-bar/forge-state.ts:114` calls `POST /__rewind/api/restore/${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/__rewind/api/restore/<p>` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.github.com/user/repos (bridge/modules/files-github/lib.ts:604)
`bridge/modules/files-github/lib.ts:604` calls `POST https://api.github.com/user/repos` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/user/repos` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/audio/speech (bridge/modules/audio-tts-openai/index.ts:98)
`bridge/modules/audio-tts-openai/index.ts:98` calls `POST https://api.openai.com/v1/audio/speech` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/audio/speech` If this points at an external A…
Dangling fetchFetch
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/chat/chat-streaming.ts:312
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 — frontend/src/chat/MessageList.tsx:2
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 — frontend/src/modules/pet/chatReflow.ts:19
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 — frontend/src/modules/render/RenderView.tsx:11
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 — frontend/src/ToastStack.tsx:90
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 — bridge/models/fetch.ts:642
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 — bridge/modules/audio-tts-openai/index.ts:98
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 — bridge/modules/context-generator/auto-title.ts:292
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 — bridge/modules/context-generator/categorizer/llm.ts:106
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 — bridge/modules/context-generator/context-rag/embed/nvidia.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 — bridge/modules/context-generator/file-categorizer/llm.ts:88
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 — bridge/modules/observability-plus/debug.ts:1475
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 — bridge/modules/pet/lib/console.ts:510
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 — bridge/tools/exec.ts:333
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 — bridge/tools/security.ts:223
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 — frontend/src/api.ts:208
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 — frontend/src/chat/chat-participants.ts:156
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 — frontend/src/chat/QuickRagPicker.tsx:282
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 — frontend/src/context/HubContextSessionPicker.tsx: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 — frontend/src/context/HubRagTab.tsx:261
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 — frontend/src/forge-bar/forge-state.ts:114
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 — frontend/src/modals/BashConsole.tsx:211
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 — frontend/src/modals/FileManager.tsx:244
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 — frontend/src/modals/FilePicker.tsx:170
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 — frontend/src/modules/input-autocomplete/index.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 — frontend/src/modules/pet/components/PetQuickChat.tsx: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 — frontend/src/modules/pet/hatch/persist.ts:72
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 — frontend/src/modules/pet/store/petStore.ts:391
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 — frontend/src/modules/welcome-messages/ChatEmptyGreeting.tsx:83
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 — frontend/src/panels/GithubModal.tsx:107
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 — frontend/src/panels/triggers.ts:85
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 — frontend/src/prefs/TabApiKeys.tsx:403
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 — frontend/src/prefs/TabHarness.tsx:114
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 — frontend/src/prefs/TabMcp.tsx:346
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 — frontend/src/prefs/TabModules.tsx:309
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 — frontend/src/prefs/TabPrompts.tsx:11
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 — frontend/src/prefs/TabSearch.tsx:210
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 — frontend/src/prefs/TabTools.tsx:319
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 — frontend/src/session.ts:541
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 — frontend/src/SessionPicker.tsx:315
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 — frontend/src/workflows/workflow.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 — frontend/src/workflows/WorkflowPicker.tsx:26
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: bridge/modules/context-generator/skills/cwd-synthesize/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.
bridge/modules/context-generator/skills/cwd-synthesize/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: bridge/skills/ask-grok/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.
bridge/skills/ask-grok/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: bridge/skills/ask-llms/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.
bridge/skills/ask-llms/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: bridge/skills/create-workflow/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.
bridge/skills/create-workflow/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: bridge/skills/cwd-plugin-creator/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.
bridge/skills/cwd-plugin-creator/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: bridge/skills/grill-with-docs/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.
bridge/skills/grill-with-docs/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: bridge/skills/review/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.
bridge/skills/review/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: bridge/skills/triage/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.
bridge/skills/triage/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: bridge/skills/writing-beats/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.
bridge/skills/writing-beats/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: bridge/skills/writing-fragments/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.
bridge/skills/writing-fragments/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: bridge/skills/writing-shape/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.
bridge/skills/writing-shape/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 'dangerous_innerhtml' in frontend/src/ToastStack.tsx:90
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/ToastStack.tsx:90 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in bridge/mcp/desktop-browser-server.win.js:660
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
bridge/mcp/desktop-browser-server.win.js:660 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/chat.ts:205
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/chat.ts:205 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/chat/AttachmentStrip.tsx:166
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/chat/AttachmentStrip.tsx:166 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/chat/chat-actions.ts:117
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/chat/chat-actions.ts:117 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/chat/chat-participants.ts:108
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/chat/chat-participants.ts:108 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/chat/chat-rendering.ts:66
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/chat/chat-rendering.ts:66 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/chat/chat-streaming.ts:55
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/chat/chat-streaming.ts:55 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/chat/chat-ui.ts:120
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/chat/chat-ui.ts:120 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/chat/chat-utils.ts:553
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/chat/chat-utils.ts:553 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/chat/MessageList.tsx:521
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/chat/MessageList.tsx:521 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/commands.ts:407
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/commands.ts:407 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/modules/voice/VoiceMode.tsx:189
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/modules/voice/VoiceMode.tsx:189 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/panels/debug-panel.ts:188
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/panels/debug-panel.ts:188 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/panels/DebugModal.tsx:74
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/panels/DebugModal.tsx:74 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/pickers/CapabilityBadges.tsx:126
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/pickers/CapabilityBadges.tsx:126 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/pickers/EffortSelector.tsx:72
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/pickers/EffortSelector.tsx:72 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/pickers/SysPromptEditor.tsx:201
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/pickers/SysPromptEditor.tsx:201 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/prefs/meta-section.ts:134
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/prefs/meta-section.ts:134 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/toast.ts:189
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/toast.ts:189 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/vendor.ts:56
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/vendor.ts:56 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/workflows/workflow.ts:355
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/workflows/workflow.ts:355 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/yha.html:153
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/yha.html:153 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in go-core/cmd/yha-rewind/main.go:1183
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
go-core/cmd/yha-rewind/main.go:1183 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in frontend/src/chat/chat-actions.ts:132
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
frontend/src/chat/chat-actions.ts:132 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in frontend/src/chat/chat-rendering.ts:168
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
frontend/src/chat/chat-rendering.ts:168 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/stores/sessionStore.ts:74
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/stores/sessionStore.ts:74 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/core/security.ts:215
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/core/security.ts:215 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/core/tui-link.ts:35
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/core/tui-link.ts:35 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/files/serve.ts:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/files/serve.ts:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/lib/deps.ts:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/lib/deps.ts:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/mcp/bash-console-server.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/mcp/bash-console-server.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/mcp/code-server.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/mcp/code-server.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/mcp/desktop-browser-server.js:34
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/mcp/desktop-browser-server.js:34 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/mcp/desktop-browser-server.win.js:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/mcp/desktop-browser-server.win.js:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/mcp/knowledge-server.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/mcp/knowledge-server.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/mcp/meta-bridge-server.js:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/mcp/meta-bridge-server.js:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/mcp/notebooklm-server.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/mcp/notebooklm-server.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/mcp/rclone-server.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/mcp/rclone-server.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/models/fetch.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/models/fetch.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/context-generator/tools/promote-log-decisions.mjs:33
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/context-generator/tools/promote-log-decisions.mjs:33 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/context-generator/tools/synth-status.mjs:38
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/context-generator/tools/synth-status.mjs:38 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/files-ftp/lib.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/files-ftp/lib.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/files-github/lib.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/files-github/lib.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/files-manager/lib.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/files-manager/lib.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/files-rclone/lib.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/files-rclone/lib.ts:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/mcp-client/lib/protocol.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/mcp-client/lib/protocol.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/mcp-client/lib/routes.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/mcp-client/lib/routes.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/multichat-partners/hermes.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/multichat-partners/hermes.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/observability-plus/debug.ts:538
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/observability-plus/debug.ts:538 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/pet/lib/hatch.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/pet/lib/hatch.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/modules/plugins-folder/data.ts:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/modules/plugins-folder/data.ts:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/providers/claude-run.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/providers/claude-run.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/providers/claude-stream.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/providers/claude-stream.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/providers/codex.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/providers/codex.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/routes/sessions.ts:976
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/routes/sessions.ts:976 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/routes/system.ts:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/routes/system.ts:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/server.ts:936
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/server.ts:936 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in bridge/tools/exec.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
bridge/tools/exec.ts:7 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — bridge/skills/google-workspace/scripts/google_api.py:108
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — bridge/skills/google-workspace/scripts/google_oauth.py:74
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — bridge/skills/google-workspace/scripts/gws_bridge.py:103
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — bridge/skills/google-workspace/scripts/setup.py:394
`urllib.request.urlopen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 452 placeholder/mock markers across 138 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 21 in use
Port 21 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
frontend/src/modals/RcloneModal.tsx Ports
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 Integrity conf 1.00 89 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ANTHROPIC_API_KEY`, `APPDATA`, `BACKEND_TARGET`, `BING_API_KEY`, `BRAVE_API_KEY`, `BRIDGE_INTERNAL_KEY`, `CLAUDE_BIN`, `CLAUDE_CONFIG_DIR` + 81 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 299 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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/modals/FilePicker.tsx:719
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 — frontend/src/modals/RcloneModal.tsx:1235
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 — frontend/src/prefs/PrefsModal.tsx:158
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 — frontend/src/Shell.tsx:66
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 Tests conf 1.00 Low test-to-source ratio
94 tests / 896 src (ratio 0.10).
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: bridge/skills/google-workspace/scripts/google_api.py:sheets_update, bridge/skills/google-workspace/scripts/google_api.py:sheets_append This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). …
duplicatesduplication
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: bridge/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.
bridge/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: frontend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
frontend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `hydrateFromLegacy` in frontend/src/main.ts:104
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 `hydrateFromLegacy` in frontend/src/stores/appStore.ts:182
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 `hydrateFromLegacy` in frontend/src/stores/graphStore.ts:86
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 `migrateLegacy` in bridge/mcp/knowledge-server.js:123
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 `sendViaLegacy` in frontend/src/chat/ChatInput.tsx:322
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 software Dead code conf 1.00 Possibly dead Python function: calendar_create
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:519
low System graph software Dead code conf 1.00 Possibly dead Python function: calendar_delete
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:557
low System graph software Dead code conf 1.00 Possibly dead Python function: calendar_list
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:465
low System graph software Dead code conf 1.00 Possibly dead Python function: contacts_list
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:600
low System graph software Dead code conf 1.00 Possibly dead Python function: docs_get
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:721
low System graph software Dead code conf 1.00 Possibly dead Python function: drive_search
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:573
low System graph software Dead code conf 1.00 Possibly dead Python function: gmail_get
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:279
low System graph software Dead code conf 1.00 Possibly dead Python function: gmail_labels
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:425
low System graph software Dead code conf 1.00 Possibly dead Python function: gmail_modify
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:439
low System graph software Dead code conf 1.00 Possibly dead Python function: gmail_reply
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:362
low System graph software Dead code conf 1.00 Possibly dead Python function: gmail_search
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:215
low System graph software Dead code conf 1.00 Possibly dead Python function: gmail_send
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:319
low System graph software Dead code conf 1.00 Possibly dead Python function: sheets_append
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:690
low System graph software Dead code conf 1.00 Possibly dead Python function: sheets_get
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:647
low System graph software Dead code conf 1.00 Possibly dead Python function: sheets_update
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bridge/skills/google-workspace/scripts/google_api.py:664
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — frontend/src/modules/pet/world/catalogPush.ts:53
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 — bridge/__tests__/file-manager.test.ts:34
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 — bridge/__tests__/image-extraction.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 — bridge/__tests__/internal-routes.test.ts:36
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 — bridge/__tests__/live-msg-delta.test.ts:26
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 — bridge/chat/openai-internal.ts:220
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 — bridge/config/harness-routes.ts:251
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 — bridge/core/auth.ts:413
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 — bridge/core/modules/watcher.ts:79
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — bridge/mcp/build_handoff.js:240
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 — bridge/modules/mcp-client/lib/materialize.ts:231
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 — bridge/modules/welcome-messages/lib.ts:162
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 — bridge/server.ts:855
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 — frontend/src/host/enabled-modules.ts:126
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 — frontend/src/modules/pet/store/petStore.ts:395
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 — frontend/src/panels/DebugModal.tsx:167
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 — frontend/src/panels/triggers.ts:325
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 /v1/api-keys/:id
`bridge/config/api-keys.ts` declares `DELETE /v1/api-keys/: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 /v1/config/codex-instances/:label
`bridge/config/presets-routes.ts` declares `DELETE /v1/config/codex-instances/:label` 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: DELETE /v1/config/grok-instances/:label
`bridge/config/presets-routes.ts` declares `DELETE /v1/config/grok-instances/:label` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /v1/config/instances/:label
`bridge/config/presets-routes.ts` declares `DELETE /v1/config/instances/:label` 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 /v1/config/presets/:name
`bridge/config/presets-routes.ts` declares `DELETE /v1/config/presets/: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: DELETE /v1/config/skills/:name
`bridge/config/presets-routes.ts` declares `DELETE /v1/config/skills/: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: DELETE /v1/config/skillSets/:name
`bridge/config/presets-routes.ts` declares `DELETE /v1/config/skillSets/: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: DELETE /v1/config/toolSets/:name
`bridge/config/presets-routes.ts` declares `DELETE /v1/config/toolSets/: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 /
`bridge/server.ts` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /brand.js
`bridge/server.ts` declares `GET /brand.js` 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 /local-image
`bridge/server.ts` declares `GET /local-image` 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 /v1/api-keys
`bridge/config/api-keys.ts` declares `GET /v1/api-keys` 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 /v1/api-keys/proxy-prefs
`bridge/config/api-keys.ts` declares `GET /v1/api-keys/proxy-prefs` 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 /v1/config-versions/list
`bridge/config/versions.ts` declares `GET /v1/config-versions/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 /v1/config/litellm-preview
`bridge/config/pricing-routes.ts` declares `GET /v1/config/litellm-preview` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /v1/config/skills/
`bridge/config/presets-routes.ts` declares `GET /v1/config/skills/` 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 /v1/config/skills/:name
`bridge/config/presets-routes.ts` declares `GET /v1/config/skills/: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 /v1/files/
`bridge/config/files-routes.ts` declares `GET /v1/files/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /v1/files/read
`bridge/config/files-routes.ts` declares `GET /v1/files/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 /v1/harness/detect
`bridge/config/harness-routes.ts` declares `GET /v1/harness/detect` 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 /v1/prefs/
`bridge/config/prefs-routes.ts` declares `GET /v1/prefs/` 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 /v1/telemetry
`bridge/server.ts` declares `GET /v1/telemetry` 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 /ypa
`bridge/server.ts` declares `GET /ypa` 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 /ypa.html
`bridge/server.ts` declares `GET /ypa.html` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /v1/api-keys/proxy-prefs
`bridge/config/api-keys.ts` declares `PATCH /v1/api-keys/proxy-prefs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /v1/config/pricing
`bridge/config/pricing-routes.ts` declares `PATCH /v1/config/pricing` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /v1/prefs/
`bridge/config/prefs-routes.ts` declares `PATCH /v1/prefs/` 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/api-keys
`bridge/config/api-keys.ts` declares `POST /v1/api-keys` 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/api-keys/:id/reset-usage
`bridge/config/api-keys.ts` declares `POST /v1/api-keys/:id/reset-usage` 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/config-versions/restore/:id
`bridge/config/versions.ts` declares `POST /v1/config-versions/restore/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/config-versions/snapshot-now
`bridge/config/versions.ts` declares `POST /v1/config-versions/snapshot-now` 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/config/activeSkillCategories
`bridge/config/presets-routes.ts` declares `POST /v1/config/activeSkillCategories` 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 /v1/files/exists
`bridge/config/files-routes.ts` declares `POST /v1/files/exists` 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/harness/refresh
`bridge/config/harness-routes.ts` declares `POST /v1/harness/refresh` 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 /v1/config/codex-instances/:label
`bridge/config/presets-routes.ts` declares `PUT /v1/config/codex-instances/:label` 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: PUT /v1/config/grok-instances/:label
`bridge/config/presets-routes.ts` declares `PUT /v1/config/grok-instances/:label` 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: PUT /v1/config/instances/:label
`bridge/config/presets-routes.ts` declares `PUT /v1/config/instances/:label` 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 /v1/config/presets/:name
`bridge/config/presets-routes.ts` declares `PUT /v1/config/presets/: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: PUT /v1/config/skills/:name
`bridge/config/presets-routes.ts` declares `PUT /v1/config/skills/: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: PUT /v1/config/skillSets/:name
`bridge/config/presets-routes.ts` declares `PUT /v1/config/skillSets/: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: PUT /v1/config/toolSets/:name
`bridge/config/presets-routes.ts` declares `PUT /v1/config/toolSets/: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: PUT /v1/files/write
`bridge/config/files-routes.ts` declares `PUT /v1/files/write` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /__rewind
`bridge/server.ts` declares `USE /__rewind` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /exchange
`bridge/server.ts` declares `USE /exchange` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /pets
`bridge/server.ts` declares `USE /pets` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /proxy/
`bridge/server.ts` declares `USE /proxy/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /proxy/browser
`bridge/server.ts` declares `USE /proxy/browser` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /proxy/serve/:id
`bridge/server.ts` declares `USE /proxy/serve/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /uploads
`bridge/server.ts` declares `USE /uploads` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /v1/
`bridge/server.ts` declares `USE /v1/` 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: bridge/config/config-core-routes.ts (1106 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: bridge/mcp/knowledge-server.js (1329 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: bridge/modules/observability-plus/debug.ts (1665 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: bridge/server.ts (1123 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/chat/chat-streaming.ts (2319 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/context/HubGeneratorTab.tsx (2010 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/modals/FileManager.tsx (1380 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/modals/RcloneModal.tsx (1289 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/modules/pet/hatch/FrameNudgeModal.tsx (1953 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/panels/debug-panel.ts (1668 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: go-core/cmd/yha-core/main.go (1328 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: go-core/cmd/yha-rewind/main.go (1498 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: go-core/internal/stream/route.go (2251 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: go-core/internal/stream/route_harness.go (1258 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/cfde0d7a-341d-4c19-a016-78e475a1d577/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/cfde0d7a-341d-4c19-a016-78e475a1d577/

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.