nuxt/nuxt

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.

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

Scan timing: clone 3.13s · analysis 72.21s · 5.3 MB · GitHub API rate-limit (preflight)

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

839 raw signals (79 security + 760 graph) 87th percentile · Typescript · medium (20-100K LoC) System graph score 48 (higher by 37)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 17 hours ago · v2 · 412 actionable findings from 2 signal sources. 47 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 · 371 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	89.2	0.25	22.30
`testing_score`	100.0	0.20	20.00
`documentation_score`	79.8	0.15	11.97
`practices_score`	94.0	0.15	14.10
`code_quality`	73.2	0.10	7.32
Overall		1.00	84.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 164 Medium 26 Low 114 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 41 System graph 371 Crowd 0 Layer: Quality 55 Cicd 8 Security 3 Software 69 Frontend 113 Network 1 Hardware 2 Api 161

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 3 findings

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.

3 matching findings on this repo

low Old/deprecated-named symbol `unheadLegacy` in packages/nuxt/src/head/module.ts:…
low Old/deprecated-named symbol `isLegacy` in packages/schema/src/types/schema.ts:4…
high Dangling fetch: GET /legacy-async-data-fail (test/basic.test.ts:594)

View all legacy markers findings →

Commented-out code 18 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 (5 lines) in test/basic.test.ts:1197
info Commented-code block (6 lines) in test/server-components.test.ts:585
info Commented-code block (5 lines) in test/fixtures/ssr-streaming/plugins/csp-nonce…
info Commented-code block (5 lines) in test/fixtures/basic-types/nuxt.config.ts:129
info Commented-code block (8 lines) in test/fixtures/basic-types/config-types.ts:52
info Commented-code block (13 lines) in test/fixtures/basic-types/app/app-types.ts:59
info Commented-code block (5 lines) in test/e2e/ssr-streaming.test.ts:148
info Commented-code block (7 lines) in test/e2e/suspense.test.ts:63
info Commented-code block (5 lines) in packages/nuxt/src/head/module.ts:119
info Commented-code block (7 lines) in packages/nuxt/src/components/plugins/loader.t…
info Commented-code block (5 lines) in packages/nuxt/src/app/plugins/prefetch-preloa…
info Commented-code block (8 lines) in packages/nuxt/src/core/utils/proxy.ts:3

View all commented-out code findings →

Config drift 20 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: playground/nuxt.config.ts
low File has no detected symbols: test/mocks/nuxt-config.ts
low File has no detected symbols: test/mocks/app-config.ts
low File has no detected symbols: test/fixtures/build-assets-dir-collision/nuxt.con…
low File has no detected symbols: test/fixtures/ssr-streaming/nuxt.config.ts
low File has no detected symbols: test/fixtures/basic-types/config-types.ts
low File has no detected symbols: test/fixtures/basic-types/app/app.config.ts
low File has no detected symbols: test/fixtures/basic-types/extends/bar/nuxt.config…
low File has no detected symbols: test/fixtures/basic-types/extends/bar/app.config.…
low File has no detected symbols: test/fixtures/minimal/nuxt.config.ts
low Stray `console.log` in TS/JS — test/fixtures/basic-types/nuxt.config.ts:64
info TODO/FIXME marker in shipping code — test/fixtures/basic-types/config-types.ts:…

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/f4a94b28-80b5-49a3-b7ff-3359394cb43f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f4a94b28-80b5-49a3-b7ff-3359394cb43f/

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.