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

UnmanagedCode/code-conductor

https://github.com/UnmanagedCode/code-conductor · scanned 2026-06-16 00:45 UTC (2 months, 1 week ago)

143 raw signals (0 security + 143 graph)

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

Complete repo analysis

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

JSON
Combined
51.8
/100
Security checks
52
0 findings
System graph
52
77.8% cov · 143 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 7 Medium 21 Low 29 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 143 Crowd 0 Layer: Frontend 1 Security 16 Cicd 1 Quality 100 Api 25
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 51.8/100 with 77.8% coverage. It contains 1276 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 143 findings — concentrated in quality (100), api (25), security (16). Risk profile is high: 0 critical, 7 high, 21 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 57 of 143 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/.conduct/sessions (public/app.js:1488)
`public/app.js:1488` calls `GET /api/projects/.conduct/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/.conduct/sessions` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/projects (tests/eaddrinuse-retry.test.mjs:130)
`tests/eaddrinuse-retry.test.mjs:130` calls `GET http://127.0.0.1:${port}/api/projects` 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>/api/projects` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/projects (tests/eaddrinuse-retry.test.mjs:54)
`tests/eaddrinuse-retry.test.mjs:54` calls `GET http://127.0.0.1:${port}/api/projects` 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>/api/projects` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/projects (tests/server-restart.test.mjs:135)
`tests/server-restart.test.mjs:135` calls `GET http://127.0.0.1:${port}/api/projects` 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>/api/projects` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/projects (tests/server-restart.test.mjs:61)
`tests/server-restart.test.mjs:61` calls `GET http://127.0.0.1:${port}/api/projects` 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>/api/projects` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/admin/restart (tests/server-restart.test.mjs:108)
`tests/server-restart.test.mjs:108` calls `POST http://127.0.0.1:${port}/api/admin/restart` 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>/api/admin/restart` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/admin/restart (tests/server-restart.test.mjs:207)
`tests/server-restart.test.mjs:207` calls `POST http://127.0.0.1:${port}/api/admin/restart` 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>/api/admin/restart` If this points at an external API, p…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/app.js:1285
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/app.js:728
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/app.js:728 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/commits.js:298
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/commits.js:298 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/conversation.js:101
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/conversation.js:101 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/costs.js:35
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/costs.js:35 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/review.js:57
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/review.js:57 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/settings.js:120
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/settings.js:120 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/sidebar.js:295
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/sidebar.js:295 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/health.js:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/health.js:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/instances.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/instances.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/mcp/handlers.js:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/mcp/handlers.js:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/restart.js:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/restart.js:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/transcribe.js:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/transcribe.js:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/tts.js:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/tts.js:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/ttsInstall.js:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/ttsInstall.js:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/whisperInstall.js:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/whisperInstall.js:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/worktrees.js:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/worktrees.js:8 Node child process
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 21 placeholder/mock markers across 12 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 quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `mOld` in tests/lazy-load-rendering.test.mjs:36
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 — server.js:121
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 /projects/:name/sessions/:sid
`src/routes.js` declares `DELETE /projects/:name/sessions/:sid` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /projects/:name/worktrees/:wt/sessions/:sid
`src/routes.js` declares `DELETE /projects/:name/worktrees/:wt/sessions/:sid` 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 /
`src/mcp/server.js` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /instances/:id/attachments/:filename
`src/routes.js` declares `GET /instances/:id/attachments/:filename` 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 /projects/:name/commits/:sha/diff
`src/routes.js` declares `GET /projects/:name/commits/:sha/diff` 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 /projects/:name/commits/uncommitted/diff
`src/routes.js` declares `GET /projects/:name/commits/uncommitted/diff` 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 /projects/:name/sessions
`src/routes.js` declares `GET /projects/:name/sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /projects/:name/worktrees
`src/routes.js` declares `GET /projects/:name/worktrees` 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 /projects/:name/worktrees/:wt/diff
`src/routes.js` declares `GET /projects/:name/worktrees/:wt/diff` 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 /projects/:name/worktrees/:wt/sessions
`src/routes.js` declares `GET /projects/:name/worktrees/:wt/sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`src/mcp/server.js` declares `POST /` 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 /instances/:id/hook-callback
`src/routes.js` declares `POST /instances/:id/hook-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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /projects/:name/sessions/:sid/archive
`src/routes.js` declares `POST /projects/:name/sessions/:sid/archive` 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 /projects/:name/sessions/:sid/restore
`src/routes.js` declares `POST /projects/:name/sessions/:sid/restore` 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 /projects/:name/worktrees/:wt/sessions/:sid/archive
`src/routes.js` declares `POST /projects/:name/worktrees/:wt/sessions/:sid/archive` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /projects/:name/worktrees/:wt/sessions/:sid/restore
`src/routes.js` declares `POST /projects/:name/worktrees/:wt/sessions/:sid/restore` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api
`server.js` declares `USE /api` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /mcp
`server.js` declares `USE /mcp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: public/app.js (2194 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/instances.js (1572 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/mcp/handlers.js (1248 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/instances.test.mjs (1358 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/mcp.test.mjs (1034 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/rendering.test.mjs (1490 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/5bf66b82-f403-4a77-a887-3d1b36270e28/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5bf66b82-f403-4a77-a887-3d1b36270e28/

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.