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

vinceblank/agent-tempo

https://github.com/vinceblank/agent-tempo · scanned 2026-06-16 00:50 UTC (2 months, 1 week ago)

346 raw signals (0 security + 346 graph)

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

Complete repo analysis

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

JSON
Combined
36.3
/100
Security checks
36
0 findings
System graph
36
100.0% cov · 320 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 10 Medium 44 Low 47 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 320 Crowd 0 Layer: Frontend 28 Hardware 5 Security 34 Cicd 3 Quality 245 Api 5
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 36.3/100 with 100.0% coverage. It contains 3498 nodes across 19 cross-layer flows, written primarily in mixed languages. Engine surfaced 346 findings — concentrated in quality (245), security (34), cicd (29). Risk profile is high: 0 critical, 10 high, 44 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 98 of 320 actionable findings. 346 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.

high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/players/${E}/${P}/inner (tests/http/inner-loop-integration.test.ts:132)
`tests/http/inner-loop-integration.test.ts:132` calls `GET http://127.0.0.1:${port}/v1/players/${E}/${P}/inner` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/players/<p>/<p>/inner` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${server.port}/v1/players/${E}/${P}/inner (tests/http/inner-loop-integration.test.ts:194)
`tests/http/inner-loop-integration.test.ts:194` calls `GET http://127.0.0.1:${server.port}/v1/players/${E}/${P}/inner` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/players/<p>/<p>/inner` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${server.port}/v1/players/${E}/${P}/inner (tests/http/inner-loop-integration.test.ts:208)
`tests/http/inner-loop-integration.test.ts:208` calls `GET http://127.0.0.1:${server.port}/v1/players/${E}/${P}/inner` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/players/<p>/<p>/inner` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/${pkgName}/latest (src/cli/startup.ts:281)
`src/cli/startup.ts:281` calls `GET https://registry.npmjs.org/${pkgName}/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/registry.npmjs.org/<p>/latest` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/cli/commands.ts:1742
Found a known-risky pattern (exec_used). Review and replace if possible.
src/cli/commands.ts:1742 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/cli/daemon.ts:713
Found a known-risky pattern (exec_used). Review and replace if possible.
src/cli/daemon.ts:713 Exec used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in src/pi/headless.ts:46
Found a known-risky pattern (new_function_used). Review and replace if possible.
src/pi/headless.ts:46 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in src/tools/recruit.ts:26
Found a known-risky pattern (new_function_used). Review and replace if possible.
src/tools/recruit.ts:26 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in src/tui/ink-loader.ts:37
Found a known-risky pattern (new_function_used). Review and replace if possible.
src/tui/ink-loader.ts:37 New function used
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: dashboard/.env.overflow
`dashboard/.env.overflow` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
dashboard/.env.overflow ConfigEnv fileRuntime env
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — dashboard/src/lib/client.ts:393
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 — dashboard/src/screens/OverflowShim.tsx:136
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 — docs/design/dashboard-handoff/project/design-canvas.jsx:63
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/gh-app-token.js:71
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 — src/client/subscribe.ts:16
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 — src/http/snapshot.ts:180
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 — src/workflows/maestro.ts:723
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 — test/pi-mission-control-actions.test.ts:3
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: CLAUDE.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
CLAUDE.md:215 Supply chainClaude instruction
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 hardware Security conf 1.00 Dockerfile runs as root: test/fixtures/multi-host/daemon-a/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: test/fixtures/multi-host/daemon-b/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Frontend route `/ensemble/:id` has no Link/navigate to it — dashboard/tests/notifications/provider.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `ensemble/:id/player/:playerId` has no Link/navigate to it — dashboard/tests/router.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
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/update-overflow-snapshots.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/dashboard-handoff/project/web-design-system.html:1622
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/dashboard-handoff/project/web-design-system.html:1622 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-components-css-sync.ts:38
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-components-css-sync.ts:38 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-pi-drift.js:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-pi-drift.js:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/run-shard.ts:33
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/run-shard.ts:33 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/verify-daemon-isolation-guard.ts:33
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/verify-daemon-isolation-guard.ts:33 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/verify-tarball.js:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/verify-tarball.js:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/activities/hard-terminate.ts:27
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/activities/hard-terminate.ts:27 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/adapters/claude-code-headless/adapter.ts:41
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/adapters/claude-code-headless/adapter.ts:41 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/adapters/claude-code-headless/pre-flight.ts:29
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/adapters/claude-code-headless/pre-flight.ts:29 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/adapters/opencode/adapter.ts:33
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/adapters/opencode/adapter.ts:33 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/adapters/opencode/helpers.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/adapters/opencode/helpers.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/commands.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/daemon-command.ts:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/daemon-command.ts:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/daemon.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/daemon.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/dashboard-command.ts:30
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/dashboard-command.ts:30 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/ensure-infra.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/ensure-infra.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/mcp.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/mcp.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/preflight.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/preflight.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/sa-preflight.ts:34
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/sa-preflight.ts:34 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/startup.ts:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/startup.ts:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/upgrade-command.ts:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/upgrade-command.ts:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/daemon-adapter-versions.ts:35
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/daemon-adapter-versions.ts:35 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/git-info.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/git-info.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/spawn.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/spawn.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/utils/sdk-probe.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/utils/sdk-probe.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/utils/worktree.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/utils/worktree.ts:7 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 249 placeholder/mock markers across 68 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph 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 85 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 27 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-node@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 27 locations
.github/workflows/ci.yml:120, 131, 213, 223, 235, 265, 291, 297, +9 more (17 hits)
.github/workflows/release.yml:39, 56, 93, 119, 175 (5 hits)
.github/workflows/update-overflow-snapshots.yml:72, 78, 84, 92, 169 (5 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `byOld` in test/integration.test.ts:144
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 `dstLegacy` in src/cli/daemon-command.ts:421
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 `pinnedToOld` in test/destroy.test.ts: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 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 — scripts/check-components-css-sync.ts:153
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-no-stale-scaffold.js:86
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-no-stray-src-js.js:68
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-pi-drift.js:68
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-surface-drift.js:200
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/lint-skip-reasons.js:80
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/repro/777-signal-buffer-race.js:49
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/run-shard.ts:92
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/strip-mock-adapter.js:42
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/verify-daemon-isolation-guard.ts:69
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/verify-tarball.js: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 — src/cli/commands.ts:230
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 — src/cli/config-command.ts:116
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 — src/cli/daemon-command.ts:308
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 — src/cli/help-text.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 — src/cli/output.ts:13
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 — src/cli/preflight.ts:68
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/cli/upgrade-command.ts:48
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 — src/cli/upgrade-to-2-command.ts:63
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 — test/helpers.ts:241
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 — tests/adapters/mock/build-exclusion.test.ts:98
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 — tests/http/dashboard-handler.test.ts:37
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: POST /v1/ensembles
`src/pi/mission-control/actions.ts` declares `POST /v1/ensembles` 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: src/activities/outbox.ts (1284 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/adapters/base.ts (1392 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/cli/commands.ts (2891 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/cli/daemon.ts (1235 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/client/core.ts (1536 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/daemon.ts (1503 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pi/mission-control/extension.ts (1132 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/spawn.ts (1550 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/tui/App.tsx (1917 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/tui/commands.ts (1615 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/workflows/session.ts (2194 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/activities.test.ts (1624 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/helpers.ts (1735 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/tools.test.ts (1495 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/tui-reducer.test.ts (1112 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/a0522150-cf23-44d5-a541-8f841c9b04b1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a0522150-cf23-44d5-a541-8f841c9b04b1/

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.