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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

Possible secret in src/node/cli.ts

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in src/node/cli.ts:14; move to env var / secrets manager.

src/node/cli.ts:14

Insecure pattern 'eval_used' in src/node/main.ts:62

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

src/node/main.ts:62

Insecure pattern 'eval_used' in src/node/routes/vscode.ts:66

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

src/node/routes/vscode.ts:66

GitHub Actions workflow grants broad write permissions

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/release.yaml

Stray `console.log` in TS/JS — ci/dev/watch.ts:34

GapSeverity.LOW Layer.FRONTEND score 0.170

Why: low severity · fix is short / mechanical

Fix: Delete or guard the `console.log` in ci/dev/watch.ts:34.

Stray `console.log` in TS/JS — src/node/entry.ts:27

GapSeverity.LOW Layer.FRONTEND score 0.170

Why: low severity · fix is short / mechanical

Fix: Delete or guard the `console.log` in src/node/entry.ts:27.

Legacy-named symbol `hashLegacy` in src/node/util.ts:164

GapSeverity.LOW Layer.QUALITY score 0.113

Why: low severity · crashes are likely without this

Fix: If genuinely unused, remove the function; if framework-registered, add a docstring.

package.json defines install-time lifecycle scripts

GapSeverity.LOW Layer.CICD score 0.100

Why: low severity

package.json

File has no detected symbols: ci/dev/preinstall.js

GapSeverity.LOW Layer.SOFTWARE score 0.100

Why: low severity

#10

File has no detected symbols: src/node/proxy.ts

GapSeverity.LOW Layer.SOFTWARE score 0.100

Why: low severity

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.