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.
104 of your 203 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 157.06s for a 375.2 MB repo slow.
  • Repobility's analysis ran in 43.92s after the clone landed.

warpdotdev/warp

https://github.com/warpdotdev/warp · scanned 2026-06-05 09:36 UTC (5 days, 17 hours ago) · 10 languages

692 raw signals (180 security + 512 graph) 11/13 scanners ran 25th percentile · Rust · huge (>500K LoC) System graph score 68 (higher by 6)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 20.0 0.20 4.00
documentation_score 96.0 0.15 14.40
practices_score 80.0 0.15 12.00
code_quality 58.0 0.10 5.80
Overall 1.00 74.0
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

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

#1
Possible secret in crates/warp_core/src/channel/config.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/warp_core/src/channel/config.rs:62; move to env var / secrets manager.
crates/warp_core/src/channel/config.rs:62
#2
Possible secret in crates/warp_completer/src/completer/testing/mod.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/warp_completer/src/completer/testing/mod.rs:207; move to env var / secrets manager.
crates/warp_completer/src/completer/testing/mod.rs:207
#3
Insecure pattern 'eval_used' in crates/warpui_core/src/keymap.rs:788
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
crates/warpui_core/src/keymap.rs:788
#4
Insecure pattern 'eval_used' in crates/warpui_core/src/keymap/matcher.rs:262
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
crates/warpui_core/src/keymap/matcher.rs:262
#5
Dockerfile pipes a remote installer into a shell
GapSeverity.HIGH Layer.HARDWARE score 0.375
Why: high severity
docker/agent-dev/Dockerfile:51
#6
Dockerfile pipes a remote installer into a shell
GapSeverity.HIGH Layer.HARDWARE score 0.375
Why: high severity
docker/linux-dev/Dockerfile:51
#7
GitHub Action tracks a moving branch
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/feature_flag_cleanup.yml:38
#8
GitHub Action tracks a moving branch
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/feature_flag_cleanup.yml:170
#9
GitHub Action tracks a moving branch
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/ci.yml:690
#10
GitHub Action tracks a moving branch
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/repo-sync.yml:19

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/0dd1f97e-6133-4b37-bee6-e7b7a311db71/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0dd1f97e-6133-4b37-bee6-e7b7a311db71/

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.