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

taskclaw/taskclaw

https://github.com/taskclaw/taskclaw · scanned 2026-06-16 00:30 UTC (2 months, 2 weeks ago)

275 raw signals (0 security + 275 graph)

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

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 246 actionable findings from 1 signal source. 29 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
44.8
/100
Security checks
45
0 findings
System graph
45
100.0% cov · 246 findings
Critical
3
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 3 High 11 Medium 64 Low 104 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 246 Crowd 0 Layer: Software 22 Frontend 70 Network 2 Hardware 2 Security 15 Cicd 4 Quality 73 Api 58
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 44.8/100 with 100.0% coverage. It contains 4255 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 275 findings — concentrated in quality (73), frontend (70), api (58). Risk profile is high: 9 critical, 11 high, 79 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 180 of 246 actionable findings. 275 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 3 occurrences Possible secret in backend/scripts/auth-e2e-smoke.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 39, 51, 56
backend/scripts/auth-e2e-smoke.ts:39, 51, 56 (3 hits)
critical System graph security Secrets conf 1.00 3 occurrences Possible secret in scripts/install.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 429, 430, 488
scripts/install.sh:429, 430, 488 (3 hits)
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/skills/app-store-optimization/references/keyword-research-guide.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/skills/app-store-optimization/references/keyword-research-guide.md:330 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/skills/dev-setup/SKILL.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/skills/dev-setup/SKILL.md:522 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.anthropic.com/v1/models (backend/src/backbone/adapters/anthropic.adapter.ts:49)
`backend/src/backbone/adapters/anthropic.adapter.ts:49` calls `GET https://api.anthropic.com/v1/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/models` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.example.com/data (backend/src/common/utils/retry.util.ts:69)
`backend/src/common/utils/retry.util.ts:69` calls `GET https://api.example.com/data` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.example.com/data` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.replicate.com/v1/predictions/${prediction_id} (backend/src/ai-assistant/tools/replicate-poll.tool.ts:16)
`backend/src/ai-assistant/tools/replicate-poll.tool.ts:16` calls `GET https://api.replicate.com/v1/predictions/${prediction_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.replicate.com/v1/predictions…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (backend/src/backbone/adapters/anthropic.adapter.ts:126)
`backend/src/backbone/adapters/anthropic.adapter.ts:126` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.elevenlabs.io/v1/text-to-speech/${voice_id} (backend/src/ai-assistant/tools/elevenlabs-tts.tool.ts:38)
`backend/src/ai-assistant/tools/elevenlabs-tts.tool.ts:38` calls `POST https://api.elevenlabs.io/v1/text-to-speech/${voice_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/text-to-spee…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.elevenlabs.io/v1/voices/add (backend/src/ai-assistant/tools/elevenlabs-clone-voice.tool.ts:81)
`backend/src/ai-assistant/tools/elevenlabs-clone-voice.tool.ts:81` calls `POST https://api.elevenlabs.io/v1/voices/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/voices/add` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.replicate.com/v1/files (backend/src/ai-assistant/tools/upload-to-storage.tool.ts:33)
`backend/src/ai-assistant/tools/upload-to-storage.tool.ts:33` calls `POST https://api.replicate.com/v1/files` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.replicate.com/v1/files` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.replicate.com/v1/predictions (backend/src/ai-assistant/tools/replicate-predict.tool.ts:31)
`backend/src/ai-assistant/tools/replicate-predict.tool.ts:31` calls `POST https://api.replicate.com/v1/predictions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.replicate.com/v1/predictions` If this poi…
Dangling fetchFetch
high System graph cicd CI/CD security conf 1.00 GitHub Action tracks a moving branch
trufflesecurity/trufflehog@main can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci.yml:42 CI/CD securitySupply chainGithub actions
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/app/(marketing)/layout.tsx:41
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/app/dashboard/cockpit/page.tsx:1288
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/app/layout.tsx:177
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/components/boards/board-ai-chat.tsx:498
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/components/integrations/integration-test-chat.tsx:262
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/components/tasks/task-ai-chat.tsx:382
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/components/theme/GlobalThemeInjector.tsx:43
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/kit/shadcn/chart.tsx:81
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 — backend/src/adapters/clickup/clickup.adapter.ts:267
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 — backend/src/ai-assistant/tools/elevenlabs-clone-voice.tool.ts:81
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 — backend/src/ai-assistant/tools/upload-to-storage.tool.ts:33
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 — backend/src/common/utils/retry.util.ts:69
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 — backend/src/integrations/oauth/oauth.service.ts:267
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 — backend/src/mcp/api-client.ts:37
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 — backend/src/memory/adapters/obsidian-memory.adapter.ts:205
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/eslint.config.mjs: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/app/(auth)/actions.ts:23
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/app/admin/settings/actions.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 — frontend/src/app/api/[...path]/route.ts:34
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/app/api/events/route.ts:22
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/app/dashboard/agents/actions.ts:56
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/app/dashboard/chat/actions.ts:97
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/app/dashboard/factory/actions.ts:35
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/app/dashboard/inbox/actions.ts:67
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/app/dashboard/knowledge/actions.ts:34
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/app/dashboard/pods/actions.ts:272
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/app/dashboard/pods/bundle-actions.ts:33
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/app/dashboard/settings/agent-sync/actions.ts:118
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/app/dashboard/settings/memory/actions.ts:190
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/app/dashboard/settings/skills/actions.ts:43
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/app/dashboard/skills-actions.ts:67
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/app/dashboard/tasks/actions.ts:49
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/hooks/use-orchestration-events.ts:64
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/kit/makerkit/version-updater.tsx: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 — frontend/src/lib/auth.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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/evals/scenarios/orchestration/S004-autonomy-dial.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/evals/scenarios/orchestration/S004-autonomy-dial.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/evals/scenarios/S001-cockpit-idle-live-transition.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/evals/scenarios/S001-cockpit-idle-live-transition.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.json
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/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json
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/settings.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/board-architect/references/manifest_schema.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/skills/board-architect/references/manifest_schema.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/board-architect/references/step_types.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/skills/board-architect/references/step_types.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/dev-setup/references/env-vars.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/skills/dev-setup/references/env-vars.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/taskclaw-builder/references/workflow.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/skills/taskclaw-builder/references/workflow.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/taskclaw-shared/bundle_format.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/skills/taskclaw-shared/bundle_format.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.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.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 14 occurrences GitHub Action is tag-pinned rather than SHA-pinned
amannn/action-semantic-pull-request@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 14 locations
.github/workflows/docker-publish.yml:28, 31, 34, 49, 73, 76, 79, 94 (8 hits)
.github/workflows/release.yml:26, 32, 35, 47, 59 (5 hits)
.github/workflows/ci.yml:17
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/app/(marketing)/layout.tsx:41
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/app/(marketing)/layout.tsx:41 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/app/dashboard/cockpit/page.tsx:1288
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/app/dashboard/cockpit/page.tsx:1288 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/app/layout.tsx:177
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/app/layout.tsx:177 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/boards/board-ai-chat.tsx:498
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/boards/board-ai-chat.tsx:498 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/tasks/task-ai-chat.tsx:382
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/tasks/task-ai-chat.tsx:382 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/theme/GlobalThemeInjector.tsx:43
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/theme/GlobalThemeInjector.tsx:43 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/kit/shadcn/chart.tsx:81
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/kit/shadcn/chart.tsx:81 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/architecture-visual.html:659
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/architecture-visual.html:659 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/src/backbone/adapters/claude-code.adapter.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/src/backbone/adapters/claude-code.adapter.ts:2 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 283 placeholder/mock markers across 101 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 10 in use
Port 10 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docker-compose.quickstart.yml Ports
medium System graph network Security conf 1.00 Privileged port 1000 in use
Port 1000 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docker-compose.yml 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
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
18 test file(s) for 733 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — frontend/src/app/dashboard/settings/skills/page.tsx:543
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Integrity conf 1.00 26 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALLOWED_ORIGINS`, `ANTHROPIC_API_KEY`, `BRAND_NAME`, `COOKIE_SECURE`, `INTERNAL_API_URL`, `NEXT_PUBLIC_BRAND_ICON_LOGO`, `NEXT_PUBLIC_BRAND_IMAGE_PATH`, `NEXT_PUBLIC_ENABLE_SIDEBAR_TRIGGER` + 18 more. Add them (with a placeholder/comment) to .env.…
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 138 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 hardware Supply chain conf 1.00 4 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
2 files, 4 locations
backend/Dockerfile:2, 13 (2 hits)
frontend/Dockerfile:2, 23 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 8 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 8 locations
.github/workflows/ci.yml:37, 55, 58, 86, 89 (5 hits)
.github/workflows/docker-publish.yml:25, 70 (2 hits)
.github/workflows/release.yml:20
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: .claude/skills/social-media-analyzer/scripts/calculate_metrics.py:safe_divide, .claude/skills/campaign-analytics/scripts/funnel_analyzer.py:safe_divide, .claude/skills/campaign-analytics/scripts/attribution_analyzer.py:safe_divide, .claude/skills/camp…
duplicatesduplication
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/openclaw-plugin/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/openclaw-plugin/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `eleven_multilingual_v2` in backend/src/ai-assistant/tools/elevenlabs-tts.tool.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 `post_copy` in .claude/skills/social-media-analyzer/scripts/calculate_metrics.py:125
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: adapt_keywords
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/localization_helper.py:191
low System graph software Dead code conf 1.00 Possibly dead Python function: analyze_all
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/social-media-analyzer/scripts/calculate_metrics.py:141
low System graph software Dead code conf 1.00 Possibly dead Python function: analyze_competitor_set
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/competitor_analyzer.py:560
low System graph software Dead code conf 1.00 Possibly dead Python function: analyze_keyword_set
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/keyword_analyzer.py:395
low System graph software Dead code conf 1.00 Possibly dead Python function: analyze_reviews
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/review_analyzer.py:693
low System graph software Dead code conf 1.00 Possibly dead Python function: calculate_aso_score
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/aso_scorer.py:458
low System graph software Dead code conf 1.00 Possibly dead Python function: create_update_plan
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/launch_checklist.py:98
low System graph software Dead code conf 1.00 Possibly dead Python function: extract_keywords_from_text
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/keyword_analyzer.py:194
low System graph software Dead code conf 1.00 Possibly dead Python function: find_long_tail_opportunities
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/keyword_analyzer.py:144
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_insights
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/social-media-analyzer/scripts/analyze_performance.py:122
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_launch_checklist
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/launch_checklist.py:722
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_response_templates
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/review_analyzer.py:341
low System graph software Dead code conf 1.00 Possibly dead Python function: identify_gaps
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/competitor_analyzer.py:125
low System graph software Dead code conf 1.00 Possibly dead Python function: optimize_app_metadata
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/metadata_optimizer.py:549
low System graph software Dead code conf 1.00 Possibly dead Python function: optimize_launch_timing
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/launch_checklist.py:143
low System graph software Dead code conf 1.00 Possibly dead Python function: plan_localization_strategy
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/localization_helper.py:550
low System graph software Dead code conf 1.00 Possibly dead Python function: plan_seasonal_campaigns
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/launch_checklist.py:187
low System graph software Dead code conf 1.00 Possibly dead Python function: track_sentiment_trends
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/review_analyzer.py:293
low System graph software Dead code conf 1.00 Possibly dead Python function: translate_metadata
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/localization_helper.py:118
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_app_store_compliance
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/launch_checklist.py:65
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_character_limits
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/metadata_optimizer.py:229
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_translations
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/app-store-optimization/scripts/localization_helper.py:242
low System graph frontend Frontend quality conf 1.00 React Flow <Controls> without dark theming — frontend/src/components/pods/pod-board-canvas.tsx:387
`<Controls>` ships with white buttons. Override `.react-flow__controls` and `.react-flow__controls-button` in your stylesheet or pass a styled wrapper. Why: P1 in CHECKLIST.md — vendor defaults bleed light through. Rule id: fq.controls.no-bg
Fq controls no bg
low System graph frontend Frontend quality conf 1.00 React Flow <MiniMap> without dark background — frontend/src/components/pods/pod-board-canvas.tsx:388
A bare <MiniMap> renders with the vendor's white default in dark themes. Wrap the canvas in a class that overrides `.react-flow__minimap` background, or pass an explicit `style`/`maskColor`/`bgColor`. Why: P1 in CHECKLIST.md — vendor defaults bleed light through. Rule id: fq.minimap.no-bg
Fq minimap 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 — backend/scripts/auth-e2e-smoke.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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/categories-pilot-smoke.ts:14
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 — backend/scripts/db-smoke.ts:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/setup-supabase.ts:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/sources-pilot-smoke.ts:9
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 — backend/src/common/utils/encryption.util.ts:33
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 — backend/src/teams/teams.service.ts:135
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 — backend/test-openclaw-ws.ts:59
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/app/(auth)/actions.ts:44
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/app/dashboard/chat/actions.ts:22
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/components/marketing/CustomerValidatorModal.tsx:269
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/components/tasks/task-ai-chat.tsx:123
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/lib/i18n/i18n.server.ts:28
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/test-supabase.js: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 api Wiring conf 1.00 Unused endpoint: DELETE /accounts/:accountId/api-keys/:keyId
`backend/src/auth/api-keys/api-keys.controller.ts` declares `DELETE /accounts/:accountId/api-keys/:keyId` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /accounts/:accountId/board-routing/routes/:routeId
`backend/src/board-routing/board-routing.controller.ts` declares `DELETE /accounts/:accountId/board-routing/routes/:routeId` 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 — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /accounts/:accountId/integrations/:refId
`backend/src/integrations/integrations.controller.ts` declares `DELETE /accounts/:accountId/integrations/:refId` 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: DELETE /accounts/:accountId/integrations/connections/:connId
`backend/src/integrations/integrations.controller.ts` declares `DELETE /accounts/:accountId/integrations/connections/:connId` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /accounts/:accountId/integrations/definitions/:defId
`backend/src/integrations/integrations.controller.ts` declares `DELETE /accounts/:accountId/integrations/definitions/:defId` 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 — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /accounts/:accountId/syncs/:id
`backend/src/syncs/syncs.controller.ts` declares `DELETE /accounts/:accountId/syncs/: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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /admin/users/:id
`backend/src/users/admin-users.controller.ts` declares `DELETE /admin/users/: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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/board-routing/dags
`backend/src/board-routing/board-routing.controller.ts` declares `GET /accounts/:accountId/board-routing/dags` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/board-routing/dags/:dagId
`backend/src/board-routing/board-routing.controller.ts` declares `GET /accounts/:accountId/board-routing/dags/:dagId` 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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/board-routing/routes
`backend/src/board-routing/board-routing.controller.ts` declares `GET /accounts/:accountId/board-routing/routes` 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: GET /accounts/:accountId/board-routing/routes/:routeId
`backend/src/board-routing/board-routing.controller.ts` declares `GET /accounts/:accountId/board-routing/routes/:routeId` 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 — consid…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/integrations/connections
`backend/src/integrations/integrations.controller.ts` declares `GET /accounts/:accountId/integrations/connections` 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 remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/integrations/connections/:connId
`backend/src/integrations/integrations.controller.ts` declares `GET /accounts/:accountId/integrations/connections/:connId` 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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/integrations/definitions
`backend/src/integrations/integrations.controller.ts` declares `GET /accounts/:accountId/integrations/definitions` 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 remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/integrations/definitions/:defId
`backend/src/integrations/integrations.controller.ts` declares `GET /accounts/:accountId/integrations/definitions/:defId` 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 — consid…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/integrations/oauth/:defId/authorize
`backend/src/integrations/oauth/oauth.controller.ts` declares `GET /accounts/:accountId/integrations/oauth/:defId/authorize` 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 — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/orchestrations/:oid
`backend/src/orchestration/orchestration.controller.ts` declares `GET /accounts/:accountId/orchestrations/:oid` 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 removin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/sync/status
`backend/src/sync/sync.controller.ts` declares `GET /accounts/:accountId/sync/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/syncs/:id
`backend/src/syncs/syncs.controller.ts` declares `GET /accounts/:accountId/syncs/: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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /accounts/:accountId/syncs/:id/runs
`backend/src/syncs/syncs.controller.ts` declares `GET /accounts/:accountId/syncs/:id/runs` 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 /accounts/:accountId/syncs/:id/skills
`backend/src/syncs/syncs.controller.ts` declares `GET /accounts/:accountId/syncs/:id/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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/users/:id
`backend/src/users/admin-users.controller.ts` declares `GET /admin/users/: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 /auth/me
`backend/src/auth/auth.controller.ts` declares `GET /auth/me` 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 /integrations/oauth/callback
`backend/src/integrations/oauth/oauth.controller.ts` declares `GET /integrations/oauth/callback` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /users/me
`backend/src/users/users.controller.ts` declares `GET /users/me` 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 /users/me/preferences
`backend/src/users/users.controller.ts` declares `GET /users/me/preferences` 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 /accounts/:accountId/board-routing/routes/:routeId
`backend/src/board-routing/board-routing.controller.ts` declares `PATCH /accounts/:accountId/board-routing/routes/:routeId` 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 — cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /accounts/:accountId/integrations/connections/:connId
`backend/src/integrations/integrations.controller.ts` declares `PATCH /accounts/:accountId/integrations/connections/:connId` 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 — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /accounts/:accountId/integrations/definitions/:defId
`backend/src/integrations/integrations.controller.ts` declares `PATCH /accounts/:accountId/integrations/definitions/:defId` 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 — cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /accounts/:accountId/syncs/:id
`backend/src/syncs/syncs.controller.ts` declares `PATCH /accounts/:accountId/syncs/: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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /users/me/preferences
`backend/src/users/users.controller.ts` declares `PATCH /users/me/preferences` 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 /accounts/:accountId/board-routing/decompose-goal
`backend/src/board-routing/board-routing.controller.ts` declares `POST /accounts/:accountId/board-routing/decompose-goal` 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 — consid…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /accounts/:accountId/board-routing/routes
`backend/src/board-routing/board-routing.controller.ts` declares `POST /accounts/:accountId/board-routing/routes` 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 /accounts/:accountId/integrations/connections
`backend/src/integrations/integrations.controller.ts` declares `POST /accounts/:accountId/integrations/connections` 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 rem…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /accounts/:accountId/integrations/connections/:connId/health-check
`backend/src/integrations/integrations.controller.ts` declares `POST /accounts/:accountId/integrations/connections/:connId/health-check` 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 dea…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /accounts/:accountId/integrations/connections/:connId/toggle
`backend/src/integrations/integrations.controller.ts` declares `POST /accounts/:accountId/integrations/connections/:connId/toggle` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /accounts/:accountId/integrations/definitions
`backend/src/integrations/integrations.controller.ts` declares `POST /accounts/:accountId/integrations/definitions` 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 rem…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /accounts/:accountId/orchestrations/:oid/approve
`backend/src/orchestration/orchestration.controller.ts` declares `POST /accounts/:accountId/orchestrations/:oid/approve` 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 — conside…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /accounts/:accountId/orchestrations/:oid/reject
`backend/src/orchestration/orchestration.controller.ts` declares `POST /accounts/:accountId/orchestrations/:oid/reject` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /accounts/:accountId/sync/sources/:sourceId
`backend/src/sync/sync.controller.ts` declares `POST /accounts/:accountId/sync/sources/:sourceId` 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: POST /accounts/:accountId/syncs/:id/run
`backend/src/syncs/syncs.controller.ts` declares `POST /accounts/:accountId/syncs/:id/run` 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: POST /auth/forgot-password
`backend/src/auth/auth.controller.ts` declares `POST /auth/forgot-password` 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 /auth/login
`backend/src/auth/auth.controller.ts` declares `POST /auth/login` 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 /auth/logout
`backend/src/auth/auth.controller.ts` declares `POST /auth/logout` 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 /auth/refresh
`backend/src/auth/auth.controller.ts` declares `POST /auth/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: POST /auth/reset-password
`backend/src/auth/auth.controller.ts` declares `POST /auth/reset-password` 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 /auth/signup
`backend/src/auth/auth.controller.ts` declares `POST /auth/signup` 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 /auth/update-password
`backend/src/auth/auth.controller.ts` declares `POST /auth/update-password` 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 /admin/users/:id/role
`backend/src/users/admin-users.controller.ts` declares `PUT /admin/users/:id/role` 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 /admin/users/:id/status
`backend/src/users/admin-users.controller.ts` declares `PUT /admin/users/:id/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/src/conversations/conversations.service.ts (3182 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/src/db/schema.ts (2058 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/app/dashboard/cockpit/page.tsx (1861 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/app/dashboard/settings/categories/page.tsx (1682 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/components/tasks/task-detail-panel.tsx (869 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/829afcb7-c71b-410f-b021-1e33a7e73fc2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/829afcb7-c71b-410f-b021-1e33a7e73fc2/

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.