zed-industries/zed

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.

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

Scan timing: clone 16.4s · analysis 24.93s · 80.2 MB · GitHub API rate-limit (preflight)

https://github.com/zed-industries/zed · scanned 2026-06-05 07:19 UTC (6 days ago) · 10 languages

718 raw signals (164 security + 554 graph) 11/13 scanners ran 0th percentile · Rust · huge (>500K LoC) System graph score 72 (lower by 5)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 270 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	22.0	0.20	4.40
`documentation_score`	91.0	0.15	13.65
`practices_score`	76.0	0.15	11.40
`code_quality`	44.0	0.10	4.40
Overall		1.00	67.9

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 8 High 19 Medium 19 Low 249 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 54 System graph 270 Crowd 0 Layer: Quality 274 Cicd 18 Software 12 Security 14 Frontend 3 Network 1 Hardware 2

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.

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

2 matching findings on this repo

info Commented-code block (5 lines) in crates/eval_cli/zed_eval/agent.py:126
info Commented-code block (5 lines) in script/triage_project_sync.py:106

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 Very large file: crates/agent_ui/src/agent_configuration.rs (1547 lines)
low Very large file: crates/agent_ui/src/agent_configuration/configure_context_serv…

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/a119af50-ee8c-43d5-8bbf-b3fa8f6264d6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a119af50-ee8c-43d5-8bbf-b3fa8f6264d6/

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.