coder/code-server

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.

25 of your 92 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.84s · analysis 27.25s · 1.6 MB · GitHub API rate-limit (preflight)

https://github.com/coder/code-server · scanned 2026-06-05 07:33 UTC (5 days, 22 hours ago) · 10 languages

274 raw signals (82 security + 192 graph) 57th percentile · Typescript · small (2-20K LoC) System graph score 55 (higher by 15)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 22 hours ago · v2 · 154 actionable findings from 2 signal sources. 24 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 96 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	47.5	0.25	11.88
`testing_score`	90.0	0.20	18.00
`documentation_score`	33.6	0.15	5.04
`practices_score`	89.0	0.15	13.35
`code_quality`	66.0	0.10	6.60
Overall		1.00	69.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 19 Medium 27 Low 70 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 58 System graph 96 Crowd 0 Layer: Quality 29 Security 11 Software 70 Cicd 5 Frontend 14 Api 25

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 2 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.

2 matching findings on this repo

low Old/deprecated-named symbol `hashLegacy` in test/unit/node/util.test.ts:158
low Old/deprecated-named symbol `hashLegacy` in src/node/util.ts:164

View all legacy markers findings →

Commented-out code 7 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/`.

7 matching findings on this repo

info Commented-code block (7 lines) in test/playwright.config.ts:5
info Commented-code block (8 lines) in test/unit/node/util.test.ts:419
info Commented-code block (9 lines) in test/e2e/logout.test.ts:4
info Commented-code block (7 lines) in test/e2e/models/CodeServer.ts:486
info Commented-code block (6 lines) in src/node/cli.ts:875
info Commented-code block (6 lines) in src/node/entry.ts:8
info Commented-code block (7 lines) in src/node/http.ts:225

View all commented-out code findings →

Config drift 2 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

2 matching findings on this repo

low File has no detected symbols: test/playwright.config.ts
info Commented-code block (7 lines) in test/playwright.config.ts:5

View all config drift 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/8618e285-16c4-4629-8ab9-901d19f88409/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8618e285-16c4-4629-8ab9-901d19f88409/

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.