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.

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

88.9% cov · 114 findings

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

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Legacy markers 5 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

5 matching findings on this repo

low Old/deprecated-named symbol `reusedLegacy` in tests/slug.test.js:107
low Old/deprecated-named symbol `reusedLegacy` in tests/org-launch.test.js:90
low Old/deprecated-named symbol `reusedLegacy` in lib/org-launch.js:139
low Old/deprecated-named symbol `reusedLegacy` in lib/slug-lookup.js:40
low Old/deprecated-named symbol `reusedLegacy` in lib/org-launch-route.js:90

View all legacy markers findings →

Commented-out code 39 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (5 lines) in server.js:337
info Commented-code block (5 lines) in tests/run-command.test.js:10
info Commented-code block (5 lines) in tests/virtual-desktop.test.js:15
info Commented-code block (6 lines) in tests/esc.test.js:4
info Commented-code block (5 lines) in scripts/check-frontend-syntax.js:3
info Commented-code block (5 lines) in scripts/gen-update-keypair.js:5
info Commented-code block (5 lines) in packaging/open-browser.js:76
info Commented-code block (6 lines) in lib/identity.js:37
info Commented-code block (14 lines) in lib/server-lock.js:3
info Commented-code block (6 lines) in lib/atomic-write.js:4
info Commented-code block (12 lines) in lib/org-launch.js:6
info Commented-code block (7 lines) in lib/net-acquire.js:3

View all commented-out code findings →

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.