esbuild

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.

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)

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

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

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.

Fragile runtime 32 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

12 matching findings on this repo

medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. scripts/parse-ts-files.js:53
medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. scripts/destructuring-fuzzer.js:139
medium Average file size is 986 lines (recommend <300)
low [SEC132] String concat where the language has interpolation (AI style drift): S… scripts/test262-async.js:71
low Duplicated implementation block across source files scripts/uglify-tests.js:244
low Duplicated implementation block across source files pkg/api/api.go:52
low Duplicated implementation block across source files lib/npm/browser.ts:32
low Duplicated implementation block across source files lib/deno/wasm.ts:10
low Duplicated implementation block across source files internal/logger/logger_linux.go:10
low Duplicated implementation block across source files compat-table/src/mdn.ts:108
low Duplicated implementation block across source files compat-table/src/js_table.ts:5
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… scripts/node-unref-tests.js:78

View all fragile runtime findings →

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Legacy-named symbol `spawnOld` in lib/deno/mod.ts:241

View all legacy markers findings →

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

12 matching findings on this repo

info Commented-code block (6 lines) in compat-table/src/index.ts:238
info Commented-code block (5 lines) in compat-table/src/mdn.ts:196
info Commented-code block (5 lines) in scripts/esbuild.js:28
info Commented-code block (7 lines) in scripts/js-api-tests.js:2977
info Commented-code block (12 lines) in scripts/terser-tests.js:193
info Commented-code block (6 lines) in scripts/end-to-end-tests.js:4412
info Commented-code block (5 lines) in scripts/gen-unicode-table.js:22
info Commented-code block (10 lines) in scripts/test262.js:180
info Commented-code block (12 lines) in scripts/uglify-tests.js:321
info Commented-code block (5 lines) in scripts/verify-source-map.js:658
info Commented-code block (7 lines) in scripts/browser/browser-tests.js:86
info Commented-code block (6 lines) in lib/shared/common.ts:1017

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

low Very large file: internal/bundler_tests/bundler_tsconfig_test.go (2788 lines)

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