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
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)

zed-industries/zed

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
Combined
74.2
/100
Security checks
76
54 findings
System graph
73
100.0% cov · 270 findings
Critical
8
click to filter
Agents
6
0 votes
Crowd
0
reported
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

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

#1
Possible secret in crates/client/src/proxy/http_proxy.rs
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 crates/client/src/proxy/http_proxy.rs:189; move to env var / secrets manager.
crates/client/src/proxy/http_proxy.rs:189
#2
Possible secret in crates/client/src/proxy/socks_proxy.rs
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 crates/client/src/proxy/socks_proxy.rs:206; move to env var / secrets manager.
crates/client/src/proxy/socks_proxy.rs:206
#3
Possible secret in crates/repl/src/outputs.rs
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 crates/repl/src/outputs.rs:1190; move to env var / secrets manager.
crates/repl/src/outputs.rs:1190
#4
Possible secret in crates/repl/src/outputs.rs
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 crates/repl/src/outputs.rs:1203; move to env var / secrets manager.
crates/repl/src/outputs.rs:1203
#5
Possible secret in crates/collab/.env.toml
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 crates/collab/.env.toml:6; move to env var / secrets manager.
crates/collab/.env.toml:6
#6
Possible secret in crates/language_models/src/provider/opencode.rs
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 crates/language_models/src/provider/opencode.rs:755; move to env var / secrets manager.
crates/language_models/src/provider/opencode.rs:755
#7
Possible secret in crates/language_models/src/provider/deepseek.rs
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 crates/language_models/src/provider/deepseek.rs:649; move to env var / secrets manager.
crates/language_models/src/provider/deepseek.rs:649
#8
Possible secret in crates/language_models/src/provider/open_ai.rs
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 crates/language_models/src/provider/open_ai.rs:566; move to env var / secrets manager.
crates/language_models/src/provider/open_ai.rs:566
#9
Insecure pattern 'eval_used' in crates/agent_ui/src/inline_assistant.rs:2058
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
crates/agent_ui/src/inline_assistant.rs:2058
#10
Insecure pattern 'eval_used' in crates/gpui_macos/src/platform.rs:316
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
crates/gpui_macos/src/platform.rs:316

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