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
40 of your 63 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.85s · analysis 3.01s · 9.4 MB · GitHub API rate-limit (preflight)

esbuild

https://github.com/evanw/esbuild · scanned 2026-05-24 01:23 UTC (1 week, 5 days ago) · 10 languages

278 findings (60 legacy + 218 scanner) 40th percentile · Go · large (100-500K LoC) Scanner says 67 (higher by 13)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 5 days ago · v2 · 169 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
76.8
/100
Repobility
87
60 legacy
9-layer
67
88.9% cov · 109 gaps
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 96.0 0.25 24.00
testing_score 76.0 0.20 15.20
documentation_score 72.0 0.15 10.80
practices_score 84.0 0.15 12.60
code_quality 45.5 0.10 4.55
Overall 1.00 79.9
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 38 Medium 9 Low 88 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 60 9-layer 109 Crowd 0 Layer: Quality 83 Security 3 Software 33 Api 1 Frontend 22 Cicd 27

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

#1
GitHub Action tracks a moving branch
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/ci.yml:119
#2
GitHub Action tracks a moving branch
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/ci.yml:315
#3
GitHub Action tracks a moving branch
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/e2e.yml:26
#4
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish.yml
#5
`fetch()` without try/.catch or AbortSignal — scripts/plugin-tests.js:16
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in scripts/plugin-tests.js:16, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#6
`fetch()` without try/.catch or AbortSignal — scripts/js-api-tests.js:3932
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in scripts/js-api-tests.js:3932, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#7
`fetch()` without try/.catch or AbortSignal — lib/shared/worker.ts:89
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in lib/shared/worker.ts:89, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#8
`fetch()` without try/.catch or AbortSignal — lib/npm/node-install.ts:70
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in lib/npm/node-install.ts:70, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#9
`fetch()` without try/.catch or AbortSignal — lib/deno/mod.ts:72
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in lib/deno/mod.ts:72, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#10
Stray `console.log` in TS/JS — scripts/destructuring-fuzzer.js:270
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in scripts/destructuring-fuzzer.js:270.

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/8da981ac-3685-4c52-b871-6094005ae9e9/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8da981ac-3685-4c52-b871-6094005ae9e9/

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.