webpack/webpack

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.

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

Scan timing: clone 3.85s · analysis 8.78s · 39.2 MB · GitHub API rate-limit (preflight)

https://github.com/webpack/webpack · scanned 2026-06-05 08:57 UTC (5 days, 19 hours ago) · 10 languages

1079 raw signals (87 security + 992 graph) 11/13 scanners ran 100th percentile · Javascript · huge (>500K LoC) System graph score 64 (higher by 29)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 492 findings

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`	100.0	0.20	20.00
`documentation_score`	89.0	0.15	13.35
`practices_score`	94.0	0.15	14.10
`code_quality`	80.0	0.10	8.00
Overall		1.00	93.2

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 0 High 12 Medium 10 Low 296 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 22 System graph 492 Crowd 0 Layer: Quality 145 Security 13 Software 53 Cicd 3 Api 1 Frontend 298 Network 1

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.

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 Old/deprecated-named symbol `isAssertLegacy` in lib/javascript/JavascriptParser…

View all legacy markers findings →

Commented-out code 97 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 test/HotTestCases.template.js:213
info Commented-code block (8 lines) in test/test262.spectest.js:757
info Commented-code block (7 lines) in test/NormalModule.unittest.js:518
info Commented-code block (6 lines) in test/walkHtmlTokens.unittest.js:1939
info Commented-code block (6 lines) in test/FileSystemInfo.unittest.js:504
info Commented-code block (7 lines) in test/cases/parsing/issue-17063/index.js:8
info Commented-code block (6 lines) in test/cases/parsing/harmony-tdz/index.js:4
info Commented-code block (7 lines) in test/cases/chunks/nested-blocks-with-availabl…
info Commented-code block (5 lines) in test/cases/resolving/module-sync/index.js:10
info Commented-code block (5 lines) in test/configCases/require/esm-module-exports/t…
info Commented-code block (8 lines) in test/configCases/require/esm-module-exports/i…
info Commented-code block (7 lines) in test/configCases/externals/phase-imports-sour…

View all commented-out code findings →

Config drift 97 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.

12 matching findings on this repo

low File has no detected symbols: jest.config.js
low File has no detected symbols: generate-types-config.js
low File has no detected symbols: test/ConfigTestCases.basictest.js
low File has no detected symbols: test/ConfigCacheTestCases.basictest.js
low Stray `console.log` in TS/JS — test/configCases/race-conditions/load-module/mod…
low Stray `console.log` in TS/JS — test/configCases/library/concatenate-modules-nam…
low Stray `console.log` in TS/JS — test/configCases/library/modern-module-named-imp…
low Stray `console.log` in TS/JS — test/configCases/wasm/reference-types/pkg/wasm_l…
low Stray `console.log` in TS/JS — test/configCases/asset-modules/url-target-web2/a…
low Stray `console.log` in TS/JS — test/configCases/asset-modules/url-target-webwor…
low Stray `console.log` in TS/JS — test/configCases/parsing/issue-19514/index.js:7
low Stray `console.log` in TS/JS — test/configCases/deprecations/non-unique-hash/b.…

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/aca40d56-d526-49b3-b7c4-a68c7a21b443/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/aca40d56-d526-49b3-b7c4-a68c7a21b443/

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.