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

conorb-DR/dr-launcher

https://github.com/conorb-DR/dr-launcher · scanned 2026-06-17 01:50 UTC (1 month, 1 week ago)

114 raw signals (0 security + 114 graph)

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

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -28.1 (diff) · 114 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
48.6
/100
Security checks
49
0 findings
System graph
49
88.9% cov · 114 findings
Critical
1
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 1 High 3 Medium 28 Low 43 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 114 Crowd 0 Layer: Frontend 10 Security 27 Cicd 1 Quality 53 Api 23
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 48.6/100 with 88.9% coverage. It contains 905 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 114 findings — concentrated in quality (53), security (27), api (23). Risk profile is high: 1 critical, 3 high, 28 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 75 of 114 actionable findings. 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 Possible secret in lib/auth.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lib/auth.js:15
high System graph security security conf 1.00 Insecure pattern 'exec_used' in lib/auth.js:168
Found a known-risky pattern (exec_used). Review and replace if possible.
lib/auth.js:168 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packaging/open-browser.js:59
Found a known-risky pattern (exec_used). Review and replace if possible.
packaging/open-browser.js:59 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in server.js:1475
Found a known-risky pattern (exec_used). Review and replace if possible.
server.js:1475 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/js/cli-tools.mjs:75
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 — public/js/main.mjs:138
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: agents/dashboard-agent/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.
agents/dashboard-agent/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 license. 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/js/cleanup.mjs:25
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/cleanup.mjs:25 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/cli-tools.mjs:29
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/cli-tools.mjs:29 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/diagnostics.mjs:16
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/diagnostics.mjs:16 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/main.mjs:136
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/main.mjs:136 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/orgroster.mjs:45
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/orgroster.mjs:45 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/restart.mjs:14
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/restart.mjs:14 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/settings.mjs:35
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/settings.mjs:35 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/update.mjs:70
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/update.mjs:70 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in agents/datamapper-agent/scripts/download-filebox.js:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
agents/datamapper-agent/scripts/download-filebox.js:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in lib/auth.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
lib/auth.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in lib/chrome.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
lib/chrome.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in lib/dr-cli.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
lib/dr-cli.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in lib/restart.js:31
Found a known-risky pattern (node_child_process). Review and replace if possible.
lib/restart.js:31 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in lib/run-command.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
lib/run-command.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in lib/server-lock.js:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
lib/server-lock.js:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in lib/sessions.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
lib/sessions.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in lib/tray.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
lib/tray.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in lib/virtual-desktop.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
lib/virtual-desktop.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in lib/workspace.js:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
lib/workspace.js:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packaging/open-browser.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
packaging/open-browser.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-frontend-syntax.js:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-frontend-syntax.js:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/gen-update-keypair.js:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/gen-update-keypair.js:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in server.js:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
server.js:6 Node child process
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 35 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 GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci.yml:44 CI/CD securitySupply chainGithub actions
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 `reusedLegacy` in lib/org-launch-route.js:90
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 `reusedLegacy` in lib/org-launch.js:139
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 `reusedLegacy` in lib/slug-lookup.js:40
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 `reusedLegacy` in tests/org-launch.test.js:90
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 `reusedLegacy` in tests/slug.test.js:107
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — agents/dashboard-agent/scripts/api-put-widget.js:154
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 — agents/dashboard-agent/scripts/grid-engine.js:461
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 — agents/datamapper-agent/scripts/download-filebox.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 — agents/datamapper-agent/scripts/validate-spec.js:220
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — lib/log.js:66
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-frontend-syntax.js:32
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/gen-server-maps.js:53
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/gen-update-keypair.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/lint-agent-paths.js:75
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/sign-manifest.js:56
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: GET /
`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 /api/agents
`server.js` declares `GET /api/agents` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/auth/status
`server.js` declares `GET /api/auth/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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cli/install
`server.js` declares `GET /api/cli/install` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`server.js` declares `GET /api/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/launch-stream
`server.js` declares `GET /api/launch-stream` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/logs
`server.js` declares `GET /api/logs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/recents
`server.js` declares `GET /api/recents` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/servers
`server.js` declares `GET /api/servers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/sessions
`server.js` declares `GET /api/sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/sessions/health
`server.js` declares `GET /api/sessions/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/settings
`server.js` declares `GET /api/settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/sync/status
`server.js` declares `GET /api/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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/update-check
`server.js` declares `GET /api/update-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 dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /auth/callback
`server.js` declares `GET /auth/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: GET /index.html
`tests-e2e/server.mjs` declares `GET /index.html` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth-health/check
`server.js` declares `POST /api/auth-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 dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/recents
`server.js` declares `POST /api/recents` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/refresh
`server.js` declares `POST /api/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 /api/settings
`server.js` declares `POST /api/settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/sync
`server.js` declares `POST /api/sync` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/sync/init
`server.js` declares `POST /api/sync/init` 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 /static
`server.js` declares `USE /static` 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/js/main.mjs (2453 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server.js (1484 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/d08415a5-025a-4eab-a0b5-a8cec3906345/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d08415a5-025a-4eab-a0b5-a8cec3906345/

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.