Public report of sveltejs/kit, published 15 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 15 November 2026, 04:06 UTC · Survey ID cd_2e17cb0540da48e4b4246feb771e57cc

sveltejs/kit

Measured 15 November 2026, 04:05 UTC, at code version ccd3474

CAI score 59out of 100 At risk Up 5 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 38,493 lines of product code in 12 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Code Health, 55

Findings by how serious they are

27 critical 700 serious 125 minor

7 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 04:05 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

71of 71 dimensions measured by tools.
827of 852 findings point to an exact file and line, so you can open each one in the code. The other 25 concern the repository as a whole, such as missing documentation.
71dimensions across 7 lenses, read from 38,493 lines of product code in 12 projects.
Chapters

Executive summary

sveltejs/kit is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 59 out of 100, which the At risk rating leaves unchanged.

Code Health, at 55, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is turning on missing-value checks, worth about 3 points. Simplifying the hardest methods would lift Code Health itself, also worth about 3.

Six known security holes in the packages the code depends on can be used by attackers. Two secrets can leak from the build pipeline, and fourteen packages carry licence risk. Updating the vulnerable packages, limiting each secret to its own step and replacing or clearing the banned-licence packages would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and passing outside input through environment variables would deal with the pipeline step that puts outside input straight into a shell command. The loop of files that import each other needs breaking.

The product code is 38,493 lines, about €89,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Code Health 55 · counts for 46%Security and Compliance 60 · counts for 25%Performance 60 · counts for 14%Production Readiness 64 · counts for 8%Maturity 70 · counts for 4%Accessibility 78 · counts for 2%Architecture 92 · counts for 1%

The weakest lenses score close to each other, so improving any of them moves the score.

Code composition: what the lines of code are
Product code 46%Tests 54%
New since the last survey: 100 findings

These 100 critical or serious findings weren't in the previous survey, on 29 October 2026.

  • Cyclomatic Complexity · crawl (cyclomatic 61) packages/kit/src/core/postbuild/crawl.js
  • Cyclomatic Complexity · static.serve_static.<returned closure> (cyclomatic 26) packages/adapter-node/src/static.js
  • Cyclomatic Complexity · serve_static (cyclomatic 26) packages/adapter-node/src/static.js
  • Cyclomatic Complexity · index.preview.<returned closure> (cyclomatic 25) packages/kit/src/exports/vite/preview/index.js
  • Cyclomatic Complexity · remote.plugin_remote (cyclomatic 23) REDACTED
  • Cyclomatic Complexity · plugin_remote::handler (cyclomatic 22) REDACTED
  • Cyclomatic Complexity · index.dev.<returned closure> (cyclomatic 20) packages/kit/src/exports/vite/dev/index.js
  • Cyclomatic Complexity · watch (cyclomatic 19) packages/package/src/index.js
  • Cyclomatic Complexity · find_server_assets.find_server_assets (cyclomatic 18) packages/kit/src/core/generate_manifest/find_server_assets.js
  • Cyclomatic Complexity · kit::handler (cyclomatic 17) packages/kit/src/exports/vite/index.js
  • Cyclomatic Complexity · plugin_guard::handler (cyclomatic 17) packages/kit/src/exports/vite/plugins/guard.js
  • Cognitive Complexity · crawl (cognitive 227) packages/kit/src/core/postbuild/crawl.js
  • Cognitive Complexity · watch (cognitive 34) packages/package/src/index.js
  • Cognitive Complexity · static.serve_static.<returned closure> (cognitive 33) packages/adapter-node/src/static.js
  • Cognitive Complexity · index.preview.<returned closure> (cognitive 33) packages/kit/src/exports/vite/preview/index.js
  • Cognitive Complexity · internal.format_response (cognitive 31) packages/kit/src/runtime/server/internal.js
  • Cognitive Complexity · index.dev.<returned closure> (cognitive 23) packages/kit/src/exports/vite/dev/index.js
  • Cognitive Complexity · handler.render (cognitive 21) packages/adapter-node/src/handler.js
  • Cognitive Complexity · options.object.<returned closure> (cognitive 21) packages/kit/src/core/config/options.js
  • Cognitive Complexity · object (cognitive 21) packages/kit/src/core/config/options.js
  • Cognitive Complexity · query-batch.svelte.query_batch.wrapper (cognitive 20) packages/kit/src/runtime/client/remote-functions/query-batch.svelte.js
  • Cognitive Complexity · kit::handler (cognitive 19) packages/kit/src/exports/vite/index.js
  • Cognitive Complexity · forked (cognitive 16) packages/kit/src/utils/fork.js
  • God Classes · FunctionTooLong: remote.plugin_remote REDACTED
  • God Classes · FunctionTooLong: index.dev.<returned closure> packages/kit/src/exports/vite/dev/index.js
  • Test Quality · Skipped test: (unnamed test) packages/kit/test/apps/writes/test/test.js
  • Test Quality · Skipped test: (unnamed test) packages/kit/test/apps/writes/test/test.js
  • Test Quality · Skipped test: (unnamed test) packages/kit/test/apps/dev-only/test/test.js
  • Test Quality · No assertions: Server hooks can be added and removed packages/kit/test/apps/writes/test/test.js
  • License Compliance · Banned license: @img/sharp-libvips-darwin-arm64 REDACTED
  • License Compliance · Banned license: @img/sharp-libvips-darwin-x64 REDACTED
  • License Compliance · Banned license: @img/sharp-libvips-linux-arm REDACTED
  • License Compliance · Banned license: @img/sharp-libvips-linux-arm64 REDACTED
  • License Compliance · Banned license: @img/sharp-libvips-linux-ppc64 REDACTED
  • License Compliance · Banned license: @img/sharp-libvips-linux-riscv64 REDACTED
  • License Compliance · Banned license: @img/sharp-libvips-linux-s390x REDACTED
  • License Compliance · Banned license: @img/sharp-libvips-linux-x64 REDACTED
  • License Compliance · Banned license: @img/sharp-libvips-linuxmusl-arm64 REDACTED
  • License Compliance · Banned license: @img/sharp-libvips-linuxmusl-x64 REDACTED
  • License Compliance · Banned license: @img/sharp-wasm32 REDACTED
  • License Compliance · Banned license: @img/sharp-win32-arm64 REDACTED
  • License Compliance · Banned license: @img/sharp-win32-ia32 REDACTED
  • License Compliance · Banned license: @img/sharp-win32-x64 REDACTED
  • Churn × Complexity Hotspots · Hotspot: packages/kit/src/core/postbuild/crawl.js packages/kit/src/core/postbuild/crawl.js
  • Churn × Complexity Hotspots · Hotspot: REDACTED REDACTED
  • Churn × Complexity Hotspots · Repeated repair: packages/adapter-vercel/utils.js packages/adapter-vercel/utils.js
  • Churn × Complexity Hotspots · Repeated repair: REDACTED REDACTED
  • Churn × Complexity Hotspots · Repeated repair: REDACTED REDACTED
  • Explicit Debt · TodoComment packages/adapter-vercel/test/apps/basic/test/test.ts
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Code Duplication · Duplicated block (29 lines × 2 locations) packages/adapter-static/platforms.js
  • Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) packages/kit/src/runtime/app/paths/client.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/kit/src/runtime/app/server/remote/query.js
  • Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) packages/kit/src/runtime/server/remote-functions.js
  • Import Boundaries · Boundary violation [package:test-cross-package-internals] packages/kit/test/apps/basics/test/vitest/server.spec.js
  • Cyclomatic Complexity · Complex function crawl (cyclomatic 60, cognitive 226) packages/kit/src/core/postbuild/crawl.js
  • Cyclomatic Complexity · Complex function visit (cyclomatic 26, cognitive 46) packages/kit/src/core/postbuild/prerender.js
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 26, cognitive 35) packages/adapter-node/src/static.js
  • Cyclomatic Complexity · Complex function treeshake_prerendered_remotes (cyclomatic 25, cognitive 58) packages/kit/src/exports/vite/build/remote.js
  • Cyclomatic Complexity · Complex function process_ssr_build (cyclomatic 25, cognitive 47) packages/kit/src/exports/vite/build/index.js
  • Cyclomatic Complexity · Complex function write_all_types (cyclomatic 25, cognitive 40) packages/kit/src/core/sync/write_types/index.js
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 23, cognitive 35) packages/kit/src/runtime/client/client.js
  • Cyclomatic Complexity · Complex function adapt (cyclomatic 23, cognitive 33) packages/adapter-cloudflare/index.js
  • Cyclomatic Complexity · Complex function render_endpoint (cyclomatic 23, cognitive 25) packages/kit/src/runtime/server/endpoint.js
  • Cyclomatic Complexity · Complex function handler (cyclomatic 22, cognitive 53) REDACTED
  • Cyclomatic Complexity · Complex function update_types (cyclomatic 22, cognitive 33) packages/kit/src/core/sync/write_types/index.js
  • Cyclomatic Complexity · Complex function update_element (cyclomatic 21, cognitive 32) packages/enhanced-img/src/vite-plugin.js
  • Cyclomatic Complexity · Complex function save (cyclomatic 21, cognitive 32) packages/kit/src/core/postbuild/prerender.js
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 21, cognitive 24) packages/kit/src/exports/vite/dev/index.js
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 20, cognitive 31) packages/kit/src/core/sync/write_types/index.js
  • Cyclomatic Complexity · Complex function exec (cyclomatic 20, cognitive 28) REDACTED
  • Cyclomatic Complexity · Complex function validate (cyclomatic 20, cognitive 27) REDACTED
  • Cyclomatic Complexity · Complex function _start (cyclomatic 20, cognitive 26) packages/kit/src/runtime/client/client.js
  • Cyclomatic Complexity · Complex function handle_remote_call_internal (cyclomatic 20, cognitive 22) packages/kit/src/runtime/server/remote-functions.js
  • Cyclomatic Complexity · Complex function get_routes_json (cyclomatic 19, cognitive 34) REDACTED
  • Cyclomatic Complexity · Complex function create_env_modules (cyclomatic 18, cognitive 29) REDACTED
  • Large Files · packages/kit/src/runtime/client/client.js: 3278 lines of code packages/kit/src/runtime/client/client.js
  • Large Files · packages/kit/src/runtime/form-utils.js: 819 lines of code packages/kit/src/runtime/form-utils.js
  • Large Files · packages/kit/src/core/sync/write_types/index.js: 782 lines of code packages/kit/src/core/sync/write_types/index.js
  • Large Files · packages/kit/src/core/postbuild/prerender.js: 622 lines of code packages/kit/src/core/postbuild/prerender.js
  • Large Files · packages/kit/src/exports/vite/index.js: 615 lines of code packages/kit/src/exports/vite/index.js
  • Large Files · packages/kit/src/runtime/server/page/render.js: 590 lines of code packages/kit/src/runtime/server/page/render.js
  • Large Files · packages/adapter-vercel/index.js: 582 lines of code packages/adapter-vercel/index.js
  • Large Files · packages/kit/src/runtime/server/remote-functions.js: 537 lines of code packages/kit/src/runtime/server/remote-functions.js
  • Large Files · packages/kit/src/exports/vite/dev/index.js: 439 lines of code packages/kit/src/exports/vite/dev/index.js
  • Large Files · packages/enhanced-img/src/vite-plugin.js: 412 lines of code packages/enhanced-img/src/vite-plugin.js
  • Test Coverage · This test file cannot be loaded packages/kit/test/apps/writes/test/test.js
  • Dead Code · Dead file (~147 LoC) packages/kit/src/runtime/server/instance.js
  • Exception handling · Swallowed exception (empty catch) packages/kit/src/runtime/server/internal.js
  • Exception handling · Swallowed exception (empty catch) packages/kit/src/runtime/client/client.js
  • Exception handling · Swallowed exception (empty catch) packages/kit/src/runtime/client/client.js
  • Exception handling · Swallowed exception (caught, then discarded) packages/kit/src/runtime/client/client.js
  • Exception handling · Swallowed exception (caught, then discarded) packages/kit/src/runtime/client/client.js
  • Exception handling · Swallowed exception (empty catch) packages/kit/src/runtime/client/session-storage.js
  • Exception handling · Swallowed exception (empty catch) packages/kit/src/runtime/client/session-storage.js
  • Exception handling · Swallowed exception (empty catch) packages/adapter-vercel/index.js
  • Exception handling · Swallowed exception (empty catch) packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-bun/index.js

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 147 findings

These 147 critical or serious findings were in the previous survey, on 29 October 2026, and are gone from this one. The first 100 are listed here.

  • Cyclomatic Complexity · crawl (cyclomatic 63) packages/kit/src/core/postbuild/crawl.js
  • Cyclomatic Complexity · static.serve_static (cyclomatic 25) packages/adapter-node/src/static.js
  • Cyclomatic Complexity · watch (cyclomatic 18) packages/package/src/index.js
  • Cyclomatic Complexity · kit::handler (cyclomatic 16) packages/kit/src/exports/vite/index.js
  • Cognitive Complexity · crawl (cognitive 256) packages/kit/src/core/postbuild/crawl.js
  • Cognitive Complexity · watch (cognitive 30) packages/package/src/index.js
  • Cognitive Complexity · handler.ssr (cognitive 21) packages/adapter-node/src/handler.js
  • Cognitive Complexity · options.object (cognitive 21) packages/kit/src/core/config/options.js
  • Cognitive Complexity · kit::handler (cognitive 18) packages/kit/src/exports/vite/index.js
  • Cognitive Complexity · virtual_workers_module.setup (cognitive 17) packages/adapter-cloudflare/index.js
  • Cognitive Complexity · init (cognitive 17) packages/kit/src/runtime/server/instance.js
  • Cognitive Complexity · fork.forked (cognitive 16) packages/kit/src/utils/fork.js
  • God Classes · FunctionTooLong: remote-functions.handle_remote_call_internal packages/kit/src/runtime/server/remote-functions.js
  • Churn × Complexity Hotspots · Hotspot: packages/kit/src/core/sync/write_client_manifest.js packages/kit/src/core/sync/write_client_manifest.js
  • Churn × Complexity Hotspots · Hotspot: packages/package/src/index.js packages/package/src/index.js
  • Churn × Complexity Hotspots · Hotspot: REDACTED REDACTED
  • Churn × Complexity Hotspots · Hotspot: packages/kit/src/runtime/client/focus.js packages/kit/src/runtime/client/focus.js
  • Churn × Complexity Hotspots · Hotspot: packages/adapter-static/index.js packages/adapter-static/index.js
  • Churn × Complexity Hotspots · Hotspot: packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js
  • Churn × Complexity Hotspots · Repeated repair: packages/kit/src/runtime/client/remote-functions/query/instance.svelte.js packages/kit/src/runtime/client/remote-functions/query/instance.svelte.js
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Change Coupling · Boundary-crossing change coupling: serverless.js ↔ handler.js packages/adapter-netlify/files/serverless.js
  • Code Duplication · Duplicated block (29 lines × 2 locations) packages/adapter-static/platforms.js
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) packages/kit/src/runtime/app/paths/client.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/kit/src/runtime/app/server/remote/query.js
  • Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) packages/kit/src/exports/vite/dev/index.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/kit/src/runtime/app/server/remote/shared.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/kit/src/runtime/app/server/remote/shared.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/kit/src/runtime/client/client.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/kit/src/runtime/client/remote-functions/shared.svelte.js
  • Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) packages/kit/src/runtime/form-utils.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/kit/src/core/sync/create_manifest_data/index.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/kit/src/core/sync/write_app_types.js
  • Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) packages/kit/src/exports/vite/dev/index.js
  • Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) packages/kit/src/runtime/client/client.js
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/kit/src/core/config/options.js
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/kit/src/core/generate_manifest/find_server_assets.js
  • Code Duplication · Duplicated block (5 lines × 2 locations) packages/adapter-bun/src/handler.js
  • Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) packages/kit/src/runtime/server/fetch.js
  • Cyclomatic Complexity · Complex function crawl (cyclomatic 62, cognitive 255) packages/kit/src/core/postbuild/crawl.js
  • Large Files · packages/kit/src/runtime/client/client.js: 3272 lines of code packages/kit/src/runtime/client/client.js
  • Large Files · packages/kit/src/runtime/form-utils.js: 801 lines of code packages/kit/src/runtime/form-utils.js
  • Large Files · packages/kit/src/core/sync/write_types/index.js: 761 lines of code packages/kit/src/core/sync/write_types/index.js
  • Large Files · packages/kit/src/core/postbuild/prerender.js: 623 lines of code packages/kit/src/core/postbuild/prerender.js
  • Large Files · packages/kit/src/exports/vite/index.js: 607 lines of code packages/kit/src/exports/vite/index.js
  • Large Files · packages/kit/src/runtime/server/page/render.js: 593 lines of code packages/kit/src/runtime/server/page/render.js
  • Large Files · packages/adapter-vercel/index.js: 585 lines of code packages/adapter-vercel/index.js
  • Large Files · packages/kit/src/runtime/server/remote-functions.js: 517 lines of code packages/kit/src/runtime/server/remote-functions.js
  • Large Files · packages/kit/src/exports/vite/dev/index.js: 433 lines of code packages/kit/src/exports/vite/dev/index.js
  • Large Files · packages/enhanced-img/src/vite-plugin.js: 406 lines of code packages/enhanced-img/src/vite-plugin.js
  • Test Coverage · No test reaches this file scripts/check-dependencies.js
  • Test Coverage · No test reaches this file scripts/sync-all.js
  • Test Coverage · No test reaches this file scripts/print-flaky-test-report.js
  • Dead Code · Dead file (~170 LoC) packages/kit/src/runtime/server/instance.js
  • Dead Code · Dead file (~0 LoC) playgrounds/basic/src/service-worker/index.ts
  • Exception handling · Swallowed exception (empty catch) packages/kit/src/runtime/client/client.js
  • Exception handling · Swallowed exception (empty catch) packages/kit/src/runtime/client/client.js
  • Exception handling · Swallowed exception (caught, then discarded) packages/kit/src/runtime/client/client.js
  • Exception handling · Swallowed exception (caught, then discarded) packages/kit/src/runtime/client/client.js
  • Exception handling · Swallowed exception (empty catch) packages/kit/src/runtime/client/session-storage.js
  • Exception handling · Swallowed exception (empty catch) packages/kit/src/runtime/client/session-storage.js
  • Exception handling · Swallowed exception (empty catch) packages/adapter-vercel/index.js
  • Exception handling · Swallowed exception (empty catch) packages/adapter-vercel/index.js
  • A11y enforcement · Accessibility enforcement below the top rung
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-bun/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-netlify/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-netlify/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-netlify/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-netlify/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-netlify/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-node/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-node/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-node/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-node/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-static/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-static/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/adapter-vercel/index.js
  • Async & latency hygiene · Sync-over-async blocking packages/enhanced-img/src/vite-plugin.js
  • Async & latency hygiene · Sync-over-async blocking packages/kit/src/core/adapt/builder.js
  • Async & latency hygiene · Sync-over-async blocking packages/kit/src/core/adapt/builder.js
  • Async & latency hygiene · Sync-over-async blocking packages/kit/src/core/postbuild/fallback.js
  • Async & latency hygiene · Sync-over-async blocking packages/kit/src/core/postbuild/prerender.js
Rebuild cost: about €89,000 · Estimate
Cost to rebuild€30,000 to €150,000, for 493 to 1,564 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 38,493 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
The findings name the configuration each number was taken from and, for the assertions, the files that hold them.
Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Raises the score by about 3 points · Medium effort · Nullable reference types
2
Resolve the 3 TodoComment finding(s) in Explicit Debt — start with test.ts (3).
Raises the score by about 1 point · Low effort · Explicit Debt
3
Bring the 58 bodies over 30 down to 30 or less in Cognitive Complexity — start with crawl (cognitive 227), render_response (cognitive 189), index.statically_analyse_page_options (cognitive 120).
Raises the score by about 3 points · High effort · Cognitive Complexity

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €89,000 to build again, about 0.6 person-years of work. Its weakest lens is Code Health, at 55 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 11% on every change. The history of the code shows how much it changes: about 59,358 lines over the last 90 days, which is about 240,730 lines a year. At that pace, the extra work comes to an estimated 29.2 to 174.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch @sveltejs/adapter-auto adapter-auto @sveltejs/kit kit @sveltejs/adapter-auto->@sveltejs/kit @sveltejs/adapter-bun adapter-bun @sveltejs/adapter-bun->@sveltejs/kit @sveltejs/adapter-cloudflare adapter-cloudflare @sveltejs/adapter-cloudflare->@sveltejs/kit @sveltejs/adapter-netlify adapter-netlify @sveltejs/adapter-netlify->@sveltejs/kit @sveltejs/adapter-node adapter-node @sveltejs/adapter-node->@sveltejs/kit @sveltejs/adapter-static adapter-static @sveltejs/adapter-static->@sveltejs/kit @sveltejs/adapter-vercel adapter-vercel @sveltejs/adapter-vercel->@sveltejs/kit @sveltejs/enhanced-img enhanced-img @sveltejs/package package playground-basic playground-basic

At a glance — Code Health · 55% · Adequate · gated by D1, D2, X5 ·

At a glance — Architecture · 92% · Exemplary ·

At a glance — Maturity · 70% · Adequate · gated by M2 ·

At a glance — Readiness · 64% · Adequate · gated by D14, P3 ·

At a glance — Security · 60% · Adequate · gated by D29, D36 ·

At a glance — Accessibility · 78% · Strong ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection17High / Critical
A03:2025 — Software Supply Chain Failures16High / Critical

Roadmap

Top priorities: The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`); Bring the 58 bodies over 30 down to 30 or less in Cognitive Complexity — start with crawl (cognitive 227), render_response (cognitive 189), index.statically_analyse_page_options (cognitive 120); Resolve the 30 FunctionTooLong finding(s) in God Classes — start with index.js (11), client.js (4), load_data.js (2).

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).+2.8 ptsMediumNullable reference types
Resolve the 3 TodoComment finding(s) in Explicit Debt — start with test.ts (3).+1.4 ptsLowExplicit Debt
Bring the 58 bodies over 30 down to 30 or less in Cognitive Complexity — start with crawl (cognitive 227), render_response (cognitive 189), index.statically_analyse_page_options (cognitive 120).+2.6 ptsHighCognitive Complexity
Resolve the 30 FunctionTooLong finding(s) in God Classes — start with index.js (11), client.js (4), load_data.js (2).+2.4 ptsHighGod Classes
Swallowed exception (empty catch)+1.9 ptsMediumException handling
Bring the 8 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with render_response (cyclomatic 105), form.svelte.form (cyclomatic 84), _start_router (cyclomatic 76).+1.9 ptsHighCyclomatic Complexity
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.+1.8 ptsMediumAsync & latency hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json.+0.8 ptsLowADR Quality

File quality

Per-file score 0–10 — a quality signature. Of 125 files carrying findings, judged against the Production bar: 1% slop · 68% mixed · 31% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopLicense Compliance: Banned license: @img/sharp-libvips-darwin-arm64
REDACTED5.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
packages/kit/test/apps/async/test/client.test.js6.9MixedTest Quality: Skipped test: (unnamed test)
packages/kit/src/runtime/client/client.js7.0MixedCyclomatic Complexity: _start_router (cyclomatic 76)
packages/kit/src/core/sync/write_types/index.js7.0MixedCyclomatic Complexity: tweak_types (cyclomatic 69)
packages/kit/test/apps/options-2/test/test.js7.0MixedTest Quality: Skipped test: (unnamed test)
packages/kit/test/apps/options/test/paths.test.js7.0MixedTest Quality: Skipped test: (unnamed test)
packages/kit/test/apps/basics/test/playwright/client.test.js7.0MixedTest Quality: Skipped test: (unnamed test)
packages/kit/test/apps/basics/test/playwright/test.js7.0MixedTest Quality: Skipped test: (unnamed test)
packages/kit/test/apps/async/test/test.js7.0MixedTest Quality: Skipped test: (unnamed test)
packages/kit/src/runtime/server/respond.js7.0MixedCyclomatic Complexity: respond.internal_respond (cyclomatic 72)
packages/adapter-vercel/index.js7.0MixedCyclomatic Complexity: plugin.adapt (cyclomatic 35)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 27

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 700

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 125

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 7

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 71 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 71 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D16D17D19D20D23D24D26D27D28D29D30D31D34D35D36D43AC3AC5AC6AX10AX3AX4AX8C2GD1IC1M1M2M3M4P1P10P2P3P4P6PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X16X17X2X21X24X25X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 827 of 852 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1dd61-e6d0-7840-8d02-8a527eacdb7d.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for packages/adapter-bun/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/adapter-auto/ was NOT MEASURED: the dependency install for packages/adapter-auto/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the bun:test suite in packages/adapter-bun/ was NOT MEASURED: the dependency install for packages/adapter-bun/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/adapter-cloudflare/ was NOT MEASURED: the dependency install for packages/adapter-cloudflare/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/adapter-netlify/ was NOT MEASURED: the dependency install for packages/adapter-netlify/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/adapter-netlify/test/apps/basic/ was NOT MEASURED: the dependency install for packages/adapter-netlify/test/apps/basic/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/adapter-netlify/test/apps/edge/ was NOT MEASURED: the dependency install for packages/adapter-netlify/test/apps/edge/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/adapter-netlify/test/apps/split/ was NOT MEASURED: the dependency install for packages/adapter-netlify/test/apps/split/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/adapter-node/ was NOT MEASURED: the dependency install for packages/adapter-node/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/adapter-node/test/apps/basic/ was NOT MEASURED: the dependency install for packages/adapter-node/test/apps/basic/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/adapter-bun/index.d.ts`, `packages/adapter-bun/internal.d.ts`, `packages/adapter-netlify/ambient.d.ts`, `packages/kit/src/exports/public.d.ts`, `packages/kit/src/runtime/app/paths/types.d.ts`, … (+4 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (the repository): package.json has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 57 further occurrence(s) are not listed individually; the score already reflects all 97.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 76 further occurrence(s) are not listed individually; the score already reflects all 116.
  • R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 74 further occurrence(s) are not listed individually; the score already reflects all 114.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity2.2 / 10Critical✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 2.2 / 10 · rule-coverage 100% · ceiling Prevented

146 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was render_response at 105. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being index.watch at 19 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/package/src/index.js (index.watch at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

respond.internal_respond::resolve (cyclomatic 48) · ×2packages/kit/src/runtime/server/respond.js:593
form::create_instance::(anonymous)::handle_submit (cyclomatic 16) · ×2packages/kit/src/runtime/client/remote-functions/form.svelte.js:402
render_response (cyclomatic 105)packages/kit/src/runtime/server/page/render.js:55
form.svelte.form (cyclomatic 84)packages/kit/src/runtime/client/remote-functions/form.svelte.js:70
_start_router (cyclomatic 76)packages/kit/src/runtime/client/client.js:3093

+ 90 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 8 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with render_response (cyclomatic 105), form.svelte.form (cyclomatic 84), _start_router (cyclomatic 76). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cyclomatic Complexity from 2.3 to about 3.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Prevented

203 method(s) exceeded the cognitive complexity threshold of 15; the worst was crawl at 227.

form::create_instance::(anonymous)::handle_input (cognitive 36) · ×3packages/kit/src/runtime/client/remote-functions/form.svelte.js:488
respond.internal_respond::resolve (cognitive 78) · ×2packages/kit/src/runtime/server/respond.js:593
prerender (cognitive 20) · ×2packages/kit/src/runtime/app/server/remote/prerender.js:62
crawl (cognitive 227)packages/kit/src/core/postbuild/crawl.js:34
render_response (cognitive 189)packages/kit/src/runtime/server/page/render.js:55

+ 123 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 58 bodies over 30 down to 30 or less in Cognitive Complexity — start with crawl (cognitive 227), render_response (cognitive 189), index.statically_analyse_page_options (cognitive 120). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 58 together lifts Cognitive Complexity from 2.0 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes6.9 / 10Adequate✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.9 / 10 · rule-coverage 100% · ceiling Prevented

32 over-large unit(s) detected — types, modules or files that carry too much.

FunctionTooLong: respond.internal_respond · ×30packages/kit/src/runtime/server/respond.js:93
FileTooLong: client/client.js · ×2packages/kit/src/runtime/client/client.js

What to do

  1. Resolve the 30 FunctionTooLong finding(s) in God Classes — start with index.js (11), client.js (4), load_data.js (2). — One of this dimension's main actionable groups (30 warning-level).
  2. Resolve the 2 FileTooLong finding(s) in God Classes — start with client.js, respond.js. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication10.0 / 10Exemplary✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 duplicated block group(s) detected. 0.0 % of the production lines (0 of 38,493) are in a reported copy.

✓ On the Gold path — maintain.

Detailed fixes: d4_recommendation.md.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

11 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 11 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D10 · Test Quality8.9 / 10Strong✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Prevented

97 skipped (4 with a documented reason), 29 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2079 tests.

Skipped test: (unnamed test) · ×93packages/kit/test/apps/writes/test/test.js:43
No assertions: Server hooks can be added and removed · ×29packages/kit/test/apps/writes/test/test.js:156
Skipped (documented): (unnamed test) · ×4packages/kit/test/apps/basics/test/vitest/server.spec.js:244

What to do

  1. Resolve the 93 Skipped test finding(s) in Test Quality — start with test.js (54), server.test.js (11), paths.test.js (10). — One of this dimension's main actionable groups (93 warning-level).
  2. Resolve the 29 No assertions finding(s) in Test Quality — start with client.test.js (15), test.js (9), url.spec.js (2). — One of this dimension's main actionable groups (29 warning-level).

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene9.3 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 100% · ceiling Verified

13 outdated direct production npm dependency(ies) of 23 graded, 0 pinning defect(s), across 76 package.json (13 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Outdated (npm): @cloudflare/workers-types · ×13

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance0.0 / 10Critical✓ Tool-verified

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Verified

14 of 234 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 234 package(s) this repository's committed lockfile installs for a consumer — its 23 production, optional and peer dependency(ies), across 13 product package.json manifest(s), and everything those install in turn. Its 493 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.

Banned license: @img/sharp-libvips-darwin-arm64 · ×14REDACTED:2522

What to do

  1. Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).

Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.

D15 · Churn × Complexity Hotspots9.1 / 10Stronggated by 36 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 9.1 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: packages/kit/src/runtime/server/page/render.js (22×101=2222); packages/kit/src/runtime/server/respond.js (15×146=2190); packages/kit/src/runtime/client/client.js (27×71=1917) Repeated repair below the complexity floor: packages/kit/test/apps/async/test/test.js (8 of 12 changes were fixes); packages/adapter-vercel/utils.js (5 of 9 changes were fixes); packages/adapter-bun/index.js (4 of 6 changes were fixes)

Hotspot: packages/kit/src/runtime/server/page/render.js · ×30packages/kit/src/runtime/server/page/render.js:55
Repeated repair: packages/kit/test/apps/async/test/test.js · ×6packages/kit/test/apps/async/test/test.js:841

What to do

  1. Resolve the 30 Hotspot finding(s) in Churn × Complexity Hotspots — start with index.js (9), client.js (2), render.js. — One of this dimension's main actionable groups (30 warning-level).
  2. Resolve the 6 Repeated repair finding(s) in Churn × Complexity Hotspots — start with test.js (2), REDACTED (2), index.js. — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D16 · Bus Factor7.0 / 10Strong✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Documented

35 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/kit/src/runtime/server/remote-functions.js. Counted over 119 of the 245 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt9.7 / 10Stronggated by 3 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Prevented

3 deducted task-comment markers across 0 LoC (0.2/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×3packages/adapter-vercel/test/apps/split/test/test.ts:17

What to do

  1. Resolve the 3 TodoComment finding(s) in Explicit Debt — start with test.ts (3). — One of this dimension's main actionable groups (3 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality6.8 / 10Adequate✓ Tool-verified

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 6.8 / 10 · rule-coverage 100% · ceiling Documented

1 of 2 documentation facets pass in full; short on: F2 example. 102 document(s) read across 13 unit(s).

Documentation: no build, run or usage example · ×7packages/adapter-auto/README.md:1

What to do

  1. Resolve the 7 Documentation finding(s) in Documentation Quality — start with README.md (7). — One of this dimension's main actionable groups (7 recommendation-level).

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundpackages/package/package.json:49

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

No domain types leak across context boundaries (11 contexts). Contexts: adapter-auto, adapter-bun, adapter-cloudflare, adapter-netlify, adapter-node, adapter-static, adapter-vercel, enhanced-img, kit, package, test-redirect-importer.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value9.5 9.3 / 10Exemplary✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 98% · ceiling Documented

8 of 1578 judged comments only repeat the code they sit on (0.5 %). 44 comment(s) in another language or script were not judged.

redundant comment · ×3packages/kit/src/exports/vite/build/index.js:185
doc comments repeat the names · ×2packages/kit/src/runtime/app/forms/client.js:54

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion8.3 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.3 / 10 · rule-coverage 100% · ceiling Documented

1 of 12 build units (npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

42 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)2.2 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 2.2 / 10 · rule-coverage 100% · ceiling Documented

17 finding(s): 0 critical, 5 high, 12 medium, 0 low. semgrep hit a parse error in 9 file(s) — `packages/adapter-bun/index.d.ts` (line 39, line 57), `packages/adapter-bun/internal.d.ts` (line 13), `packages/adapter-netlify/ambient.d.ts` (line 7), `packages/kit/src/exports/public.d.ts` (line 122, line 358, line 364, …), `packages/kit/src/runtime/app/paths/types.d.ts` (lines 10–14), … (+4 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 2 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities4.6 / 10Weak✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 4.6 / 10 · rule-coverage 100% · ceiling Documented

12 finding(s): 1 critical, 5 high, 5 medium, 1 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 119 of the 245 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.9 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: fallback.js↔index.js 67%; REDACTED↔index.js 60%; REDACTED↔handler.js 52%

Change coupling: fallback.js ↔ index.js · ×4packages/kit/src/core/postbuild/fallback.js:1

What to do

  1. Resolve the 4 Change coupling finding(s) in Change Coupling — start with REDACTED (2), fallback.js, index.js. — One of this dimension's main actionable groups (4 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC3 · Page structure5.0 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — packages/kit/src/core/config/default-error.html:2
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — playgrounds/basic/src/app.html:2

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AX10 · Code composition9.8 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

C2 · Access Controls4.7 / 10Weak✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

  • Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.

What to do

  • Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `match_implementation` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/kit/src/runtime/app/paths/internal/client.js:21
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×36) — packages/adapter-bun/test/apps/basic/test/server.test.js:21, packages/adapter-cloudflare/test/apps/workers/test/test.js:31, packages/kit/src/runtime/server/page/csp.spec.js:45, …
  • `end` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:147
  • `recordException` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:148
  • `getActiveSpan` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:161

What to do

  • Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)9.7 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability7.6 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 6/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/adapter-netlify`, `packages/adapter-node`, `packages/package`, `packages/test-redirect-importer`, `playgrounds/basic`.
  • `packages/adapter-bun/src/handler.js` reports through `console.*` at line 7 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/adapter-bun/src/handler.js:7
  • `packages/adapter-bun/src/handler.js` reports through `console.*` at line 68 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/adapter-bun/src/handler.js:68
  • `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 108 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/runtime/server/errors.js:108
  • `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 110 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/runtime/server/errors.js:110
  • `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 112 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/runtime/server/errors.js:112
  • `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 129 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/runtime/server/errors.js:129
  • `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 141 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/runtime/server/errors.js:141
  • `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 147 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/runtime/server/errors.js:147
  • `packages/kit/src/runtime/server/instance.js` reports through `console.*` at line 84 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/runtime/server/instance.js:84
  • `packages/kit/src/runtime/server/instance.js` reports through `console.*` at line 106 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/runtime/server/instance.js:106
  • `packages/kit/src/runtime/client/remote-functions/prerender.svelte.js` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/runtime/client/remote-functions/prerender.svelte.js:29
  • `packages/kit/src/messages/internal/build.js` reports through `console.*` at line 57 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/messages/internal/build.js:57
  • `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/exports/hooks/sequence.js:23
  • `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 27 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/exports/hooks/sequence.js:27
  • `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/exports/hooks/sequence.js:32
  • `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 36 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/exports/hooks/sequence.js:36
  • `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/exports/hooks/sequence.js:42
  • `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/exports/hooks/sequence.js:45
  • `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/exports/hooks/sequence.js:49
  • `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 54 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/exports/hooks/sequence.js:54
  • `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 58 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/exports/hooks/sequence.js:58
  • `packages/kit/src/core/utils.js` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/core/utils.js:43
  • `packages/kit/src/core/utils.js` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/core/utils.js:46
  • `packages/kit/src/core/utils.js` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/core/utils.js:50
  • `packages/kit/src/core/sync/write_client_manifest.js` reports through `console.*` at line 165 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/core/sync/write_client_manifest.js:165
  • `packages/kit/src/core/postbuild/prerender.js` reports through `console.*` at line 439 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/kit/src/core/postbuild/prerender.js:439

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
  • Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/ci.yml:24

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

What to do

  • Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • `execSync` in `get_adapter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/adapter-auto/index.js:103
  • `fs.existsSync` in `asset_meta` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/adapter-bun/index.js:65, packages/adapter-bun/index.js:66
  • `fs.rmSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — packages/adapter-bun/index.js:92, packages/adapter-cloudflare/index.js:84, packages/adapter-cloudflare/index.js:85
  • `fs.writeFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×7) — packages/adapter-bun/index.js:107, packages/adapter-bun/index.js:138, packages/adapter-cloudflare/index.js:106, …
  • `fs.rmSync` in `create_assets` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/adapter-bun/index.js:240
  • `fs.existsSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×7) — packages/adapter-cloudflare/index.js:31, packages/adapter-cloudflare/index.js:32, packages/adapter-cloudflare/index.js:39, …
  • `fs.mkdirSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — packages/adapter-cloudflare/index.js:87, packages/adapter-cloudflare/index.js:88, packages/adapter-cloudflare/index.js:94
  • `fs.readFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/adapter-cloudflare/index.js:154, packages/adapter-cloudflare/index.js:178
  • `fs.copyFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/adapter-cloudflare/index.js:162
  • `existsSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×5) — packages/adapter-netlify/index.js:42, packages/adapter-netlify/index.js:48, packages/adapter-netlify/index.js:64, …
  • `rmSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×7) — packages/adapter-netlify/index.js:55, packages/adapter-netlify/index.js:56, packages/adapter-netlify/index.js:60, …
  • `readdirSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/adapter-netlify/index.js:65

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

R10 · Code Duplication8.1 / 10Strong✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 10 duplicated blocks under packages/ have copies in at least two of the sibling directories adapter-auto, adapter-bun, adapter-cloudflare, adapter-netlify, adapter-node, adapter-static (+3 more sibling(s) not listed) — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/adapter-bun/index.js:169
  • packages/kit/src/runtime/client/remote-functions/query-live/proxy.js:21 · packages/kit/src/runtime/client/remote-functions/query/proxy.js:30 — the two spans are one implementation copied and then locally edited — 433 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/runtime/client/remote-functions/query-live/proxy.js:21
  • packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:290 · packages/kit/src/runtime/client/remote-functions/query/instance.svelte.js:167 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:290
  • packages/kit/src/runtime/server/page/load_data.js:46 · packages/kit/src/runtime/server/page/load_data.js:143 — the two spans are one implementation copied and then locally edited — 167 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/runtime/server/page/load_data.js:46
  • packages/adapter-bun/index.js:169 · packages/adapter-node/index.js:82 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapter-bun/index.js:169
  • packages/adapter-static/platforms.js:34 · packages/adapter-vercel/index.js:407 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/adapter-static/platforms.js:34
  • packages/kit/src/runtime/app/server/remote/query.js:432 · packages/kit/src/runtime/app/server/remote/query.js:519 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/runtime/app/server/remote/query.js:432
  • packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:25 · packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:69 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:25
  • packages/adapter-auto/index.js:53 · packages/kit/src/utils/import.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/adapter-auto/index.js:53
  • packages/kit/src/runtime/client/remote-functions/command.svelte.js:79 · packages/kit/src/runtime/client/remote-functions/form.svelte.js:302 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/runtime/client/remote-functions/command.svelte.js:79
  • packages/kit/src/runtime/server/data/index.js:39 · packages/kit/src/runtime/server/page/index.js:171 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/runtime/server/data/index.js:39
  • packages/kit/src/cli.js:48 · packages/package/src/cli.js:49 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/cli.js:48
  • packages/kit/src/runtime/app/paths/client.js:10 · packages/kit/src/runtime/app/paths/server.js:11 — the two spans are one implementation copied and then locally edited — 103 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/runtime/app/paths/client.js:10
  • packages/kit/src/messages/internal/build.js:22 · packages/kit/src/messages/internal/server.js:13 — the two spans are one implementation copied and then locally edited — 91 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/messages/internal/build.js:22
  • packages/kit/src/pathname.js:1 · packages/kit/src/pathname.js:24 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/kit/src/pathname.js:1
  • packages/adapter-cloudflare/index.js:27 · packages/adapter-netlify/index.js:32 — the two spans are one implementation copied and then locally edited — 74 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/adapter-cloudflare/index.js:27
  • packages/kit/src/exports/vite/build/index.js:182 · packages/kit/src/exports/vite/dev/index.js:365 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/exports/vite/build/index.js:182
  • packages/kit/src/messages/internal/server.js:13 · packages/kit/src/messages/internal/shared.js:28 — the two spans are one implementation copied and then locally edited — 72 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/messages/internal/server.js:13
  • packages/kit/src/runtime/app/forms/client.js:114 · packages/kit/src/runtime/client/remote-functions/form.svelte.js:404 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/runtime/app/forms/client.js:114
  • packages/kit/src/runtime/app/server/remote/requested.js:164 · packages/kit/src/runtime/app/server/remote/requested.js:186 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/runtime/app/server/remote/requested.js:164
  • packages/enhanced-img/src/vite-plugin.js:364 · packages/enhanced-img/src/vite-plugin.js:406 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/enhanced-img/src/vite-plugin.js:364
  • packages/kit/src/exports/vite/static_analysis/index.js:106 · packages/kit/src/exports/vite/static_analysis/index.js:175 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/exports/vite/static_analysis/index.js:106
  • packages/kit/src/messages/internal/build.js:22 · packages/kit/src/messages/internal/shared.js:28 — the two spans are one implementation copied and then locally edited — 57 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/messages/internal/build.js:22
  • packages/kit/src/runtime/app/server/remote/query.js:88 · packages/kit/src/runtime/app/server/remote/query.js:186 · packages/kit/src/runtime/app/server/remote/query.js:363 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/runtime/app/server/remote/query.js:88
  • packages/kit/src/runtime/client/client.js:2121 · packages/kit/src/runtime/client/client.js:2937 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/runtime/client/client.js:2121
  • packages/kit/src/core/postbuild/crawl.js:67 · packages/kit/src/core/postbuild/crawl.js:80 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/core/postbuild/crawl.js:67
  • packages/kit/src/runtime/app/server/index.js:66 · packages/kit/src/runtime/server/fetch.js:104 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/runtime/app/server/index.js:66
  • packages/kit/src/runtime/app/server/remote/query.js:110 · packages/kit/src/runtime/app/server/remote/query.js:201 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/runtime/app/server/remote/query.js:110
  • packages/kit/src/runtime/client/client.js:2484 · packages/kit/src/runtime/server/errors.js:21 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/runtime/client/client.js:2484
  • packages/kit/src/runtime/client/remote-functions/query-live/index.js:13 · packages/kit/src/runtime/client/remote-functions/query/index.js:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/runtime/client/remote-functions/query-live/index.js:13
  • packages/kit/src/core/postbuild/analyse.js:73 · packages/kit/src/runtime/client/client.js:1130 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/kit/src/core/postbuild/analyse.js:73
  • packages/kit/src/exports/vite/build/index.js:723 · packages/kit/src/exports/vite/dev/generate_manifest.js:58 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/exports/vite/build/index.js:723
  • packages/kit/src/exports/vite/dev/index.js:430 · packages/kit/src/exports/vite/preview/index.js:216 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/exports/vite/dev/index.js:430
  • packages/kit/src/runtime/client/remote-functions/prerender.svelte.js:157 · packages/kit/src/runtime/client/remote-functions/query/instance.svelte.js:130 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/runtime/client/remote-functions/prerender.svelte.js:157
  • packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:240 · packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:252 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:240
  • packages/kit/src/runtime/server/remote-functions.js:420 · packages/kit/src/runtime/server/remote-functions.js:472 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/kit/src/runtime/server/remote-functions.js:420
  • packages/kit/src/utils/fork.js:24 · packages/package/src/cli.js:100 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/kit/src/utils/fork.js:24
  • packages/kit/src/utils/imports.js:26 · packages/package/src/index.js:269 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/kit/src/utils/imports.js:26
  • packages/adapter-vercel/index.js:210 · packages/adapter-vercel/index.js:300 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/adapter-vercel/index.js:210
  • packages/kit/src/cli.js:15 · packages/package/src/cli.js:11 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/kit/src/cli.js:15

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries9.7 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • packages/enhanced-img/src/vite-plugin.js:262 reaches into another package with a relative path (../types/internal.js) — import the package by name instead. — packages/enhanced-img/src/vite-plugin.js:262
  • packages/kit/test/apps/basics/test/vitest/server.spec.js:11 reaches past another workspace package's public entry into its internals with a relative path (../../../../../src/runtime/server/page/hash_bytes.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/kit/test/apps/basics/test/vitest/server.spec.js:11
  • packages/kit/test/apps/options/unit-test/vite.spec.js:5 reaches past another workspace package's public entry into its internals with a relative path (../../../../src/utils/format.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/kit/test/apps/options/unit-test/vite.spec.js:5
  • packages/kit/test/build-errors/prerender.spec.js:2 reaches past another workspace package's public entry into its internals with a relative path (../../src/utils/format.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/kit/test/build-errors/prerender.spec.js:2
  • scripts/sync-all.js:4 reaches into another package with a relative path (../packages/kit/src/core/config/index.js) — import the package by name instead. — scripts/sync-all.js:4
  • scripts/sync-all.js:5 reaches into another package with a relative path (../packages/kit/src/core/sync/sync.js) — import the package by name instead. — scripts/sync-all.js:5
  • scripts/sync-all.js:6 reaches into another package with a relative path (../packages/kit/src/core/sync/create_manifest_data/index.js) — import the package by name instead. — scripts/sync-all.js:6

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity8.0 / 10Strong✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • render_response has cyclomatic complexity 96 and cognitive complexity 173; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/server/page/render.js:55
  • crawl has cyclomatic complexity 60 and cognitive complexity 226; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/postbuild/crawl.js:34
  • navigate has cyclomatic complexity 48 and cognitive complexity 72; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/client/client.js:1940
  • statically_analyse_page_options has cyclomatic complexity 45 and cognitive complexity 120; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/exports/vite/static_analysis/index.js:32
  • fetch has cyclomatic complexity 41 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/server/fetch.js:34
  • walk has cyclomatic complexity 40 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/sync/create_manifest_data/index.js:139
  • create_routes_and_nodes has cyclomatic complexity 39 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/sync/create_manifest_data/index.js:120
  • render_page has cyclomatic complexity 39 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/server/page/index.js:42
  • prerender has cyclomatic complexity 37 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/postbuild/prerender.js:47
  • (anonymous) has cyclomatic complexity 35 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/client/client.js:3142
  • should_ignore has cyclomatic complexity 35 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/exports/vite/static_analysis/utils.js:24
  • build_server_nodes has cyclomatic complexity 33 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/exports/vite/build/build_server.js:28
  • handle_submit has cyclomatic complexity 33 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/app/forms/client.js:113
  • (anonymous) has cyclomatic complexity 31 and cognitive complexity 92; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/sync/create_manifest_data/sort.js:66
  • adapt has cyclomatic complexity 31 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/adapter-vercel/index.js:21
  • (anonymous) has cyclomatic complexity 30 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/form-utils.js:806
  • get_navigation_result_from_branch has cyclomatic complexity 28 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/client/client.js:965
  • load_route has cyclomatic complexity 27 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/client/client.js:1373
  • analyse has cyclomatic complexity 27 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/postbuild/analyse.js:31
  • generate_app_types has cyclomatic complexity 26 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/sync/write_app_types.js:107
  • visit has cyclomatic complexity 26 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/postbuild/prerender.js:376
  • (anonymous) has cyclomatic complexity 26 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/adapter-node/src/static.js:172
  • treeshake_prerendered_remotes has cyclomatic complexity 25 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/exports/vite/build/remote.js:21
  • process_ssr_build has cyclomatic complexity 25 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/exports/vite/build/index.js:452
  • write_all_types has cyclomatic complexity 25 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/sync/write_types/index.js:58
  • (anonymous) has cyclomatic complexity 23 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/client/client.js:3311
  • adapt has cyclomatic complexity 23 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/adapter-cloudflare/index.js:29
  • render_endpoint has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/server/endpoint.js:14
  • handler has cyclomatic complexity 22 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:109
  • update_types has cyclomatic complexity 22 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/sync/write_types/index.js:215
  • update_element has cyclomatic complexity 21 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/enhanced-img/src/vite-plugin.js:85
  • save has cyclomatic complexity 21 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/postbuild/prerender.js:542
  • (anonymous) has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/exports/vite/dev/index.js:311
  • (anonymous) has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/core/sync/write_types/index.js:815
  • exec has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:190
  • validate has cyclomatic complexity 20 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:145
  • _start has cyclomatic complexity 20 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/client/client.js:461
  • handle_remote_call_internal has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kit/src/runtime/server/remote-functions.js:198
  • get_routes_json has cyclomatic complexity 19 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:136
  • create_env_modules has cyclomatic complexity 18 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:152
R3 · Large Files7.5 / 10Strong✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • packages/kit/src/runtime/client/client.js has 3278 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/runtime/client/client.js:1
  • REDACTED has 2256 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/kit/src/runtime/form-utils.js has 819 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/runtime/form-utils.js:1
  • packages/kit/src/core/sync/write_types/index.js has 782 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/core/sync/write_types/index.js:1
  • packages/kit/src/runtime/client/remote-functions/form.svelte.js has 688 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/runtime/client/remote-functions/form.svelte.js:1
  • packages/kit/src/core/postbuild/prerender.js has 622 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/core/postbuild/prerender.js:1
  • packages/kit/src/exports/vite/index.js has 615 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/exports/vite/index.js:1
  • packages/kit/src/runtime/app/server/remote/query.js has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/runtime/app/server/remote/query.js:1
  • packages/kit/src/runtime/server/page/render.js has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/runtime/server/page/render.js:1
  • packages/adapter-vercel/index.js has 582 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/adapter-vercel/index.js:1
  • packages/kit/src/runtime/server/remote-functions.js has 537 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/runtime/server/remote-functions.js:1
  • packages/adapter-netlify/index.js has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/adapter-netlify/index.js:1
  • packages/kit/src/core/sync/create_manifest_data/index.js has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/core/sync/create_manifest_data/index.js:1
  • packages/kit/src/runtime/server/page/load_data.js has 440 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/runtime/server/page/load_data.js:1
  • packages/kit/src/exports/vite/dev/index.js has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/kit/src/exports/vite/dev/index.js:1
  • packages/enhanced-img/src/vite-plugin.js has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/enhanced-img/src/vite-plugin.js:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage8.6 / 10Strong✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • packages/kit/src/core/postbuild/crawl.spec.js:6 imports './fixtures', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/kit/src/core/postbuild/crawl.spec.js:6
  • packages/kit/test/apps/basics/src/routes/cookies/enhanced/basic/+page.server.ts:1 imports './$types', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/kit/test/apps/basics/src/routes/cookies/enhanced/basic/+page.server.ts:1
  • packages/kit/test/apps/writes/test/test.js:159 imports '../src/hooks.server.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/kit/test/apps/writes/test/test.js:159
  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×33) — packages/kit/src/runtime/server/page/index.js:1, packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:1, packages/kit/src/runtime/server/data/index.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • This repository declares test tooling, and the ✓ above records that declaration — but packages/kit/src/core/postbuild/crawl.spec.js and 2 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/kit/src/core/postbuild/crawl.spec.js:6
R7 · Dead Code9.5 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • 1 file(s) (~91 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/kit/src/core/sync/write_types/test/actions
  • 32 file(s) (~285 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/kit/src/core/sync/write_types/test/app-types
  • 6 file(s) (~37 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/kit/src/core/sync/write_types/test/layout
  • 8 file(s) (~40 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/kit/src/core/sync/write_types/test/layout-advanced
  • 10 file(s) (~114 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/kit/src/core/sync/write_types/test/param-type-inference
  • 3 file(s) (~22 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/kit/src/core/sync/write_types/test/simple-page-server-and-shared
  • 4 file(s) (~39 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/kit/src/core/sync/write_types/test/simple-page-server-only
  • 4 file(s) (~29 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/kit/src/core/sync/write_types/test/simple-page-shared-only
  • 9 file(s) (~59 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/kit/src/core/sync/write_types/test/slugs
  • 7 file(s) (~14 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/kit/src/core/sync/write_types/test/slugs-layout-not-all-pages-have-load
  • 1 file(s) (~1 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/package/test/watch
  • Unreachable from the 1623 application, 207 tooling and 2270 test entry point(s) detected in this repo. Gate removals on `pnpm run check` — an undetected custom entry would make these reachable.
  • no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/kit/src/runtime/server/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/kit/src/runtime/server/instance.js
  • no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/kit/src/runtime/client/remote-functions/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — packages/kit/src/runtime/client/remote-functions/query-batch.svelte.js, packages/kit/src/runtime/client/remote-functions/query/index.js, packages/kit/src/runtime/client/remote-functions/query-live/index.js
  • no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×14) — packages/kit/src/runtime/server/index.js, packages/kit/src/runtime/app/stores.js, scripts/check-dependencies.js, …
  • no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/kit/src/runtime/client/bundle.js, packages/kit/src/runtime/client/entry.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/kit/src/runtime/client/client-entry.js
  • no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/kit/src/runtime/app/environment/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/kit/src/runtime/app/env/index.js
  • This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×8) — packages/kit/src/core/sync/write_types/test/app-types/+page.js:56, packages/kit/src/core/sync/write_types/test/app-types/+page.js:61, packages/kit/src/core/sync/write_types/test/app-types/+page.js:72, …

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene8.5 / 10Strong✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Declared in packages/adapter-netlify/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Every import is type-only — move it to devDependencies. — packages/adapter-cloudflare/files/worker.js:34

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports7.9 / 10Strong✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

  • packages/kit/src/runtime/app/paths/server.js → packages/kit/src/runtime/server/internal.js → packages/kit/src/runtime/server/remote-functions.js → packages/kit/src/runtime/app/paths/server.js (one verified cycle inside a mutually-dependent group of 6 files) — packages/kit/src/runtime/app/paths/server.js:5

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • `httpServer.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) (×2) — packages/adapter-node/src/index.js:77, packages/adapter-node/src/index.js:91

What to do

  • Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

  • `find_overridden_config` is exported and takes `config: object` from its caller, and it calls itself at line 331 (`find_overridden_config`) with a piece of `config` — and nowhere in `find_overridden_config` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `find_overridden_config` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/kit/src/exports/vite/utils.js:331

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X2 · Cancellation propagation6.4 / 10Adequate✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 4/10 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `fetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/kit/src/runtime/server/fetch.js:34
  • `init` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/kit/src/runtime/server/instance.js:59
  • `render_response` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/kit/src/runtime/server/page/render.js:55
  • `check` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/kit/src/runtime/app/state/client.svelte.js:150
  • `dev` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/kit/src/exports/vite/dev/index.js:42
  • `read` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/adapter-netlify/files/edge.js:18

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped4.2 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `src_var_name` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — packages/enhanced-img/src/vite-plugin.js:426, packages/enhanced-img/src/vite-plugin.js:428, packages/enhanced-img/src/vite-plugin.js:436
  • `serialize_img_attributes(content,attributes,{src:`{${src_var_name}}`})` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value. — packages/enhanced-img/src/vite-plugin.js:430
  • `serialize_img_attributes(content,attributes,{src:`{${src_var_name}.img.src}`,width:`${src_var_name}.img.w`,height:`${…` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value. — packages/enhanced-img/src/vite-plugin.js:439
  • `attrs.join(' ')` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value. — packages/kit/src/runtime/server/page/serialize_data.js:95

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×29) — packages/package/src/index.js:249, packages/kit/src/cli.js:92, packages/kit/src/utils/error.js:25, …
  • `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×5) — packages/kit/src/runtime/server/remote-functions.js:82, packages/kit/src/runtime/client/remote-functions/prerender.svelte.js:49, packages/kit/src/exports/internal/server/event.js:15, …
  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×2) — packages/kit/src/runtime/client/client.js:837, packages/kit/src/runtime/client/client.js:1614

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types2.4 / 10Critical✓ Tool-verified

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 3/66 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.

What to do

  • The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

WCAG coverage — what static analysis assessed

Statically assessed 8 of 55 WCAG 2.2 Level A/AA success criteria (15%; ≈16% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 47 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 47 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.1, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health55%Adequate — gated by D1, D2, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture92%ExemplaryStrongest area.
Maturity70%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness64%Adequate — gated by D14, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security60%Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility78%StrongSolid.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • P12 CI test-gate honesty — 4 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
  • AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — no exported interface declares behaviour
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (the repository): package.json has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
  • D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript surface was not measured.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — 9 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: packages/adapter-node/src/index.js:37 (http.createServer())
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 27 finding(s)
D14 · License Compliance · Banned license · ×14
  • Banned license: @img/sharp-libvips-darwin-arm64 REDACTED:2522 — `@img/sharp-libvips-darwin-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-darwin-x64 REDACTED:2532 — `@img/sharp-libvips-darwin-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-arm REDACTED:2555 — `@img/sharp-libvips-linux-arm` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-arm64 REDACTED:2543 — `@img/sharp-libvips-linux-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-ppc64 REDACTED:2567 — `@img/sharp-libvips-linux-ppc64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-riscv64 REDACTED:2579 — `@img/sharp-libvips-linux-riscv64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-s390x REDACTED:2591 — `@img/sharp-libvips-linux-s390x` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linux-x64 REDACTED:2603 — `@img/sharp-libvips-linux-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linuxmusl-arm64 REDACTED:2615 — `@img/sharp-libvips-linuxmusl-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-libvips-linuxmusl-x64 REDACTED:2627 — `@img/sharp-libvips-linuxmusl-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-wasm32 REDACTED:2749 — `@img/sharp-wasm32` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later AND MIT`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-win32-arm64 REDACTED:2769 — `@img/sharp-win32-arm64` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-win32-ia32 REDACTED:2781 — `@img/sharp-win32-ia32` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
  • Banned license: @img/sharp-win32-x64 REDACTED:2793 — `@img/sharp-win32-x64` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
D30 · Dependency Vulnerabilities · High CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · Document without a <title> · ×1
  • Document without a <title> playgrounds/basic/src/app.html:2 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×1
  • REDACTED
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) packages/kit/src/runtime/app/paths/server.js:5 — packages/kit/src/runtime/app/paths/server.js → packages/kit/src/runtime/server/internal.js → packages/kit/src/runtime/server/remote-functions.js → packages/kit/src/runtime/app/paths/server.js (one verified cycle inside a mutually-dependent group of 6 files)
Serious — 700 finding(s)
D10 · Test Quality · Skipped test · ×93
  • Skipped test: (unnamed test) packages/kit/test/apps/writes/test/test.js:43 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/writes/test/test.js:68 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/writes/test/test.js:107 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/writes/test/test.js:131 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/writes/test/test.js:157 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/prerendered-app-error-pages/test/test.js:16 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/prerendered-app-error-pages/test/test.js:17 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-3/test/test.js:12 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/env.test.js:17 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/env.test.js:33 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/env.test.js:42 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/env.test.js:53 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/env.test.js:72 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/env.test.js:84 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/env.test.js:92 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/service-worker.test.js:7 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/service-worker.test.js:10 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/service-worker.test.js:21 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/test.js:5 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/test.js:78 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/test.js:90 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/test.js:102 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/test.js:114 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/test.js:130 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/kit/test/apps/options-2/test/test.js:153 — Skipped — switched off by test.skip
  • + 68 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×40
  • Sync-over-async blocking packages/adapter-auto/index.js:103 — `execSync` in `get_adapter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-bun/index.js:65 — `fs.existsSync` in `asset_meta` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-bun/index.js:66 — `fs.existsSync` in `asset_meta` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-bun/index.js:92 — `fs.rmSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-bun/index.js:107 — `fs.writeFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-bun/index.js:138 — `fs.writeFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-bun/index.js:240 — `fs.rmSync` in `create_assets` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:31 — `fs.existsSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:32 — `fs.existsSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:39 — `fs.existsSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:45 — `fs.existsSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:84 — `fs.rmSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:85 — `fs.rmSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:87 — `fs.mkdirSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:88 — `fs.mkdirSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:94 — `fs.mkdirSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:106 — `fs.writeFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:153 — `fs.existsSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:154 — `fs.readFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:156 — `fs.writeFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:161 — `fs.existsSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:162 — `fs.copyFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:166 — `fs.writeFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:177 — `fs.existsSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/adapter-cloudflare/index.js:178 — `fs.readFileSync` in `adapt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • + 15 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×34
  • Swallowed exception (empty catch) packages/package/src/index.js:249 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/cli.js:92 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/utils/error.js:25 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/utils/imports.js:14 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/server/internal.js:98 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/server/remote-functions.js:82 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/server/sourcemaps.js:118 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/client/client.js:230 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/client/client.js:808 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/client/session-storage.js:10 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/client/session-storage.js:25 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/client/utils.js:140 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/client/remote-functions/form.svelte.js:790 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/client/remote-functions/prerender.svelte.js:49 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/client/remote-functions/shared.svelte.js:42 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/client/remote-functions/query-live/iterator.js:72 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/app/server/remote/prerender.js:115 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/runtime/app/server/remote/requested.js:290 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/exports/vite/index.js:542 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/exports/vite/utils.js:178 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/exports/vite/preview/index.js:154 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/exports/vite/dev/generate_manifest.js:154 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/exports/internal/server/event.js:15 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/core/sync/ts.js:6 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/kit/src/core/sync/write_types/index.js:122 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • + 9 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×33
  • No test reaches this file packages/kit/src/runtime/server/page/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/server/data/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/server/page/respond_with_error.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/server/instance.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/server/endpoint.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/adapter-cloudflare/files/worker.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/client/remote-functions/query-batch.svelte.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/server/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/app/state/server.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/adapter-netlify/files/edge.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/scripts/generate-dts.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/client/remote-functions/query/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/app/stores.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/adapter-vercel/files/serverless.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/server/env_module.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/client/remote-functions/query-live/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/adapter-netlify/files/serverless.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/adapter-vercel/files/catch-all.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/app/service-worker/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/client/entry.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/client/bundle.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/env/dynamic/private.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/env/dynamic/public.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/kit/src/runtime/app/environment/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 8 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×30
  • Hotspot: packages/kit/src/runtime/server/page/render.js packages/kit/src/runtime/server/page/render.js:55 — packages/kit/src/runtime/server/page/render.js changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 101 in render.render_response at line 55. 4 of those changes were fix/bug commits, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/server/page/render.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/runtime/server/respond.js packages/kit/src/runtime/server/respond.js:93 — packages/kit/src/runtime/server/respond.js changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 146 in respond.internal_respond at line 93. 2 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/server/respond.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/runtime/client/client.js packages/kit/src/runtime/client/client.js:3093 — packages/kit/src/runtime/client/client.js changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 71 in client._start_router at line 3093. 15 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/client/client.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/core/postbuild/prerender.js packages/kit/src/core/postbuild/prerender.js:47 — packages/kit/src/core/postbuild/prerender.js changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 107 in prerender.prerender at line 47. 2 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/core/postbuild/prerender.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/exports/vite/dev/index.js packages/kit/src/exports/vite/dev/index.js:42 — packages/kit/src/exports/vite/dev/index.js changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in index.dev at line 42. 5 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/exports/vite/dev/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/runtime/client/remote-functions/form.svelte.js packages/kit/src/runtime/client/remote-functions/form.svelte.js:70 — packages/kit/src/runtime/client/remote-functions/form.svelte.js changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 84 in form.svelte.form at line 70. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/client/remote-functions/form.svelte.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/runtime/form-utils.js packages/kit/src/runtime/form-utils.js:751 — packages/kit/src/runtime/form-utils.js changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 59 in form-utils.create_field_method at line 751. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/form-utils.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/core/sync/create_manifest_data/index.js packages/kit/src/core/sync/create_manifest_data/index.js:120 — packages/kit/src/core/sync/create_manifest_data/index.js changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 90 in index.create_routes_and_nodes at line 120. 3 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/core/sync/create_manifest_data/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/exports/vite/index.js packages/kit/src/exports/vite/index.js:230 — packages/kit/src/exports/vite/index.js changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in index.kit at line 230. 9 of those changes were fix/bug commits, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/exports/vite/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/runtime/server/page/index.js packages/kit/src/runtime/server/page/index.js:42 — packages/kit/src/runtime/server/page/index.js changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in index.render_page at line 42. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/server/page/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/adapter-vercel/index.js packages/adapter-vercel/index.js:21 — packages/adapter-vercel/index.js changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in index.plugin.adapt at line 21. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/adapter-vercel/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/exports/vite/preview/index.js packages/kit/src/exports/vite/preview/index.js:69 — packages/kit/src/exports/vite/preview/index.js changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in index.preview.<returned closure> at line 69. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/exports/vite/preview/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/adapter-cloudflare/index.js packages/adapter-cloudflare/index.js:29 — packages/adapter-cloudflare/index.js changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in index.default.adapt at line 29. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/adapter-cloudflare/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/core/postbuild/analyse.js packages/kit/src/core/postbuild/analyse.js:31 — packages/kit/src/core/postbuild/analyse.js changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in analyse.analyse at line 31. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/core/postbuild/analyse.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/exports/vite/plugins/guard.js packages/kit/src/exports/vite/plugins/guard.js:29 — packages/kit/src/exports/vite/plugins/guard.js changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in guard.plugin_guard at line 29. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/exports/vite/plugins/guard.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/runtime/server/fetch.js packages/kit/src/runtime/server/fetch.js:18 — packages/kit/src/runtime/server/fetch.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in fetch.create_fetch at line 18. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/server/fetch.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/runtime/server/remote-functions.js packages/kit/src/runtime/server/remote-functions.js:198 — packages/kit/src/runtime/server/remote-functions.js changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in remote-functions.handle_remote_call_internal at line 198. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/server/remote-functions.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/core/sync/write_types/index.js packages/kit/src/core/sync/write_types/index.js:58 — packages/kit/src/core/sync/write_types/index.js changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in index.write_all_types at line 58. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/core/sync/write_types/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:38 — REDACTED changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in env.load_explicit_env at line 38. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/core/sync/write_app_types.js packages/kit/src/core/sync/write_app_types.js:107 — packages/kit/src/core/sync/write_app_types.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in write_app_types.generate_app_types at line 107. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/core/sync/write_app_types.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/runtime/server/page/load_data.js packages/kit/src/runtime/server/page/load_data.js:278 — packages/kit/src/runtime/server/page/load_data.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in load_data.create_universal_fetch at line 278. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/server/page/load_data.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/runtime/app/forms/client.js packages/kit/src/runtime/app/forms/client.js:113 — packages/kit/src/runtime/app/forms/client.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in client.enhance.handle_submit at line 113. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/app/forms/client.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/core/postbuild/crawl.js packages/kit/src/core/postbuild/crawl.js:34 — packages/kit/src/core/postbuild/crawl.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in crawl.crawl at line 34. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/core/postbuild/crawl.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:30 — REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in remote.plugin_remote at line 30. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/kit/src/runtime/app/server/remote/form.js packages/kit/src/runtime/app/server/remote/form.js:66 — packages/kit/src/runtime/app/server/remote/form.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in form.form at line 66. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/src/runtime/app/server/remote/form.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 5 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×30
  • FunctionTooLong: respond.internal_respond packages/kit/src/runtime/server/respond.js:93 — FunctionTooLong — internal_respond runs 420 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 320 over it, 4.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: form.svelte.form packages/kit/src/runtime/client/remote-functions/form.svelte.js:70 — FunctionTooLong — form runs 390 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 290 over it, 3.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: prerender.prerender packages/kit/src/core/postbuild/prerender.js:47 — FunctionTooLong — prerender runs 383 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 283 over it, 3.83× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: render.render_response packages/kit/src/runtime/server/page/render.js:55 — FunctionTooLong — render_response runs 339 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 239 over it, 3.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.dev packages/kit/src/exports/vite/dev/index.js:42 — FunctionTooLong — dev runs 250 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 150 over it, 2.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.kit packages/kit/src/exports/vite/index.js:230 — FunctionTooLong — kit runs 243 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 143 over it, 2.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.create_routes_and_nodes packages/kit/src/core/sync/create_manifest_data/index.js:120 — FunctionTooLong — create_routes_and_nodes runs 222 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 122 over it, 2.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: client._start_router packages/kit/src/runtime/client/client.js:3093 — FunctionTooLong — _start_router runs 212 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 112 over it, 2.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: builder.create_builder packages/kit/src/core/adapt/builder.js:59 — FunctionTooLong — create_builder runs 192 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 92 over it, 1.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.render_page packages/kit/src/runtime/server/page/index.js:42 — FunctionTooLong — render_page runs 188 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.plugin packages/adapter-vercel/index.js:12 — FunctionTooLong — plugin runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: client.navigate packages/kit/src/runtime/client/client.js:1940 — FunctionTooLong — navigate runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.plugin.adapt packages/adapter-vercel/index.js:21 — FunctionTooLong — plugin.adapt runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.tweak_types packages/kit/src/core/sync/write_types/index.js:663 — FunctionTooLong — tweak_types runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: client.load_route packages/kit/src/runtime/client/client.js:1373 — FunctionTooLong — load_route runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: client.enhance packages/kit/src/runtime/app/forms/client.js:57 — FunctionTooLong — enhance runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: load_data.create_universal_fetch packages/kit/src/runtime/server/page/load_data.js:278 — FunctionTooLong — create_universal_fetch runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: remote.plugin_remote REDACTED:30 — FunctionTooLong — plugin_remote runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: crawl.crawl packages/kit/src/core/postbuild/crawl.js:34 — FunctionTooLong — crawl runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: generate_manifest.generate_manifest packages/kit/src/exports/vite/dev/generate_manifest.js:25 — FunctionTooLong — generate_manifest runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.preview packages/kit/src/exports/vite/preview/index.js:21 — FunctionTooLong — preview runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: form.form packages/kit/src/runtime/app/server/remote/form.js:66 — FunctionTooLong — form runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: load_data.load_server_data packages/kit/src/runtime/server/page/load_data.js:22 — FunctionTooLong — load_server_data runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: validate._create_validator REDACTED:50 — FunctionTooLong — _create_validator runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: cookie.get_cookies packages/kit/src/runtime/server/cookie.js:42 — FunctionTooLong — get_cookies runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 5 more in this group — see findings.md.
D10 · Test Quality · No assertions · ×29
  • No assertions: Server hooks can be added and removed packages/kit/test/apps/writes/test/test.js:156 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: applies autofocus after an enhanced form submit packages/kit/test/apps/basics/test/playwright/client.test.js:12 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: location.assign packages/kit/test/apps/basics/test/playwright/client.test.js:1954 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: location.replace packages/kit/test/apps/basics/test/playwright/client.test.js:1972 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: app.invalidate packages/kit/test/apps/basics/test/playwright/client.test.js:1988 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: location.reload packages/kit/test/apps/basics/test/playwright/client.test.js:1993 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: app.goto packages/kit/test/apps/basics/test/playwright/client.test.js:2005 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: location.assign packages/kit/test/apps/basics/test/playwright/client.test.js:2011 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: app.goto packages/kit/test/apps/basics/test/playwright/client.test.js:2023 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: location.replace packages/kit/test/apps/basics/test/playwright/client.test.js:2029 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: navigation.event is populated packages/kit/test/apps/basics/test/playwright/cross-platform/client.test.js:346 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: scroll is restored after hitting the back button packages/kit/test/apps/basics/test/playwright/cross-platform/client.test.js:591 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: scroll positions are recovered on reloading the page packages/kit/test/apps/basics/test/playwright/cross-platform/client.test.js:688 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: same route hash links work more than once packages/kit/test/apps/basics/test/playwright/cross-platform/client.test.js:1111 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: replaces state if the data-sveltekit-replacestate router option is specified for the hash link packages/kit/test/apps/basics/test/playwright/cross-platform/client.test.js:1260 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: resets the active element after navigation packages/kit/test/apps/basics/test/playwright/cross-platform/test.js:856 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: focus works if page load has hash packages/kit/test/apps/basics/test/playwright/cross-platform/test.js:893 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: ignores navigation to URLs the app does not own packages/kit/test/apps/basics/test/playwright/cross-platform/test.js:930 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: remote form submit resolves after redirect navigation packages/kit/test/apps/async/test/client.test.js:1372 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: form reports validation issues packages/kit/test/apps/async/test/test.js:389 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: form handles unexpected error packages/kit/test/apps/async/test/test.js:398 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: form handles expected error packages/kit/test/apps/async/test/test.js:411 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: form error falls through a throwing +error.svelte to the one above packages/kit/test/apps/async/test/test.js:420 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: form redirects packages/kit/test/apps/async/test/test.js:433 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: distinct keyed form instances can attach independently packages/kit/src/runtime/client/remote-functions/form.svelte.spec.js:57 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 4 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R11 · Import Boundaries · Boundary violation [package · ×7
  • Boundary violation [package:relative-cross-package] packages/enhanced-img/src/vite-plugin.js:262 — packages/enhanced-img/src/vite-plugin.js:262 reaches into another package with a relative path (../types/internal.js) — import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] packages/kit/test/apps/basics/test/vitest/server.spec.js:11 — packages/kit/test/apps/basics/test/vitest/server.spec.js:11 reaches past another workspace package's public entry into its internals with a relative path (../../../../../src/runtime/server/page/hash_bytes.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] packages/kit/test/apps/options/unit-test/vite.spec.js:5 — packages/kit/test/apps/options/unit-test/vite.spec.js:5 reaches past another workspace package's public entry into its internals with a relative path (../../../../src/utils/format.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] packages/kit/test/build-errors/prerender.spec.js:2 — packages/kit/test/build-errors/prerender.spec.js:2 reaches past another workspace package's public entry into its internals with a relative path (../../src/utils/format.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:relative-cross-package] scripts/sync-all.js:4 — scripts/sync-all.js:4 reaches into another package with a relative path (../packages/kit/src/core/config/index.js) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] scripts/sync-all.js:5 — scripts/sync-all.js:5 reaches into another package with a relative path (../packages/kit/src/core/sync/sync.js) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] scripts/sync-all.js:6 — scripts/sync-all.js:6 reaches into another package with a relative path (../packages/kit/src/core/sync/create_manifest_data/index.js) — import the package by name instead.
D15 · Churn × Complexity Hotspots · Repeated repair · ×6
  • Repeated repair: packages/kit/test/apps/async/test/test.js packages/kit/test/apps/async/test/test.js:841 — packages/kit/test/apps/async/test/test.js changed 12 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is (anonymous) at line 841), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: prevent separate non-exported query.batch functions from sharing a batch”; “Revert "fix: preserve untouched selects during remote form validation" (#17184)”; “fix: preserve untouched selects during remote form validation (#17132)”; “fix: redact nested and typed underscore-prefixed remote form fields after invalid submissions (#17128)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/test/apps/async/test/test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/adapter-vercel/utils.js packages/adapter-vercel/utils.js:42 — packages/adapter-vercel/utils.js changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is utils.parse_isr_expiration at line 42), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: accept every Node.js version from 26 in adapter-vercel”; “fix(adapter-vercel): support Node.js 26”; “fix: escape prerendered paths used in Vercel route patterns”; “fix: keep the detected Bun minor in adapter-vercel runtime (#17331)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/adapter-vercel/utils.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/adapter-bun/index.js packages/adapter-bun/index.js:85 — packages/adapter-bun/index.js changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is index.default.adapt at line 85), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: serve immutable files with native Bun routes and match re-encoded static paths (#17123)”; “fix: respect runtime export conditions in server adapters (#17234)”; “fix: bundle dev deps (#17210)”; “fix: build Bun apps that use server instrumentation (#16898)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/adapter-bun/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/kit/test/apps/dev-only/test/test.js packages/kit/test/apps/dev-only/test/test.js:9 — packages/kit/test/apps/dev-only/test/test.js changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is (anonymous) at line 9), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: clarify errors for remote modules in server-only locations”; “fix links (#17289)”; “fix: simpler message URLs (#17285)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- packages/kit/test/apps/dev-only/test/test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: REDACTED REDACTED:50 — REDACTED changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is utils.dedent at line 50), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: quote route params whose names are not valid identifiers (#17661)”; “fix: leave unchanged generated files alone, and replace changed ones atomically (#17310)”; “fix: resolve every module entry point using kit.moduleExtensions (#17043)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: REDACTED REDACTED:14 — REDACTED changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is filesystem.copy at line 14), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: resolve every module entry point using kit.moduleExtensions (#17043)”; “fix: rebase sourcemaps when copying files (#17082)”; “fix: walk and copy directories without a stat per file (#16995)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:21:52 +01:00' --until='2026-11-14 21:21:52 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×6
  • Duplicated block (9 lines × 2 locations) packages/kit/src/core/postbuild/analyse.js:73 — packages/kit/src/core/postbuild/analyse.js:73 · packages/kit/src/runtime/client/client.js:1130 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (9 lines × 2 locations) packages/kit/src/exports/vite/build/index.js:723 — packages/kit/src/exports/vite/build/index.js:723 · packages/kit/src/exports/vite/dev/generate_manifest.js:58 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (9 lines × 2 locations) packages/kit/src/exports/vite/dev/index.js:430 — packages/kit/src/exports/vite/dev/index.js:430 · packages/kit/src/exports/vite/preview/index.js:216 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (9 lines × 2 locations) packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:240 — packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:240 · packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:252 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (9 lines × 2 locations) packages/kit/src/utils/fork.js:24 — packages/kit/src/utils/fork.js:24 · packages/package/src/cli.js:100 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (9 lines × 2 locations) packages/kit/src/utils/imports.js:26 — packages/kit/src/utils/imports.js:26 · packages/package/src/index.js:269 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
X2 · Cancellation propagation · Async function without AbortSignal · ×6
  • Async function without AbortSignal: fetch packages/kit/src/runtime/server/fetch.js:34 — `fetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: init packages/kit/src/runtime/server/instance.js:59 — `init` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: render_response packages/kit/src/runtime/server/page/render.js:55 — `render_response` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: check packages/kit/src/runtime/app/state/client.svelte.js:150 — `check` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: dev packages/kit/src/exports/vite/dev/index.js:42 — `dev` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: read packages/adapter-netlify/files/edge.js:18 — `read` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×6
  • Untrusted text written into markup unescaped packages/enhanced-img/src/vite-plugin.js:426 — `src_var_name` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped packages/enhanced-img/src/vite-plugin.js:428 — `src_var_name` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped packages/enhanced-img/src/vite-plugin.js:430 — `serialize_img_attributes(content,attributes,{src:`{${src_var_name}}`})` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value.
  • Untrusted text written into markup unescaped packages/enhanced-img/src/vite-plugin.js:436 — `src_var_name` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped packages/enhanced-img/src/vite-plugin.js:439 — `serialize_img_attributes(content,attributes,{src:`{${src_var_name}.img.src}`,width:`${src_var_name}.img.w`,height:`${…` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value.
  • Untrusted text written into markup unescaped packages/kit/src/runtime/server/page/serialize_data.js:95 — `attrs.join(' ')` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value.
D30 · Dependency Vulnerabilities · Medium CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×5
  • Duplicated block (10 lines × 2 locations) packages/kit/src/core/postbuild/crawl.js:67 — packages/kit/src/core/postbuild/crawl.js:67 · packages/kit/src/core/postbuild/crawl.js:80 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) packages/kit/src/runtime/app/server/index.js:66 — packages/kit/src/runtime/app/server/index.js:66 · packages/kit/src/runtime/server/fetch.js:104 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) packages/kit/src/runtime/app/server/remote/query.js:110 — packages/kit/src/runtime/app/server/remote/query.js:110 · packages/kit/src/runtime/app/server/remote/query.js:201 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) packages/kit/src/runtime/client/client.js:2484 — packages/kit/src/runtime/client/client.js:2484 · packages/kit/src/runtime/server/errors.js:21 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) packages/kit/src/runtime/client/remote-functions/query-live/index.js:13 — packages/kit/src/runtime/client/remote-functions/query-live/index.js:13 · packages/kit/src/runtime/client/remote-functions/query/index.js:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R7 · Dead Code · Dead file (~1 LoC) · ×5
  • Dead file (~1 LoC) packages/kit/src/runtime/app/env/index.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/kit/src/runtime/app/environment/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~1 LoC) packages/kit/src/runtime/app/forms/index.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~1 LoC) packages/kit/src/runtime/app/manifest/index.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~1 LoC) packages/kit/src/runtime/app/paths/index.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~1 LoC) packages/kit/src/runtime/app/state/index.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: fallback.js ↔ index.js packages/kit/src/core/postbuild/fallback.js:1 — `packages/kit/src/core/postbuild/fallback.js` and `packages/kit/src/exports/vite/preview/index.js` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `8705885a` chore: gate the server runtime behind `configure` (#17008); `c6ba86ba` chore: configure the server runtime in one place (#17000); `bf6f373d` Revert "feat: custom server entry points during development" (#16586) — run `git show` on any of them.
  • Change coupling: REDACTED ↔ index.js packages/adapter-netlify/index.d.ts:1 — `packages/adapter-netlify/index.d.ts` and `packages/adapter-netlify/index.js` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `8928077d` breaking: stop reading `netlify.toml` (#17078); `4bbd0c48` feat: split edge functions (#17045); `9e1484ff` feat(adapter-netlify)!: migrate to the modern Netlify Functions API (… — run `git show` on any of them.
  • Change coupling: REDACTED ↔ handler.js packages/adapter-node/index.d.ts:1 — `packages/adapter-node/index.d.ts` and `packages/adapter-node/src/handler.js` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `55609f15` chore: hand adapt-time values to the adapter-node server as a module …; `3b907d44` breaking: add `paths.origin`, remove `prerender.origin` (#16161); `44585828` fix: bundle entrypoints alongside app code (#16069) — run `git show` on any of them.
  • Change coupling: index.js ↔ REDACTED packages/adapter-node/index.js:1 — `packages/adapter-node/index.js` and `packages/adapter-node/src/env.js` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `55609f15` chore: hand adapt-time values to the adapter-node server as a module …; `3b907d44` breaking: add `paths.origin`, remove `prerender.origin` (#16161); `c54613f6` chore: add failing tests for adapter-node (#16104) — run `git show` on any of them.
D17 · Explicit Debt · TodoComment · ×3
  • TodoComment packages/adapter-vercel/test/apps/split/test/test.ts:17 — // TODO: test remote function works — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/adapter-vercel/test/apps/split/test/test.ts:19 — // TODO: test preloadCode works — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/adapter-vercel/test/apps/basic/test/test.ts:3 — // TODO: Add a skew protection test once prebuilt deployments support it. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D2 · Cognitive Complexity · form · ×3
  • form::create_instance::(anonymous)::handle_input (cognitive 36) packages/kit/src/runtime/client/remote-functions/form.svelte.js:488 — form::create_instance::(anonymous)::handle_input has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (23 pts), ternaries 3 (7 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • form::create_instance::fn (cognitive 20) packages/kit/src/runtime/app/server/remote/form.js:93 — form::create_instance::fn has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, error handling 1 (2 pts), ternaries 1 (2 pts), other 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • form::create_instance::(anonymous)::handle_submit (cognitive 17) packages/kit/src/runtime/client/remote-functions/form.svelte.js:402 — form::create_instance::(anonymous)::handle_submit has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 3, ternaries 3, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
P12 · CI test-gate honesty · Workspace package's tests never run by CI · ×3
  • Workspace package's tests never run by CI packages/adapter-bun/package.json:36 — `packages/adapter-bun` is a workspace package with 76 test(s) in 5 file(s) (e.g. `packages/adapter-bun/test/adapter.spec.ts`, `packages/adapter-bun/test/assets.spec.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/adapter-bun/test/apps/basic/package.json:1 — `packages/adapter-bun/test/apps/basic` is a workspace package with 12 test(s) in 2 file(s) (e.g. `packages/adapter-bun/test/apps/basic/test/browser.test.js`, `packages/adapter-bun/test/apps/basic/test/server.test.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/adapter-vercel/package.json:40 — `packages/adapter-vercel` is a workspace package with 27 test(s) in 1 file(s) (e.g. `packages/adapter-vercel/utils.spec.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
R10 · Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) · ×3
  • Duplicated block with local edits (11 matched lines × 2 locations) packages/enhanced-img/src/vite-plugin.js:364 — packages/enhanced-img/src/vite-plugin.js:364 · packages/enhanced-img/src/vite-plugin.js:406 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (11 matched lines × 2 locations) packages/kit/src/exports/vite/static_analysis/index.js:106 — packages/kit/src/exports/vite/static_analysis/index.js:106 · packages/kit/src/exports/vite/static_analysis/index.js:175 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (11 matched lines × 2 locations) packages/kit/src/messages/internal/build.js:22 — packages/kit/src/messages/internal/build.js:22 · packages/kit/src/messages/internal/shared.js:28 — the two spans are one implementation copied and then locally edited — 57 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R4 · Test Coverage · This test file cannot be loaded · ×3
  • This test file cannot be loaded packages/kit/src/core/postbuild/crawl.spec.js:6 — packages/kit/src/core/postbuild/crawl.spec.js:6 imports './fixtures', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/kit/test/apps/basics/src/routes/cookies/enhanced/basic/+page.server.ts:1 — packages/kit/test/apps/basics/src/routes/cookies/enhanced/basic/+page.server.ts:1 imports './$types', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/kit/test/apps/writes/test/test.js:159 — packages/kit/test/apps/writes/test/test.js:159 imports '../src/hooks.server.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
D1 · Cyclomatic Complexity · respond.internal_respond · ×2
  • respond.internal_respond::resolve (cyclomatic 48) packages/kit/src/runtime/server/respond.js:593 — respond.internal_respond::resolve has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (respond.internal_respond, respond.internal_respond::handle) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • respond.internal_respond::handle (cyclomatic 16) packages/kit/src/runtime/server/respond.js:473 — respond.internal_respond::handle has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (respond.internal_respond, respond.internal_respond::resolve) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · form · ×2
  • form::create_instance::(anonymous)::handle_submit (cyclomatic 16) packages/kit/src/runtime/client/remote-functions/form.svelte.js:402 — form::create_instance::(anonymous)::handle_submit has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • form::create_instance::(anonymous)::handle_input (cyclomatic 16) packages/kit/src/runtime/client/remote-functions/form.svelte.js:488 — form::create_instance::(anonymous)::handle_input has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D2 · Cognitive Complexity · respond.internal_respond · ×2
  • respond.internal_respond::resolve (cognitive 78) packages/kit/src/runtime/server/respond.js:593 — respond.internal_respond::resolve has cognitive complexity 78 (threshold 15). Drivers by points: if/else 27 (55 pts), boolean chains 17, ternaries 1 (5 pts), error handling 1 (nesting depth added 32). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 2 other methods here (respond.internal_respond, respond.internal_respond::handle) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • respond.internal_respond::handle (cognitive 23) packages/kit/src/runtime/server/respond.js:473 — respond.internal_respond::handle has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (6 pts), boolean chains 4 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (respond.internal_respond, respond.internal_respond::resolve) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · prerender (cognitive 20) · ×2
  • prerender (cognitive 20) packages/kit/src/runtime/app/server/remote/prerender.js:62 — prerender has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (3 pts), ternaries 3, other 2, boolean chains 1 (nesting depth added 5). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 93, wrapper, a function literal at line 82, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • prerender (cognitive 20) packages/kit/src/runtime/client/remote-functions/prerender.svelte.js:58 — prerender has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 11). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 66, 59). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: client/client.js packages/kit/src/runtime/client/client.js — FileTooLong — 1877 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 1377 over it, 3.75× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: server/respond.js packages/kit/src/runtime/server/respond.js — FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: internal_respond (93-806). The bar is 500 significant lines; this is 16 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×2
  • Duplicated block (20 lines × 2 locations) packages/adapter-auto/index.js:53 — packages/adapter-auto/index.js:53 · packages/kit/src/utils/import.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (20 lines × 2 locations) packages/kit/src/runtime/client/remote-functions/command.svelte.js:79 — packages/kit/src/runtime/client/remote-functions/command.svelte.js:79 · packages/kit/src/runtime/client/remote-functions/form.svelte.js:302 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (12 matched lines × 2 locations) packages/kit/src/runtime/app/forms/client.js:114 — packages/kit/src/runtime/app/forms/client.js:114 · packages/kit/src/runtime/client/remote-functions/form.svelte.js:404 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (12 matched lines × 2 locations) packages/kit/src/runtime/app/server/remote/requested.js:164 — packages/kit/src/runtime/app/server/remote/requested.js:164 · packages/kit/src/runtime/app/server/remote/requested.js:186 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (9 matched lines × 2 locations) packages/kit/src/runtime/client/remote-functions/prerender.svelte.js:157 — packages/kit/src/runtime/client/remote-functions/prerender.svelte.js:157 · packages/kit/src/runtime/client/remote-functions/query/instance.svelte.js:130 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (9 matched lines × 2 locations) packages/kit/src/runtime/server/remote-functions.js:420 — packages/kit/src/runtime/server/remote-functions.js:420 · packages/kit/src/runtime/server/remote-functions.js:472 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R7 · Dead Code · Dead file (~8 LoC) · ×2
  • Dead file (~8 LoC) packages/kit/src/runtime/env/dynamic/private.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~8 LoC) packages/kit/src/runtime/env/dynamic/public.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~6 LoC) · ×2
  • Dead file (~6 LoC) packages/kit/scripts/cp.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~6 LoC) packages/kit/src/runtime/client/remote-functions/index.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×2
  • Swallowed exception (caught, then discarded) packages/kit/src/runtime/client/client.js:837 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
  • Swallowed exception (caught, then discarded) packages/kit/src/runtime/client/client.js:1614 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark packages/kit/src/core/config/default-error.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D1 · Cyclomatic Complexity · render_response (cyclomatic 105) · ×1
  • render_response (cyclomatic 105) packages/kit/src/runtime/server/page/render.js:55 — render_response has cyclomatic complexity 105 (threshold 15). Of this number, 96 points are the body's own statements and 9 belong to 11 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · form.svelte.form (cyclomatic 84) · ×1
  • form.svelte.form (cyclomatic 84) packages/kit/src/runtime/client/remote-functions/form.svelte.js:70 — form.svelte.form has cyclomatic complexity 84 (threshold 15). Most of this is not in the body itself: 1 of the 84 points is its own statement and the rest belongs to 23 function items inside it that branch (a function literal at line 488, a function literal at line 402, a function literal at line 228, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · _start_router (cyclomatic 76) · ×1
  • _start_router (cyclomatic 76) packages/kit/src/runtime/client/client.js:3093 — _start_router has cyclomatic complexity 76 (threshold 15). Most of this is not in the body itself: 4 of the 76 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 3142, a function literal at line 3311, a function literal at line 3265, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · respond.internal_respond (cyclomatic 72) · ×1
  • respond.internal_respond (cyclomatic 72) packages/kit/src/runtime/server/respond.js:93 — respond.internal_respond has cyclomatic complexity 72 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (respond.internal_respond::handle, respond.internal_respond::resolve) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · tweak_types (cyclomatic 69) · ×1
  • tweak_types (cyclomatic 69) packages/kit/src/core/sync/write_types/index.js:663 — tweak_types has cyclomatic complexity 69 (threshold 15). Most of this is not in the body itself: 5 of the 69 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 815, replace_jsdoc_type_tags, a function literal at line 691, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · dev (cyclomatic 65) · ×1
  • dev (cyclomatic 65) packages/kit/src/exports/vite/dev/index.js:42 — dev has cyclomatic complexity 65 (threshold 15). Most of this is not in the body itself: 3 of the 65 points are its own statements and the rest belongs to 27 function items inside it that branch (a function literal at line 311, a function literal at line 164, a function literal at line 200, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · create_field_method (cyclomatic 62) · ×1
  • create_field_method (cyclomatic 62) packages/kit/src/runtime/form-utils.js:751 — create_field_method has cyclomatic complexity 62 (threshold 15). Most of this is not in the body itself: 8 of the 62 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 806, a function literal at line 776, (anonymous)::files, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · crawl (cyclomatic 61) · ×1
  • crawl (cyclomatic 61) packages/kit/src/core/postbuild/crawl.js:34 — crawl has cyclomatic complexity 61 (threshold 15). Of this number, 60 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · navigate (cyclomatic 49) · ×1
  • navigate (cyclomatic 49) packages/kit/src/runtime/client/client.js:1940 — navigate has cyclomatic complexity 49 (threshold 15). Of this number, 48 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · render_page (cyclomatic 49) · ×1
  • render_page (cyclomatic 49) packages/kit/src/runtime/server/page/index.js:42 — render_page has cyclomatic complexity 49 (threshold 15). Of this number, 39 points are the body's own statements and 10 belong to 8 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · load_route (cyclomatic 47) · ×1
  • load_route (cyclomatic 47) packages/kit/src/runtime/client/client.js:1373 — load_route has cyclomatic complexity 47 (threshold 15). Of this number, 27 points are the body's own statements and 20 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.statically_analyse_page_options (cyclomatic 45) · ×1
  • index.statically_analyse_page_options (cyclomatic 45) packages/kit/src/exports/vite/static_analysis/index.js:32 — index.statically_analyse_page_options has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · create_fetch · ×1
  • create_fetch::server_fetch::fetch (cyclomatic 41) packages/kit/src/runtime/server/fetch.js:34 — create_fetch::server_fetch::fetch has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.create_routes_and_nodes · ×1
  • index.create_routes_and_nodes::walk (cyclomatic 40) packages/kit/src/core/sync/create_manifest_data/index.js:139 — index.create_routes_and_nodes::walk has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (index.create_routes_and_nodes) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · index.create_routes_and_nodes (cyclomatic 40) · ×1
  • index.create_routes_and_nodes (cyclomatic 40) packages/kit/src/core/sync/create_manifest_data/index.js:120 — index.create_routes_and_nodes has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (index.create_routes_and_nodes::walk) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · fetch.create_fetch (cyclomatic 40) · ×1
  • fetch.create_fetch (cyclomatic 40) packages/kit/src/runtime/server/fetch.js:18 — fetch.create_fetch has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 34, server_fetch). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · load_server_data (cyclomatic 39) · ×1
  • load_server_data (cyclomatic 39) packages/kit/src/runtime/server/page/load_data.js:22 — load_server_data has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 8 of the 39 points are its own statements and the rest belongs to 10 function items inside it that branch (fn::(anonymous)::depends, fn::(anonymous)::get, fn::(anonymous)::get, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · generate_app_types (cyclomatic 39) · ×1
  • generate_app_types (cyclomatic 39) packages/kit/src/core/sync/write_app_types.js:107 — generate_app_types has cyclomatic complexity 39 (threshold 15). Of this number, 26 points are the body's own statements and 13 belong to 13 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · prerender.prerender (cyclomatic 38) · ×1
  • prerender.prerender (cyclomatic 38) packages/kit/src/core/postbuild/prerender.js:47 — prerender.prerender has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (prerender.prerender::save) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · sort_routes (cyclomatic 38) · ×1
  • sort_routes (cyclomatic 38) packages/kit/src/core/sync/create_manifest_data/sort.js:18 — sort_routes has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 66, split, get_parts). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · utils.should_ignore (cyclomatic 35) · ×1
  • utils.should_ignore (cyclomatic 35) packages/kit/src/exports/vite/static_analysis/utils.js:24 — utils.should_ignore has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · deserialize_binary_form (cyclomatic 35) · ×1
  • deserialize_binary_form (cyclomatic 35) packages/kit/src/runtime/form-utils.js:207 — deserialize_binary_form has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 14 of the 35 points are its own statements and the rest belongs to 9 function items inside it that branch (File, get_buffer, get_chunk, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · plugin.adapt (cyclomatic 35) · ×1
  • plugin.adapt (cyclomatic 35) packages/adapter-vercel/index.js:21 — plugin.adapt has cyclomatic complexity 35 (threshold 15). Of this number, 31 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.plugin.adapt (cyclomatic 34) · ×1
  • index.plugin.adapt (cyclomatic 34) packages/adapter-vercel/index.js:21 — index.plugin.adapt has cyclomatic complexity 34 (threshold 15). Of this number, 30 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · enhance.handle_submit (cyclomatic 33) · ×1
  • enhance.handle_submit (cyclomatic 33) packages/kit/src/runtime/app/forms/client.js:113 — enhance.handle_submit has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · preview (cyclomatic 33) · ×1
  • preview (cyclomatic 33) packages/kit/src/exports/vite/preview/index.js:21 — preview has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 7 of the 33 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 133, a function literal at line 97, a function literal at line 205, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · write_client_manifest (cyclomatic 33) · ×1
  • write_client_manifest (cyclomatic 33) packages/kit/src/core/sync/write_client_manifest.js:15 — write_client_manifest has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 15 of the 33 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 62, a function literal at line 88, generate_node, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.update_types (cyclomatic 32) · ×1
  • index.update_types (cyclomatic 32) packages/kit/src/core/sync/write_types/index.js:215 — index.update_types has cyclomatic complexity 32 (threshold 15). Of this number, 22 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · client.enhance.handle_submit (cyclomatic 32) · ×1
  • client.enhance.handle_submit (cyclomatic 32) packages/kit/src/runtime/app/forms/client.js:113 — client.enhance.handle_submit has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · client.setup_preload (cyclomatic 30) · ×1
  • client.setup_preload (cyclomatic 30) packages/kit/src/runtime/client/client.js:2337 — client.setup_preload has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 6 function items inside it that branch (preload, after_navigate, a function literal at line 2361, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · get_navigation_result_from_branch (cyclomatic 28) · ×1
  • get_navigation_result_from_branch (cyclomatic 28) packages/kit/src/runtime/client/client.js:965 — get_navigation_result_from_branch has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · form (cyclomatic 28) · ×1
  • form (cyclomatic 28) packages/kit/src/runtime/app/server/remote/form.js:66 — form has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to 22 function items inside it that branch (create_instance::fn, create_instance::get, create_instance::get::set, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · analyse (cyclomatic 28) · ×1
  • analyse (cyclomatic 28) packages/kit/src/core/postbuild/analyse.js:31 — analyse has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.kit (cyclomatic 27) · ×1
  • index.kit (cyclomatic 27) packages/kit/src/exports/vite/index.js:230 — index.kit has cyclomatic complexity 27 (threshold 15). Of this number, 25 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · load_node (cyclomatic 27) · ×1
  • load_node (cyclomatic 27) packages/kit/src/runtime/client/client.js:1109 — load_node has cyclomatic complexity 27 (threshold 15). Of this number, 15 points are the body's own statements and 12 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · static.serve_static.<returned closure> (cyclomatic 26) · ×1
  • static.serve_static.<returned closure> (cyclomatic 26) packages/adapter-node/src/static.js:172 — static.serve_static.<returned closure> has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · write_all_types (cyclomatic 26) · ×1
  • write_all_types (cyclomatic 26) packages/kit/src/core/sync/write_types/index.js:58 — write_all_types has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to 7 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · prerender · ×1
  • prerender::visit (cyclomatic 26) packages/kit/src/core/postbuild/prerender.js:376 — prerender::visit has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · get_cookies (cyclomatic 26) · ×1
  • get_cookies (cyclomatic 26) packages/kit/src/runtime/server/cookie.js:42 — get_cookies has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 8 function items inside it that branch (get, getAll, serialize, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · serve_static (cyclomatic 26) · ×1
  • serve_static (cyclomatic 26) packages/adapter-node/src/static.js:171 — serve_static has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 172, 258). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.preview.<returned closure> (cyclomatic 25) · ×1
  • index.preview.<returned closure> (cyclomatic 25) packages/kit/src/exports/vite/preview/index.js:69 — index.preview.<returned closure> has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 133, 97, 87, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · guard.plugin_guard (cyclomatic 25) · ×1
  • guard.plugin_guard (cyclomatic 25) packages/kit/src/exports/vite/plugins/guard.js:29 — guard.plugin_guard has cyclomatic complexity 25 (threshold 15). Of this number, 20 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · load_data.create_universal_fetch · ×1
  • load_data.create_universal_fetch::universal_fetch (cyclomatic 25) packages/kit/src/runtime/server/page/load_data.js:283 — load_data.create_universal_fetch::universal_fetch has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · setResponse (cyclomatic 25) · ×1
  • setResponse (cyclomatic 25) packages/kit/src/exports/node/index.js:209 — setResponse has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to 9 function items inside it that branch (probe, next, cancel, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · remote.plugin_remote (cyclomatic 23) · ×1
  • remote.plugin_remote (cyclomatic 23) REDACTED:30 — remote.plugin_remote has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · validate._create_validator.validate (cyclomatic 23) · ×1
  • validate._create_validator.validate (cyclomatic 23) REDACTED:145 — validate._create_validator.validate has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · (anonymous).adapt (cyclomatic 23) · ×1
  • (anonymous).adapt (cyclomatic 23) packages/adapter-cloudflare/index.js:29 — (anonymous).adapt has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _create_validator.validate (cyclomatic 23) · ×1
  • _create_validator.validate (cyclomatic 23) REDACTED:145 — _create_validator.validate has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 6 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · render_endpoint (cyclomatic 23) · ×1
  • render_endpoint (cyclomatic 23) packages/kit/src/runtime/server/endpoint.js:14 — render_endpoint has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · index.default.adapt (cyclomatic 22) · ×1
  • index.default.adapt (cyclomatic 22) packages/adapter-cloudflare/index.js:29 — index.default.adapt has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.process_node (cyclomatic 22) · ×1
  • index.process_node (cyclomatic 22) packages/kit/src/core/sync/write_types/index.js:412 — index.process_node has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · plugin_remote · ×1
  • plugin_remote::handler (cyclomatic 22) REDACTED:109 — plugin_remote::handler has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · vite-plugin.image_plugin · ×1
  • vite-plugin.image_plugin::update_element (cyclomatic 21) packages/enhanced-img/src/vite-plugin.js:85 — vite-plugin.image_plugin::update_element has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · prerender.prerender · ×1
  • prerender.prerender::save (cyclomatic 21) packages/kit/src/core/postbuild/prerender.js:542 — prerender.prerender::save has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (prerender.prerender) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · _start (cyclomatic 21) · ×1
  • _start (cyclomatic 21) packages/kit/src/runtime/client/client.js:461 — _start has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · create_function_bundle (cyclomatic 21) · ×1
  • create_function_bundle (cyclomatic 21) packages/adapter-vercel/index.js:535 — create_function_bundle has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · image_plugin · ×1
  • image_plugin::handler::update_element (cyclomatic 21) packages/enhanced-img/src/vite-plugin.js:85 — image_plugin::handler::update_element has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · create.is_safe (cyclomatic 21) · ×1
  • create.is_safe (cyclomatic 21) .eslint/require-path-to-file-url.js:26 — create.is_safe has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · routing.exec (cyclomatic 20) · ×1
  • routing.exec (cyclomatic 20) REDACTED:190 — routing.exec has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.dev.<returned closure> (cyclomatic 20) · ×1
  • index.dev.<returned closure> (cyclomatic 20) packages/kit/src/exports/vite/dev/index.js:301 — index.dev.<returned closure> has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 311, 431, 436). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · remote-functions.handle_remote_call_internal (cyclomatic 20) · ×1
  • remote-functions.handle_remote_call_internal (cyclomatic 20) packages/kit/src/runtime/server/remote-functions.js:198 — remote-functions.handle_remote_call_internal has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · generate_manifest (cyclomatic 20) · ×1
  • generate_manifest (cyclomatic 20) packages/kit/src/exports/vite/dev/generate_manifest.js:25 — generate_manifest has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 12 function items inside it that branch ((anonymous)::(anonymous)::inline_styles, a function literal at line 83, a function literal at line 178, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · vite-plugin.serialize_img_attributes (cyclomatic 19) · ×1
  • vite-plugin.serialize_img_attributes (cyclomatic 19) packages/enhanced-img/src/vite-plugin.js:293 — vite-plugin.serialize_img_attributes has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · create_env_modules (cyclomatic 19) · ×1
  • create_env_modules (cyclomatic 19) REDACTED:152 — create_env_modules has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · watch (cyclomatic 19) · ×1
  • watch (cyclomatic 19) packages/package/src/index.js:81 — watch has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 124, a function literal at line 110, a function literal at line 108, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · get_routes_json (cyclomatic 19) · ×1
  • get_routes_json (cyclomatic 19) REDACTED:136 — get_routes_json has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · generate_manifest (cyclomatic 19) · ×1
  • generate_manifest (cyclomatic 19) packages/kit/src/core/generate_manifest/index.js:26 — generate_manifest has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 9 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · find_server_assets.find_server_assets (cyclomatic 18) · ×1
  • find_server_assets.find_server_assets (cyclomatic 18) packages/kit/src/core/generate_manifest/find_server_assets.js:11 — find_server_assets.find_server_assets has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BaseProvider.constructor (cyclomatic 18) · ×1
  • BaseProvider.constructor (cyclomatic 18) packages/kit/src/runtime/server/page/csp.js:95 — BaseProvider.constructor has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · update_state (cyclomatic 18) · ×1
  • update_state (cyclomatic 18) packages/kit/src/runtime/client/client.js:2898 — update_state has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · collect_remote_data (cyclomatic 18) · ×1
  • collect_remote_data (cyclomatic 18) packages/kit/src/runtime/server/remote-functions.js:391 — collect_remote_data has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 8 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · requested (cyclomatic 18) · ×1
  • requested (cyclomatic 18) packages/kit/src/runtime/app/server/remote/requested.js:104 — requested has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 163, refreshAll, reconnectAll, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · get_router_options (cyclomatic 18) · ×1
  • get_router_options (cyclomatic 18) packages/kit/src/runtime/client/utils.js:158 — get_router_options has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · env.load_explicit_env (cyclomatic 17) · ×1
  • env.load_explicit_env (cyclomatic 17) REDACTED:38 — env.load_explicit_env has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · shared.create_remote_arg_revivers (cyclomatic 17) · ×1
  • shared.create_remote_arg_revivers (cyclomatic 17) packages/kit/src/runtime/shared.js:184 — shared.create_remote_arg_revivers has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 229, 189, 212). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.get_raw_body (cyclomatic 17) · ×1
  • index.get_raw_body (cyclomatic 17) packages/kit/src/exports/node/index.js:13 — index.get_raw_body has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · _invalidate (cyclomatic 17) · ×1
  • _invalidate (cyclomatic 17) packages/kit/src/runtime/client/client.js:573 — _invalidate has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · kit · ×1
  • kit::handler (cyclomatic 17) packages/kit/src/exports/vite/index.js:319 — kit::handler has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · create_live_query_response (cyclomatic 17) · ×1
  • create_live_query_response (cyclomatic 17) packages/kit/src/runtime/server/remote-functions.js:35 — create_live_query_response has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 9 function items inside it that branch (pull, a function literal at line 57, teardown, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · normalize_options (cyclomatic 17) · ×1
  • normalize_options (cyclomatic 17) packages/package/src/index.js:211 — normalize_options has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · plugin_guard · ×1
  • plugin_guard::handler (cyclomatic 17) packages/kit/src/exports/vite/plugins/guard.js:114 — plugin_guard::handler has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · prerender (cyclomatic 17) · ×1
  • prerender (cyclomatic 17) packages/kit/src/runtime/app/server/remote/prerender.js:62 — prerender has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 93, wrapper, a function literal at line 82, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · (anonymous).adapt (cyclomatic 17) · ×1
  • (anonymous).adapt (cyclomatic 17) packages/adapter-static/index.js:9 — (anonymous).adapt has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · serialize_data (cyclomatic 17) · ×1
  • serialize_data (cyclomatic 17) packages/kit/src/runtime/server/page/serialize_data.js:43 — serialize_data has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · css.tippex_comments_and_strings (cyclomatic 16) · ×1
  • css.tippex_comments_and_strings (cyclomatic 16) packages/kit/src/utils/css.js:149 — css.tippex_comments_and_strings has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · load_root_error_page (cyclomatic 16) · ×1
  • load_root_error_page (cyclomatic 16) packages/kit/src/runtime/client/client.js:1657 — load_root_error_page has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · setup_preload · ×1
  • setup_preload::preload (cyclomatic 16) packages/kit/src/runtime/client/client.js:2418 — setup_preload::preload has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · goto (cyclomatic 16) · ×1
  • goto (cyclomatic 16) packages/kit/src/runtime/client/client.js:2629 — goto has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _hydrate (cyclomatic 16) · ×1
  • _hydrate (cyclomatic 16) packages/kit/src/runtime/client/client.js:3490 — _hydrate has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · #main (cyclomatic 16) · ×1
  • #main (cyclomatic 16) packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:120 — #main has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · (anonymous).adapt (cyclomatic 16) · ×1
  • (anonymous).adapt (cyclomatic 16) packages/adapter-bun/index.js:85 — (anonymous).adapt has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · remote_request (cyclomatic 16) · ×1
  • remote_request (cyclomatic 16) packages/kit/src/runtime/client/remote-functions/shared.svelte.js:115 — remote_request has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · reset_focus (cyclomatic 16) · ×1
  • reset_focus (cyclomatic 16) packages/kit/src/runtime/client/focus.js:40 — reset_focus has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D2 · Cognitive Complexity · crawl (cognitive 227) · ×1
  • crawl (cognitive 227) packages/kit/src/core/postbuild/crawl.js:34 — crawl has cognitive complexity 227 (threshold 15). Drivers by points: if/else 31 (133 pts), loops 14 (74 pts), boolean chains 12, error handling 2 (7 pts), other 1 (nesting depth added 167). Of this number, 226 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · render_response (cognitive 189) · ×1
  • render_response (cognitive 189) packages/kit/src/runtime/server/page/render.js:55 — render_response has cognitive complexity 189 (threshold 15). Drivers by points: if/else 65 (127 pts), ternaries 13 (26 pts), boolean chains 18, loops 8 (14 pts), other 4 (nesting depth added 81). Of this number, 173 points are the body's own statements and 16 belong to 11 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.statically_analyse_page_options (cognitive 120) · ×1
  • index.statically_analyse_page_options (cognitive 120) packages/kit/src/exports/vite/static_analysis/index.js:32 — index.statically_analyse_page_options has cognitive complexity 120 (threshold 15). Drivers by points: if/else 26 (86 pts), loops 6 (19 pts), boolean chains 5, ternaries 1 (5 pts), match/switch 1 (4 pts), error handling 1 (nesting depth added 80). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · respond.internal_respond (cognitive 110) · ×1
  • respond.internal_respond (cognitive 110) packages/kit/src/runtime/server/respond.js:93 — respond.internal_respond has cognitive complexity 110 (threshold 15). Drivers by points: if/else 83 (155 pts), boolean chains 41, ternaries 4 (13 pts), error handling 7 (12 pts), loops 5 (9 pts) (nesting depth added 90). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (respond.internal_respond::handle, respond.internal_respond::resolve) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · create_field_method (cognitive 110) · ×1
  • create_field_method (cognitive 110) packages/kit/src/runtime/form-utils.js:751 — create_field_method has cognitive complexity 110 (threshold 15). Drivers by points: if/else 22 (57 pts), ternaries 12 (31 pts), boolean chains 13, loops 2 (5 pts), other 3, match/switch 1 (nesting depth added 57). Most of this is not in the body itself: 1 of the 110 points is its own statement and the rest belongs to 13 function items inside it that branch (a function literal at line 806, a function literal at line 776, (anonymous)::files, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · sort_routes (cognitive 104) · ×1
  • sort_routes (cognitive 104) packages/kit/src/core/sync/create_manifest_data/sort.js:18 — sort_routes has cognitive complexity 104 (threshold 15). Drivers by points: if/else 19 (70 pts), ternaries 7 (22 pts), boolean chains 6, loops 3 (4 pts), other 2 (nesting depth added 67). None of this is in the body itself: all 104 points belong to 3 function items inside it that branch (a function literal at line 66, split, get_parts). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · _start_router (cognitive 100) · ×1
  • _start_router (cognitive 100) packages/kit/src/runtime/client/client.js:3093 — _start_router has cognitive complexity 100 (threshold 15). Drivers by points: if/else 42 (62 pts), boolean chains 19, ternaries 7 (13 pts), other 5, loops 1 (nesting depth added 26). Most of this is not in the body itself: 4 of the 100 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 3142, a function literal at line 3311, a function literal at line 3265, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · generate_app_types (cognitive 79) · ×1
  • generate_app_types (cognitive 79) packages/kit/src/core/sync/write_app_types.js:107 — generate_app_types has cognitive complexity 79 (threshold 15). Drivers by points: if/else 18 (41 pts), ternaries 6 (18 pts), loops 7 (13 pts), boolean chains 5, other 2 (nesting depth added 41). Of this number, 56 points are the body's own statements and 23 belong to 13 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.create_routes_and_nodes · ×1
  • index.create_routes_and_nodes::walk (cognitive 76) packages/kit/src/core/sync/create_manifest_data/index.js:139 — index.create_routes_and_nodes::walk has cognitive complexity 76 (threshold 15). Drivers by points: if/else 34 (68 pts), boolean chains 3, ternaries 1 (3 pts), loops 2 (nesting depth added 36). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (index.create_routes_and_nodes) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · index.create_routes_and_nodes (cognitive 76) · ×1
  • index.create_routes_and_nodes (cognitive 76) packages/kit/src/core/sync/create_manifest_data/index.js:120 — index.create_routes_and_nodes has cognitive complexity 76 (threshold 15). Drivers by points: if/else 63 (156 pts), ternaries 6 (21 pts), loops 10 (14 pts), boolean chains 10 (nesting depth added 112). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (index.create_routes_and_nodes::walk) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · render_page (cognitive 76) · ×1
  • render_page (cognitive 76) packages/kit/src/runtime/server/page/index.js:42 — render_page has cognitive complexity 76 (threshold 15). Drivers by points: if/else 27 (46 pts), loops 7 (12 pts), error handling 6 (10 pts), boolean chains 6, ternaries 2 (nesting depth added 28). Of this number, 65 points are the body's own statements and 11 belong to 8 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · navigate (cognitive 75) · ×1
  • navigate (cognitive 75) packages/kit/src/runtime/client/client.js:1940 — navigate has cognitive complexity 75 (threshold 15). Drivers by points: if/else 32 (47 pts), ternaries 6 (10 pts), boolean chains 9, loops 2 (6 pts), other 3 (nesting depth added 23). Of this number, 72 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · load_route (cognitive 74) · ×1
  • load_route (cognitive 74) packages/kit/src/runtime/client/client.js:1373 — load_route has cognitive complexity 74 (threshold 15). Drivers by points: if/else 19 (41 pts), boolean chains 13, error handling 5 (10 pts), ternaries 5, loops 3, other 2 (nesting depth added 27). Of this number, 53 points are the body's own statements and 21 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · dev (cognitive 72) · ×1
  • dev (cognitive 72) packages/kit/src/exports/vite/dev/index.js:42 — dev has cognitive complexity 72 (threshold 15). Drivers by points: if/else 34 (43 pts), boolean chains 17, other 6, ternaries 4, error handling 2 (nesting depth added 9). Most of this is not in the body itself: 2 of the 72 points are its own statements and the rest belongs to 27 function items inside it that branch (a function literal at line 311, a function literal at line 164, a function literal at line 272, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · prerender.prerender (cognitive 66) · ×1
  • prerender.prerender (cognitive 66) packages/kit/src/core/postbuild/prerender.js:47 — prerender.prerender has cognitive complexity 66 (threshold 15). Drivers by points: if/else 59 (113 pts), loops 17 (26 pts), boolean chains 14, ternaries 7 (14 pts), error handling 2 (4 pts), match/switch 1 (nesting depth added 72). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (prerender.prerender::save) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · plugin.adapt (cognitive 65) · ×1
  • plugin.adapt (cognitive 65) packages/adapter-vercel/index.js:21 — plugin.adapt has cognitive complexity 65 (threshold 15). Drivers by points: if/else 22 (41 pts), ternaries 6 (14 pts), loops 6 (8 pts), boolean chains 1, other 1 (nesting depth added 29). Of this number, 61 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.plugin.adapt (cognitive 64) · ×1
  • index.plugin.adapt (cognitive 64) packages/adapter-vercel/index.js:21 — index.plugin.adapt has cognitive complexity 64 (threshold 15). Drivers by points: if/else 22 (41 pts), ternaries 6 (14 pts), loops 6 (8 pts), boolean chains 1 (nesting depth added 29). Of this number, 60 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · form.svelte.form (cognitive 61) · ×1
  • form.svelte.form (cognitive 61) packages/kit/src/runtime/client/remote-functions/form.svelte.js:70 — form.svelte.form has cognitive complexity 61 (threshold 15). Drivers by points: if/else 36 (45 pts), boolean chains 12, error handling 2, ternaries 1 (2 pts) (nesting depth added 10). None of this is in the body itself: all 61 points belong to 23 function items inside it that branch (a function literal at line 228, a function literal at line 691, create_instance, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.update_types (cognitive 54) · ×1
  • index.update_types (cognitive 54) packages/kit/src/core/sync/write_types/index.js:215 — index.update_types has cognitive complexity 54 (threshold 15). Drivers by points: if/else 21 (41 pts), boolean chains 7, loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 23). Of this number, 33 points are the body's own statements and 21 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · plugin_remote · ×1
  • plugin_remote::handler (cognitive 53) REDACTED:109 — plugin_remote::handler has cognitive complexity 53 (threshold 15). Drivers by points: if/else 16 (40 pts), loops 4 (11 pts), ternaries 1 (2 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remote.plugin_remote (cognitive 52) · ×1
  • remote.plugin_remote (cognitive 52) REDACTED:30 — remote.plugin_remote has cognitive complexity 52 (threshold 15). Drivers by points: if/else 17 (41 pts), loops 4 (11 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create_fetch · ×1
  • create_fetch::server_fetch::fetch (cognitive 51) packages/kit/src/runtime/server/fetch.js:34 — create_fetch::server_fetch::fetch has cognitive complexity 51 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 13, ternaries 6 (13 pts), other 3, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · collect_remote_data (cognitive 48) · ×1
  • collect_remote_data (cognitive 48) packages/kit/src/runtime/server/remote-functions.js:391 — collect_remote_data has cognitive complexity 48 (threshold 15). Drivers by points: if/else 9 (27 pts), ternaries 3 (11 pts), loops 4 (9 pts), other 1 (nesting depth added 31). Of this number, 25 points are the body's own statements and 23 belong to 8 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · prerender · ×1
  • prerender::visit (cognitive 46) packages/kit/src/core/postbuild/prerender.js:376 — prerender::visit has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (29 pts), ternaries 3 (8 pts), loops 3 (5 pts), boolean chains 3, other 1 (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · fetch.create_fetch (cognitive 45) · ×1
  • fetch.create_fetch (cognitive 45) packages/kit/src/runtime/server/fetch.js:18 — fetch.create_fetch has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 14, ternaries 4 (9 pts), loops 1 (nesting depth added 11). None of this is in the body itself: all 45 points belong to 2 function items inside it that branch (a function literal at line 34, server_fetch). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · write_client_manifest (cognitive 45) · ×1
  • write_client_manifest (cognitive 45) packages/kit/src/core/sync/write_client_manifest.js:15 — write_client_manifest has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16 (25 pts), ternaries 10 (12 pts), loops 2 (4 pts), boolean chains 2, other 2 (nesting depth added 13). Of this number, 16 points are the body's own statements and 29 belong to 8 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · load_node (cognitive 44) · ×1
  • load_node (cognitive 44) packages/kit/src/runtime/client/client.js:1109 — load_node has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (27 pts), ternaries 3 (7 pts), other 5, boolean chains 3, loops 1 (2 pts) (nesting depth added 18). Of this number, 18 points are the body's own statements and 26 belong to 10 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · write_all_types (cognitive 42) · ×1
  • write_all_types (cognitive 42) packages/kit/src/core/sync/write_types/index.js:58 — write_all_types has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 5 (8 pts), boolean chains 2, error handling 1 (2 pts), other 2, ternaries 1 (nesting depth added 19). Of this number, 40 points are the body's own statements and 2 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · preview (cognitive 42) · ×1
  • preview (cognitive 42) packages/kit/src/exports/vite/preview/index.js:21 — preview has cognitive complexity 42 (threshold 15). Drivers by points: if/else 22 (29 pts), ternaries 4 (5 pts), boolean chains 3, error handling 2, other 2, loops 1 (nesting depth added 8). Most of this is not in the body itself: 7 of the 42 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 133, a function literal at line 97, a function literal at line 69, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · normalize_options (cognitive 41) · ×1
  • normalize_options (cognitive 41) packages/package/src/index.js:211 — normalize_options has cognitive complexity 41 (threshold 15). Drivers by points: if/else 6 (21 pts), ternaries 2 (7 pts), loops 2 (6 pts), other 3, boolean chains 2, error handling 1 (2 pts) (nesting depth added 25). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · analyse (cognitive 41) · ×1
  • analyse (cognitive 41) packages/kit/src/core/postbuild/analyse.js:31 — analyse has cognitive complexity 41 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 6 (11 pts), boolean chains 7, other 6, ternaries 1 (2 pts) (nesting depth added 15). Of this number, 39 points are the body's own statements and 2 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.process_node (cognitive 40) · ×1
  • index.process_node (cognitive 40) packages/kit/src/core/sync/write_types/index.js:412 — index.process_node has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 8 (17 pts), boolean chains 4 (nesting depth added 15). Of this number, 29 points are the body's own statements and 11 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · enhance.handle_submit (cognitive 40) · ×1
  • enhance.handle_submit (cognitive 40) packages/kit/src/runtime/app/forms/client.js:113 — enhance.handle_submit has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 8 (11 pts), boolean chains 7, error handling 2, loops 1 (2 pts), other 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · client.enhance.handle_submit (cognitive 38) · ×1
  • client.enhance.handle_submit (cognitive 38) packages/kit/src/runtime/app/forms/client.js:113 — client.enhance.handle_submit has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 7 (11 pts), boolean chains 6, error handling 2, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create_function_bundle (cognitive 37) · ×1
  • create_function_bundle (cognitive 37) packages/adapter-vercel/index.js:535 — create_function_bundle has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 6 (10 pts), error handling 2 (5 pts), ternaries 1 (3 pts), other 2 (nesting depth added 16). Of this number, 30 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · setResponse (cognitive 37) · ×1
  • setResponse (cognitive 37) packages/kit/src/exports/node/index.js:209 — setResponse has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (22 pts), ternaries 3 (6 pts), error handling 4 (5 pts), loops 3, boolean chains 1 (nesting depth added 12). Most of this is not in the body itself: 8 of the 37 points are its own statements and the rest belongs to 9 function items inside it that branch (probe, next, cancel, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · utils.should_ignore (cognitive 36) · ×1
  • utils.should_ignore (cognitive 36) packages/kit/src/exports/vite/static_analysis/utils.js:24 — utils.should_ignore has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 11, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.kit (cognitive 35) · ×1
  • index.kit (cognitive 35) packages/kit/src/exports/vite/index.js:230 — index.kit has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (19 pts), loops 5 (6 pts), boolean chains 5, error handling 1 (3 pts), ternaries 2 (nesting depth added 8). Of this number, 33 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · client.setup_preload (cognitive 35) · ×1
  • client.setup_preload (cognitive 35) packages/kit/src/runtime/client/client.js:2337 — client.setup_preload has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (25 pts), boolean chains 8, loops 2 (nesting depth added 7). None of this is in the body itself: all 35 points belong to 6 function items inside it that branch (preload, after_navigate, a function literal at line 2361, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · load_data.create_universal_fetch · ×1
  • load_data.create_universal_fetch::universal_fetch (cognitive 35) packages/kit/src/runtime/server/page/load_data.js:283 — load_data.create_universal_fetch::universal_fetch has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (20 pts), ternaries 5 (9 pts), boolean chains 6 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · get_navigation_result_from_branch (cognitive 35) · ×1
  • get_navigation_result_from_branch (cognitive 35) packages/kit/src/runtime/client/client.js:965 — get_navigation_result_from_branch has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 8, loops 3 (6 pts), other 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · load_server_data (cognitive 35) · ×1
  • load_server_data (cognitive 35) packages/kit/src/runtime/server/page/load_data.js:22 — load_server_data has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 12, loops 1, other 1, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 35 points are its own statements and the rest belongs to 10 function items inside it that branch (fn::(anonymous)::depends, fn::(anonymous)::get, fn::(anonymous)::get, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · serve_static (cognitive 35) · ×1
  • serve_static (cognitive 35) packages/adapter-node/src/static.js:171 — serve_static has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (20 pts), ternaries 3 (8 pts), boolean chains 7 (nesting depth added 10). None of this is in the body itself: all 35 points belong to 2 function literals inside it that branch (lines 172, 258). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · watch (cognitive 34) · ×1
  • watch (cognitive 34) packages/package/src/index.js:81 — watch has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (20 pts), boolean chains 5, error handling 2 (5 pts), loops 2 (4 pts) (nesting depth added 17). None of this is in the body itself: all 34 points belong to 8 function items inside it that branch (a function literal at line 124, a function literal at line 110, a function literal at line 108, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · get_routes_json (cognitive 34) · ×1
  • get_routes_json (cognitive 34) REDACTED:136 — get_routes_json has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 4 (8 pts), other 2, boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · static.serve_static.<returned closure> (cognitive 33) · ×1
  • static.serve_static.<returned closure> (cognitive 33) packages/adapter-node/src/static.js:172 — static.serve_static.<returned closure> has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 7, ternaries 2 (6 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.preview.<returned closure> (cognitive 33) · ×1
  • index.preview.<returned closure> (cognitive 33) packages/kit/src/exports/vite/preview/index.js:69 — index.preview.<returned closure> has cognitive complexity 33 (threshold 15). Drivers by points: if/else 19 (25 pts), boolean chains 3, ternaries 2 (3 pts), error handling 1, loops 1 (nesting depth added 7). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 133, 97, 87, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · (anonymous).adapt (cognitive 33) · ×1
  • (anonymous).adapt (cognitive 33) packages/adapter-cloudflare/index.js:29 — (anonymous).adapt has cognitive complexity 33 (threshold 15). Drivers by points: if/else 20 (26 pts), boolean chains 3, ternaries 1 (3 pts), other 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.default.adapt (cognitive 32) · ×1
  • index.default.adapt (cognitive 32) packages/adapter-cloudflare/index.js:29 — index.default.adapt has cognitive complexity 32 (threshold 15). Drivers by points: if/else 20 (26 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · prerender.prerender · ×1
  • prerender.prerender::save (cognitive 32) packages/kit/src/core/postbuild/prerender.js:542 — prerender.prerender::save has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 5, ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (prerender.prerender) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · deserialize_binary_form (cognitive 32) · ×1
  • deserialize_binary_form (cognitive 32) packages/kit/src/runtime/form-utils.js:207 — deserialize_binary_form has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 6, loops 5, error handling 1, other 1 (nesting depth added 4). Of this number, 17 points are the body's own statements and 15 belong to 9 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · image_plugin · ×1
  • image_plugin::handler::update_element (cognitive 32) packages/enhanced-img/src/vite-plugin.js:85 — image_plugin::handler::update_element has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 6 (12 pts), boolean chains 5 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · #main (cognitive 32) · ×1
  • #main (cognitive 32) packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:120 — #main has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 2 (3 pts), error handling 1 (2 pts), boolean chains 1, other 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · get_cookies (cognitive 32) · ×1
  • get_cookies (cognitive 32) packages/kit/src/runtime/server/cookie.js:42 — get_cookies has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 7, loops 3, other 3, ternaries 1 (2 pts) (nesting depth added 8). Most of this is not in the body itself: 2 of the 32 points are its own statements and the rest belongs to 8 function items inside it that branch (get, getAll, serialize, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · guard.plugin_guard (cognitive 31) · ×1
  • guard.plugin_guard (cognitive 31) packages/kit/src/exports/vite/plugins/guard.js:29 — guard.plugin_guard has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 4, loops 2 (nesting depth added 8). Of this number, 23 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · internal.format_response (cognitive 31) · ×1
  • internal.format_response (cognitive 31) packages/kit/src/runtime/server/internal.js:78 — internal.format_response has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 2, error handling 1 (2 pts), ternaries 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · vite-plugin.image_plugin · ×1
  • vite-plugin.image_plugin::update_element (cognitive 30) packages/enhanced-img/src/vite-plugin.js:85 — vite-plugin.image_plugin::update_element has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 5 (10 pts), boolean chains 5 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (vite-plugin.image_plugin) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · vite-plugin.serialize_img_attributes (cognitive 30) · ×1
  • vite-plugin.serialize_img_attributes (cognitive 30) packages/enhanced-img/src/vite-plugin.js:293 — vite-plugin.serialize_img_attributes has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 7, ternaries 1 (3 pts), loops 1 (nesting depth added 12). Of this number, 28 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · find_server_assets.find_server_assets (cognitive 30) · ×1
  • find_server_assets.find_server_assets (cognitive 30) packages/kit/src/core/generate_manifest/find_server_assets.js:11 — find_server_assets.find_server_assets has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 7 (14 pts) (nesting depth added 13). Of this number, 27 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validate._create_validator.validate (cognitive 30) · ×1
  • validate._create_validator.validate (cognitive 30) REDACTED:145 — validate._create_validator.validate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 11 (nesting depth added 7). Of this number, 28 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create_env_modules (cognitive 30) · ×1
  • create_env_modules (cognitive 30) REDACTED:152 — create_env_modules has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 5 (6 pts), boolean chains 3, other 3, loops 1 (nesting depth added 10). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _create_validator.validate (cognitive 29) · ×1
  • _create_validator.validate (cognitive 29) REDACTED:145 — _create_validator.validate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 10 (nesting depth added 7). Of this number, 27 points are the body's own statements and 2 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · routing.exec (cognitive 28) · ×1
  • routing.exec (cognitive 28) REDACTED:190 — routing.exec has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 4, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · form.form (cognitive 28) · ×1
  • form.form (cognitive 28) packages/kit/src/runtime/app/server/remote/form.js:66 — form.form has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (18 pts), ternaries 4, boolean chains 3, error handling 2 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 93, a function literal at line 157, a function literal at line 177, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · typescript.load_tsconfig (cognitive 28) · ×1
  • typescript.load_tsconfig (cognitive 28) packages/package/src/typescript.js:217 — typescript.load_tsconfig has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 3 (7 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · utils.matches (cognitive 27) · ×1
  • utils.matches (cognitive 27) packages/adapter-netlify/utils.js:10 — utils.matches has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 5, loops 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _start (cognitive 27) · ×1
  • _start (cognitive 27) packages/kit/src/runtime/client/client.js:461 — _start has cognitive complexity 27 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 7, ternaries 4 (6 pts), other 5, boolean chains 1 (nesting depth added 6). Of this number, 26 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · categorize_updates (cognitive 27) · ×1
  • categorize_updates (cognitive 27) packages/kit/src/runtime/client/remote-functions/shared.svelte.js:236 — categorize_updates has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 2 (6 pts), boolean chains 2, other 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.get_split_functions (cognitive 26) · ×1
  • index.get_split_functions (cognitive 26) packages/adapter-netlify/index.js:175 — index.get_split_functions has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 2 (6 pts), loops 3 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · css.fix_css_urls (cognitive 26) · ×1
  • css.fix_css_urls (cognitive 26) packages/kit/src/utils/css.js:38 — css.fix_css_urls has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 12). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 65). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · tweak_types · ×1
  • tweak_types::replace_jsdoc_type_tags (cognitive 26) packages/kit/src/core/sync/write_types/index.js:726 — tweak_types::replace_jsdoc_type_tags has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 1 (6 pts), loops 2 (5 pts), boolean chains 3, other 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · generate_manifest (cognitive 26) · ×1
  • generate_manifest (cognitive 26) packages/kit/src/exports/vite/dev/generate_manifest.js:25 — generate_manifest has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 5 (7 pts), boolean chains 3, error handling 1 (3 pts), loops 2 (nesting depth added 6). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 12 function items inside it that branch ((anonymous)::(anonymous)::inline_styles, a function literal at line 83, a function literal at line 178, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · get_router_options (cognitive 26) · ×1
  • get_router_options (cognitive 26) packages/kit/src/runtime/client/utils.js:158 — get_router_options has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (4 pts), other 3, boolean chains 2, match/switch 1 (nesting depth added 11). Of this number, 25 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous).adapt (cognitive 26) · ×1
  • (anonymous).adapt (cognitive 26) packages/adapter-static/index.js:9 — (anonymous).adapt has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 3, other 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.default.adapt (cognitive 25) · ×1
  • index.default.adapt (cognitive 25) packages/adapter-static/index.js:9 — index.default.adapt has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · routing.parse_route_id (cognitive 25) · ×1
  • routing.parse_route_id (cognitive 25) REDACTED:35 — routing.parse_route_id has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 4 (11 pts), boolean chains 3 (nesting depth added 13). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 76, 44). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · render_endpoint (cognitive 25) · ×1
  • render_endpoint (cognitive 25) packages/kit/src/runtime/server/endpoint.js:14 — render_endpoint has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 9, error handling 1, other 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · reset_focus (cognitive 25) · ×1
  • reset_focus (cognitive 25) packages/kit/src/runtime/client/focus.js:40 — reset_focus has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (6 pts), boolean chains 3, other 1 (nesting depth added 12). Of this number, 14 points are the body's own statements and 11 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _hydrate (cognitive 24) · ×1
  • _hydrate (cognitive 24) packages/kit/src/runtime/client/client.js:3490 — _hydrate has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1, other 1 (nesting depth added 7). Of this number, 22 points are the body's own statements and 2 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create_remote_arg_reducers (cognitive 24) · ×1
  • create_remote_arg_reducers (cognitive 24) packages/kit/src/runtime/shared.js:105 — create_remote_arg_reducers has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 2 (4 pts) (nesting depth added 11). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 132, a function literal at line 159, a function literal at line 120, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · generate_manifest (cognitive 24) · ×1
  • generate_manifest (cognitive 24) packages/kit/src/core/generate_manifest/index.js:26 — generate_manifest has cognitive complexity 24 (threshold 15). Drivers by points: loops 5 (9 pts), if/else 5 (7 pts), boolean chains 4, ternaries 3, other 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 6 belong to 9 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.dev.<returned closure> (cognitive 23) · ×1
  • index.dev.<returned closure> (cognitive 23) packages/kit/src/exports/vite/dev/index.js:301 — index.dev.<returned closure> has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 6, error handling 1, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 23 points belong to 3 function literals inside it that branch (lines 311, 431, 436). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · remote_request (cognitive 23) · ×1
  • remote_request (cognitive 23) packages/kit/src/runtime/client/remote-functions/shared.svelte.js:115 — remote_request has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3 (5 pts), ternaries 2 (3 pts), error handling 1 (2 pts), other 1 (nesting depth added 7). Of this number, 18 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · env.load_explicit_env (cognitive 22) · ×1
  • env.load_explicit_env (cognitive 22) REDACTED:38 — env.load_explicit_env has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 7, error handling 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remote-functions.handle_remote_call_internal (cognitive 22) · ×1
  • remote-functions.handle_remote_call_internal (cognitive 22) packages/kit/src/runtime/server/remote-functions.js:198 — remote-functions.handle_remote_call_internal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 2 (3 pts), boolean chains 1, error handling 1, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · load_root_error_page (cognitive 22) · ×1
  • load_root_error_page (cognitive 22) packages/kit/src/runtime/client/client.js:1657 — load_root_error_page has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 4, error handling 2 (4 pts), other 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create_live_query_response (cognitive 22) · ×1
  • create_live_query_response (cognitive 22) packages/kit/src/runtime/server/remote-functions.js:35 — create_live_query_response has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), error handling 2, boolean chains 1, loops 1, other 1 (nesting depth added 5). None of this is in the body itself: all 22 points belong to 9 function items inside it that branch (pull, a function literal at line 57, teardown, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · handler.render (cognitive 21) · ×1
  • handler.render (cognitive 21) packages/adapter-node/src/handler.js:70 — handler.render has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (3 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 9). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 103). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · options.object.<returned closure> (cognitive 21) · ×1
  • options.object.<returned closure> (cognitive 21) packages/kit/src/core/config/options.js:333 — options.object.<returned closure> has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, ternaries 1 (4 pts), loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BaseProvider.get_header (cognitive 21) · ×1
  • BaseProvider.get_header (cognitive 21) packages/kit/src/runtime/server/page/csp.js:218 — BaseProvider.get_header has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 6, loops 2 (4 pts), ternaries 1 (4 pts) (nesting depth added 8). Of this number, 19 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · setup_preload · ×1
  • setup_preload::preload (cognitive 21) packages/kit/src/runtime/client/client.js:2418 — setup_preload::preload has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 2 (6 pts), boolean chains 5 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · object (cognitive 21) · ×1
  • object (cognitive 21) packages/kit/src/core/config/options.js:332 — object has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, ternaries 1 (4 pts), loops 2 (nesting depth added 9). None of this is in the body itself: all 21 points belong to one function literal inside it that branches (line 333). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · query_batch (cognitive 21) · ×1
  • query_batch (cognitive 21) packages/kit/src/runtime/client/remote-functions/query-batch.svelte.js:12 — query_batch has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (13 pts), if/else 4 (6 pts), error handling 1, other 1 (nesting depth added 9). None of this is in the body itself: all 21 points belong to 4 function items inside it that branch (a function literal at line 38, a function literal at line 19, wrapper, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · prevent_conflicts (cognitive 21) · ×1
  • prevent_conflicts (cognitive 21) packages/kit/src/core/sync/create_manifest_data/conflict.js:4 — prevent_conflicts has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 10). Of this number, 16 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · filesystem.copy · ×1
  • filesystem.copy::go (cognitive 20) REDACTED:33 — filesystem.copy::go has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (6 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · query-batch.svelte.query_batch.wrapper (cognitive 20) · ×1
  • query-batch.svelte.query_batch.wrapper (cognitive 20) packages/kit/src/runtime/client/remote-functions/query-batch.svelte.js:17 — query-batch.svelte.query_batch.wrapper has cognitive complexity 20 (threshold 15). Drivers by points: loops 6 (13 pts), if/else 4 (6 pts), error handling 1 (nesting depth added 9). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 38, 19). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · _invalidate (cognitive 20) · ×1
  • _invalidate (cognitive 20) packages/kit/src/runtime/client/client.js:573 — _invalidate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (8 pts), loops 4 (6 pts), error handling 2 (4 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · preloadCode (cognitive 20) · ×1
  • preloadCode (cognitive 20) packages/kit/src/runtime/client/client.js:2803 — preloadCode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, other 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · batch (cognitive 20) · ×1
  • batch (cognitive 20) packages/kit/src/runtime/app/server/remote/query.js:245 — batch has cognitive complexity 20 (threshold 15). Drivers by points: loops 5 (11 pts), error handling 3 (4 pts), if/else 4, other 1 (nesting depth added 7). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 17 function items inside it that branch (a function literal at line 295, a function literal at line 285, a function literal at line 263, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · split_config (cognitive 20) · ×1
  • split_config (cognitive 20) packages/kit/src/core/config/index.js:23 — split_config has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (4 pts), other 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create.is_safe (cognitive 20) · ×1
  • create.is_safe (cognitive 20) .eslint/require-path-to-file-url.js:26 — create.is_safe has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 8, other 1 (nesting depth added 3). Of this number, 19 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · css.tippex_comments_and_strings (cognitive 19) · ×1
  • css.tippex_comments_and_strings (cognitive 19) packages/kit/src/utils/css.js:149 — css.tippex_comments_and_strings has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 5, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · _goto (cognitive 19) · ×1
  • _goto (cognitive 19) packages/kit/src/runtime/client/client.js:708 — _goto has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 4 (8 pts), other 1 (nesting depth added 8). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (accept, a function literal at line 760). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · update_state (cognitive 19) · ×1
  • update_state (cognitive 19) packages/kit/src/runtime/client/client.js:2898 — update_state has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 4, boolean chains 2, other 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · kit · ×1
  • kit::handler (cognitive 19) packages/kit/src/exports/vite/index.js:319 — kit::handler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5, loops 3 (4 pts), other 4, error handling 1 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous).adapt (cognitive 19) · ×1
  • (anonymous).adapt (cognitive 19) packages/adapter-bun/index.js:85 — (anonymous).adapt has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 3, loops 1 (2 pts), other 2, ternaries 2 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · routing.validate_route_id_params (cognitive 18) · ×1
  • routing.validate_route_id_params (cognitive 18) REDACTED:119 — routing.validate_route_id_params has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · constructor (cognitive 18) · ×1
  • constructor (cognitive 18) packages/kit/src/runtime/server/page/csp.js:95 — constructor has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 14, if/else 2 (3 pts), ternaries 1 (nesting depth added 1). Of this number, 11 points are the body's own statements and 7 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · requested (cognitive 18) · ×1
  • requested (cognitive 18) packages/kit/src/runtime/app/server/remote/requested.js:104 — requested has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (7 pts), loops 5, error handling 3 (4 pts), boolean chains 1, other 1 (nesting depth added 2). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 163, refreshAll, reconnectAll, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · server_data_serializer.get_replacer (cognitive 18) · ×1
  • server_data_serializer.get_replacer (cognitive 18) packages/kit/src/runtime/server/page/data_serializer.js:25 — server_data_serializer.get_replacer has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 2 (6 pts), error handling 2 (5 pts), if/else 3 (5 pts), loops 1 (2 pts) (nesting depth added 10). None of this is in the body itself: all 18 points belong to 5 function items inside it that branch (replacer, a function literal at line 42, a function literal at line 32, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.default.adapt (cognitive 17) · ×1
  • index.default.adapt (cognitive 17) packages/adapter-bun/index.js:85 — index.default.adapt has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 3, loops 1 (2 pts), ternaries 2 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · client.has_changed (cognitive 17) · ×1
  • client.has_changed (cognitive 17) packages/kit/src/runtime/client/client.js:1293 — client.has_changed has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 3 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolve_route (cognitive 17) · ×1
  • resolve_route (cognitive 17) REDACTED:311 — resolve_route has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 319, 318). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · create_remote_arg_revivers (cognitive 17) · ×1
  • create_remote_arg_revivers (cognitive 17) packages/kit/src/runtime/shared.js:184 — create_remote_arg_revivers has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (7 pts), loops 2 (nesting depth added 2). None of this is in the body itself: all 17 points belong to 5 function items inside it that branch (a function literal at line 229, a function literal at line 189, a function literal at line 212, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · plugin_guard · ×1
  • plugin_guard::handler (cognitive 17) packages/kit/src/exports/vite/plugins/guard.js:114 — plugin_guard::handler has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, loops 1, other 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · render_data (cognitive 17) · ×1
  • render_data (cognitive 17) packages/kit/src/runtime/server/data/index.js:21 — render_data has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 3, loops 1, other 1, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 39, (anonymous)::(anonymous)::parent, a function literal at line 76, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · handle_error_and_jsonify (cognitive 17) · ×1
  • handle_error_and_jsonify (cognitive 17) packages/kit/src/runtime/server/errors.js:21 — handle_error_and_jsonify has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), error handling 2 (4 pts), loops 1 (2 pts), boolean chains 1, ternaries 1 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · serialize_data (cognitive 17) · ×1
  • serialize_data (cognitive 17) packages/kit/src/runtime/server/page/serialize_data.js:43 — serialize_data has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, other 2, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · vite-plugin.image_plugin (cognitive 16) · ×1
  • vite-plugin.image_plugin (cognitive 16) packages/enhanced-img/src/vite-plugin.js:18 — vite-plugin.image_plugin has cognitive complexity 16 (threshold 15). Drivers by points: if/else 20 (29 pts), ternaries 6 (12 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (vite-plugin.image_plugin::update_element) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · index.create_node_analyser.get_page_options (cognitive 16) · ×1
  • index.create_node_analyser.get_page_options (cognitive 16) packages/kit/src/exports/vite/static_analysis/index.js:252 — index.create_node_analyser.get_page_options has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · goto (cognitive 16) · ×1
  • goto (cognitive 16) packages/kit/src/runtime/client/client.js:2629 — goto has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), other 5, boolean chains 4 (nesting depth added 2). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · deep_set (cognitive 16) · ×1
  • deep_set (cognitive 16) packages/kit/src/runtime/form-utils.js:522 — deep_set has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · flatten_issues (cognitive 16) · ×1
  • flatten_issues (cognitive 16) packages/kit/src/runtime/form-utils.js:593 — flatten_issues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 1 (5 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create_node_analyser.crawl (cognitive 16) · ×1
  • create_node_analyser.crawl (cognitive 16) packages/kit/src/exports/vite/static_analysis/index.js:252 — create_node_analyser.crawl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · forked (cognitive 16) · ×1
  • forked (cognitive 16) packages/kit/src/utils/fork.js:15 — forked has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 3). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 71, 90, 19, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Fake-async · ×1
  • Fake-async — async method never awaits packages/kit/src/runtime/app/paths/internal/client.js:21 — `match_implementation` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
P12 · CI test-gate honesty · Pull-request path filter skips the test gate for source changes · ×1
  • Pull-request path filter skips the test gate for source changes .github/workflows/ci.yml:8 — `paths-ignore: .changeset/**` matches compiled source (`.changeset/changelog.js`) — a pull request that changes only those files merges without running the tests. Ignore only documentation and other files no build reads.
R10 · Code Duplication · Duplication concentrated across 9 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 9 sibling directories (10 clone groups) packages/adapter-bun/index.js:169 — 10 duplicated blocks under packages/ have copies in at least two of the sibling directories adapter-auto, adapter-bun, adapter-cloudflare, adapter-netlify, adapter-node, adapter-static (+3 more sibling(s) not listed) — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (75 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (75 matched lines × 2 locations) packages/kit/src/runtime/client/remote-functions/query-live/proxy.js:21 — packages/kit/src/runtime/client/remote-functions/query-live/proxy.js:21 · packages/kit/src/runtime/client/remote-functions/query/proxy.js:30 — the two spans are one implementation copied and then locally edited — 433 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (39 lines × 2 locations) · ×1
  • Duplicated block (39 lines × 2 locations) packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:290 — packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js:290 · packages/kit/src/runtime/client/remote-functions/query/instance.svelte.js:167 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (35 matched lines × 2 locations) packages/kit/src/runtime/server/page/load_data.js:46 — packages/kit/src/runtime/server/page/load_data.js:46 · packages/kit/src/runtime/server/page/load_data.js:143 — the two spans are one implementation copied and then locally edited — 167 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) packages/adapter-bun/index.js:169 — packages/adapter-bun/index.js:169 · packages/adapter-node/index.js:82 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) packages/adapter-static/platforms.js:34 — packages/adapter-static/platforms.js:34 · packages/adapter-vercel/index.js:407 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1
  • Duplicated block (27 lines × 2 locations) packages/kit/src/runtime/app/server/remote/query.js:432 — packages/kit/src/runtime/app/server/remote/query.js:432 · packages/kit/src/runtime/app/server/remote/query.js:519 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:25 — packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:25 · packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:69 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (20 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (20 matched lines × 2 locations) packages/kit/src/runtime/server/data/index.js:39 — packages/kit/src/runtime/server/data/index.js:39 · packages/kit/src/runtime/server/page/index.js:171 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) packages/kit/src/cli.js:48 — packages/kit/src/cli.js:48 · packages/package/src/cli.js:49 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (17 matched lines × 2 locations) packages/kit/src/runtime/app/paths/client.js:10 — packages/kit/src/runtime/app/paths/client.js:10 · packages/kit/src/runtime/app/paths/server.js:11 — the two spans are one implementation copied and then locally edited — 103 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (15 matched lines × 2 locations) packages/kit/src/messages/internal/build.js:22 — packages/kit/src/messages/internal/build.js:22 · packages/kit/src/messages/internal/server.js:13 — the two spans are one implementation copied and then locally edited — 91 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×1
  • Duplicated block (15 lines × 2 locations) packages/kit/src/pathname.js:1 — packages/kit/src/pathname.js:1 · packages/kit/src/pathname.js:24 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (14 matched lines × 2 locations) packages/adapter-cloudflare/index.js:27 — packages/adapter-cloudflare/index.js:27 · packages/adapter-netlify/index.js:32 — the two spans are one implementation copied and then locally edited — 74 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×1
  • Duplicated block (13 lines × 2 locations) packages/kit/src/exports/vite/build/index.js:182 — packages/kit/src/exports/vite/build/index.js:182 · packages/kit/src/exports/vite/dev/index.js:365 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (13 matched lines × 2 locations) packages/kit/src/messages/internal/server.js:13 — packages/kit/src/messages/internal/server.js:13 · packages/kit/src/messages/internal/shared.js:28 — the two spans are one implementation copied and then locally edited — 72 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (11 lines × 3 locations) · ×1
  • Duplicated block (11 lines × 3 locations) packages/kit/src/runtime/app/server/remote/query.js:88 — packages/kit/src/runtime/app/server/remote/query.js:88 · packages/kit/src/runtime/app/server/remote/query.js:186 · packages/kit/src/runtime/app/server/remote/query.js:363 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×1
  • Duplicated block (11 lines × 2 locations) packages/kit/src/runtime/client/client.js:2121 — packages/kit/src/runtime/client/client.js:2121 · packages/kit/src/runtime/client/client.js:2937 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (8 matched lines × 2 locations) packages/adapter-vercel/index.js:210 — packages/adapter-vercel/index.js:210 · packages/adapter-vercel/index.js:300 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (8 lines × 2 locations) · ×1
  • Duplicated block (8 lines × 2 locations) packages/kit/src/cli.js:15 — packages/kit/src/cli.js:15 · packages/package/src/cli.js:11 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R2 · Cyclomatic Complexity · Complex function render_response (cyclomatic 96, cognitive 173) · ×1
  • Complex function render_response (cyclomatic 96, cognitive 173) packages/kit/src/runtime/server/page/render.js:55 — render_response has cyclomatic complexity 96 and cognitive complexity 173; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function crawl (cyclomatic 60, cognitive 226) · ×1
  • Complex function crawl (cyclomatic 60, cognitive 226) packages/kit/src/core/postbuild/crawl.js:34 — crawl has cyclomatic complexity 60 and cognitive complexity 226; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function navigate (cyclomatic 48, cognitive 72) · ×1
  • Complex function navigate (cyclomatic 48, cognitive 72) packages/kit/src/runtime/client/client.js:1940 — navigate has cyclomatic complexity 48 and cognitive complexity 72; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function statically_analyse_page_options (cyclomatic 45, cognitive 120) · ×1
  • Complex function statically_analyse_page_options (cyclomatic 45, cognitive 120) packages/kit/src/exports/vite/static_analysis/index.js:32 — statically_analyse_page_options has cyclomatic complexity 45 and cognitive complexity 120; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function fetch (cyclomatic 41, cognitive 51) · ×1
  • Complex function fetch (cyclomatic 41, cognitive 51) packages/kit/src/runtime/server/fetch.js:34 — fetch has cyclomatic complexity 41 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function walk (cyclomatic 40, cognitive 76) · ×1
  • Complex function walk (cyclomatic 40, cognitive 76) packages/kit/src/core/sync/create_manifest_data/index.js:139 — walk has cyclomatic complexity 40 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function create_routes_and_nodes (cyclomatic 39, cognitive 75) · ×1
  • Complex function create_routes_and_nodes (cyclomatic 39, cognitive 75) packages/kit/src/core/sync/create_manifest_data/index.js:120 — create_routes_and_nodes has cyclomatic complexity 39 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function render_page (cyclomatic 39, cognitive 65) · ×1
  • Complex function render_page (cyclomatic 39, cognitive 65) packages/kit/src/runtime/server/page/index.js:42 — render_page has cyclomatic complexity 39 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function prerender (cyclomatic 37, cognitive 65) · ×1
  • Complex function prerender (cyclomatic 37, cognitive 65) packages/kit/src/core/postbuild/prerender.js:47 — prerender has cyclomatic complexity 37 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 35, cognitive 43) · ×1
  • Complex function (anonymous) (cyclomatic 35, cognitive 43) packages/kit/src/runtime/client/client.js:3142 — (anonymous) has cyclomatic complexity 35 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function should_ignore (cyclomatic 35, cognitive 36) · ×1
  • Complex function should_ignore (cyclomatic 35, cognitive 36) packages/kit/src/exports/vite/static_analysis/utils.js:24 — should_ignore has cyclomatic complexity 35 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function build_server_nodes (cyclomatic 33, cognitive 63) · ×1
  • Complex function build_server_nodes (cyclomatic 33, cognitive 63) packages/kit/src/exports/vite/build/build_server.js:28 — build_server_nodes has cyclomatic complexity 33 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handle_submit (cyclomatic 33, cognitive 40) · ×1
  • Complex function handle_submit (cyclomatic 33, cognitive 40) packages/kit/src/runtime/app/forms/client.js:113 — handle_submit has cyclomatic complexity 33 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 31, cognitive 92) · ×1
  • Complex function (anonymous) (cyclomatic 31, cognitive 92) packages/kit/src/core/sync/create_manifest_data/sort.js:66 — (anonymous) has cyclomatic complexity 31 and cognitive complexity 92; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function adapt (cyclomatic 31, cognitive 61) · ×1
  • Complex function adapt (cyclomatic 31, cognitive 61) packages/adapter-vercel/index.js:21 — adapt has cyclomatic complexity 31 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 30, cognitive 37) · ×1
  • Complex function (anonymous) (cyclomatic 30, cognitive 37) packages/kit/src/runtime/form-utils.js:806 — (anonymous) has cyclomatic complexity 30 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function get_navigation_result_from_branch (cyclomatic 28, cognitive 35) · ×1
  • Complex function get_navigation_result_from_branch (cyclomatic 28, cognitive 35) packages/kit/src/runtime/client/client.js:965 — get_navigation_result_from_branch has cyclomatic complexity 28 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function load_route (cyclomatic 27, cognitive 53) · ×1
  • Complex function load_route (cyclomatic 27, cognitive 53) packages/kit/src/runtime/client/client.js:1373 — load_route has cyclomatic complexity 27 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function analyse (cyclomatic 27, cognitive 39) · ×1
  • Complex function analyse (cyclomatic 27, cognitive 39) packages/kit/src/core/postbuild/analyse.js:31 — analyse has cyclomatic complexity 27 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function generate_app_types (cyclomatic 26, cognitive 56) · ×1
  • Complex function generate_app_types (cyclomatic 26, cognitive 56) packages/kit/src/core/sync/write_app_types.js:107 — generate_app_types has cyclomatic complexity 26 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function visit (cyclomatic 26, cognitive 46) · ×1
  • Complex function visit (cyclomatic 26, cognitive 46) packages/kit/src/core/postbuild/prerender.js:376 — visit has cyclomatic complexity 26 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 26, cognitive 35) · ×1
  • Complex function (anonymous) (cyclomatic 26, cognitive 35) packages/adapter-node/src/static.js:172 — (anonymous) has cyclomatic complexity 26 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function treeshake_prerendered_remotes (cyclomatic 25, cognitive 58) · ×1
  • Complex function treeshake_prerendered_remotes (cyclomatic 25, cognitive 58) packages/kit/src/exports/vite/build/remote.js:21 — treeshake_prerendered_remotes has cyclomatic complexity 25 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function process_ssr_build (cyclomatic 25, cognitive 47) · ×1
  • Complex function process_ssr_build (cyclomatic 25, cognitive 47) packages/kit/src/exports/vite/build/index.js:452 — process_ssr_build has cyclomatic complexity 25 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function write_all_types (cyclomatic 25, cognitive 40) · ×1
  • Complex function write_all_types (cyclomatic 25, cognitive 40) packages/kit/src/core/sync/write_types/index.js:58 — write_all_types has cyclomatic complexity 25 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 23, cognitive 35) · ×1
  • Complex function (anonymous) (cyclomatic 23, cognitive 35) packages/kit/src/runtime/client/client.js:3311 — (anonymous) has cyclomatic complexity 23 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function adapt (cyclomatic 23, cognitive 33) · ×1
  • Complex function adapt (cyclomatic 23, cognitive 33) packages/adapter-cloudflare/index.js:29 — adapt has cyclomatic complexity 23 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function render_endpoint (cyclomatic 23, cognitive 25) · ×1
  • Complex function render_endpoint (cyclomatic 23, cognitive 25) packages/kit/src/runtime/server/endpoint.js:14 — render_endpoint has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handler (cyclomatic 22, cognitive 53) · ×1
  • Complex function handler (cyclomatic 22, cognitive 53) REDACTED:109 — handler has cyclomatic complexity 22 and cognitive complexity 53; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function update_types (cyclomatic 22, cognitive 33) · ×1
  • Complex function update_types (cyclomatic 22, cognitive 33) packages/kit/src/core/sync/write_types/index.js:215 — update_types has cyclomatic complexity 22 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function update_element (cyclomatic 21, cognitive 32) · ×1
  • Complex function update_element (cyclomatic 21, cognitive 32) packages/enhanced-img/src/vite-plugin.js:85 — update_element has cyclomatic complexity 21 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function save (cyclomatic 21, cognitive 32) · ×1
  • Complex function save (cyclomatic 21, cognitive 32) packages/kit/src/core/postbuild/prerender.js:542 — save has cyclomatic complexity 21 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 21, cognitive 24) · ×1
  • Complex function (anonymous) (cyclomatic 21, cognitive 24) packages/kit/src/exports/vite/dev/index.js:311 — (anonymous) has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 20, cognitive 31) · ×1
  • Complex function (anonymous) (cyclomatic 20, cognitive 31) packages/kit/src/core/sync/write_types/index.js:815 — (anonymous) has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function exec (cyclomatic 20, cognitive 28) · ×1
  • Complex function exec (cyclomatic 20, cognitive 28) REDACTED:190 — exec has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function validate (cyclomatic 20, cognitive 27) · ×1
  • Complex function validate (cyclomatic 20, cognitive 27) REDACTED:145 — validate has cyclomatic complexity 20 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _start (cyclomatic 20, cognitive 26) · ×1
  • Complex function _start (cyclomatic 20, cognitive 26) packages/kit/src/runtime/client/client.js:461 — _start has cyclomatic complexity 20 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handle_remote_call_internal (cyclomatic 20, cognitive 22) · ×1
  • Complex function handle_remote_call_internal (cyclomatic 20, cognitive 22) packages/kit/src/runtime/server/remote-functions.js:198 — handle_remote_call_internal has cyclomatic complexity 20 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function get_routes_json (cyclomatic 19, cognitive 34) · ×1
  • Complex function get_routes_json (cyclomatic 19, cognitive 34) REDACTED:136 — get_routes_json has cyclomatic complexity 19 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function create_env_modules (cyclomatic 18, cognitive 29) · ×1
  • Complex function create_env_modules (cyclomatic 18, cognitive 29) REDACTED:152 — create_env_modules has cyclomatic complexity 18 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · packages/kit/src/runtime/client/client.js · ×1
  • packages/kit/src/runtime/client/client.js: 3278 lines of code packages/kit/src/runtime/client/client.js:1 — packages/kit/src/runtime/client/client.js has 3278 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 2256 lines of code REDACTED:1 — REDACTED has 2256 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/runtime/form-utils.js · ×1
  • packages/kit/src/runtime/form-utils.js: 819 lines of code packages/kit/src/runtime/form-utils.js:1 — packages/kit/src/runtime/form-utils.js has 819 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/core/sync/write_types/index.js · ×1
  • packages/kit/src/core/sync/write_types/index.js: 782 lines of code packages/kit/src/core/sync/write_types/index.js:1 — packages/kit/src/core/sync/write_types/index.js has 782 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/runtime/client/remote-functions/form.svelte.js · ×1
  • packages/kit/src/runtime/client/remote-functions/form.svelte.js: 688 lines of code packages/kit/src/runtime/client/remote-functions/form.svelte.js:1 — packages/kit/src/runtime/client/remote-functions/form.svelte.js has 688 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/core/postbuild/prerender.js · ×1
  • packages/kit/src/core/postbuild/prerender.js: 622 lines of code packages/kit/src/core/postbuild/prerender.js:1 — packages/kit/src/core/postbuild/prerender.js has 622 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/exports/vite/index.js · ×1
  • packages/kit/src/exports/vite/index.js: 615 lines of code packages/kit/src/exports/vite/index.js:1 — packages/kit/src/exports/vite/index.js has 615 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/runtime/app/server/remote/query.js · ×1
  • packages/kit/src/runtime/app/server/remote/query.js: 594 lines of code packages/kit/src/runtime/app/server/remote/query.js:1 — packages/kit/src/runtime/app/server/remote/query.js has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/runtime/server/page/render.js · ×1
  • packages/kit/src/runtime/server/page/render.js: 590 lines of code packages/kit/src/runtime/server/page/render.js:1 — packages/kit/src/runtime/server/page/render.js has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/adapter-vercel/index.js · ×1
  • packages/adapter-vercel/index.js: 582 lines of code packages/adapter-vercel/index.js:1 — packages/adapter-vercel/index.js has 582 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/runtime/server/remote-functions.js · ×1
  • packages/kit/src/runtime/server/remote-functions.js: 537 lines of code packages/kit/src/runtime/server/remote-functions.js:1 — packages/kit/src/runtime/server/remote-functions.js has 537 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/adapter-netlify/index.js · ×1
  • packages/adapter-netlify/index.js: 509 lines of code packages/adapter-netlify/index.js:1 — packages/adapter-netlify/index.js has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/core/sync/create_manifest_data/index.js · ×1
  • packages/kit/src/core/sync/create_manifest_data/index.js: 499 lines of code packages/kit/src/core/sync/create_manifest_data/index.js:1 — packages/kit/src/core/sync/create_manifest_data/index.js has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/runtime/server/page/load_data.js · ×1
  • packages/kit/src/runtime/server/page/load_data.js: 440 lines of code packages/kit/src/runtime/server/page/load_data.js:1 — packages/kit/src/runtime/server/page/load_data.js has 440 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/kit/src/exports/vite/dev/index.js · ×1
  • packages/kit/src/exports/vite/dev/index.js: 439 lines of code packages/kit/src/exports/vite/dev/index.js:1 — packages/kit/src/exports/vite/dev/index.js has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/enhanced-img/src/vite-plugin.js · ×1
  • packages/enhanced-img/src/vite-plugin.js: 412 lines of code packages/enhanced-img/src/vite-plugin.js:1 — packages/enhanced-img/src/vite-plugin.js has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1
  • The declared test suite includes a file that cannot be loaded packages/kit/src/core/postbuild/crawl.spec.js:6 — This repository declares test tooling, and the ✓ above records that declaration — but packages/kit/src/core/postbuild/crawl.spec.js and 2 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
R7 · Dead Code · Dead file (~147 LoC) · ×1
  • Dead file (~147 LoC) packages/kit/src/runtime/server/instance.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/kit/src/runtime/server/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~96 LoC) · ×1
  • Dead file (~96 LoC) packages/kit/src/runtime/client/remote-functions/query-batch.svelte.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/kit/src/runtime/client/remote-functions/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~80 LoC) · ×1
  • Dead file (~80 LoC) packages/kit/src/runtime/server/index.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~41 LoC) · ×1
  • Dead file (~41 LoC) packages/kit/src/runtime/client/remote-functions/query/index.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/kit/src/runtime/client/remote-functions/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~37 LoC) · ×1
  • Dead file (~37 LoC) packages/kit/src/runtime/app/stores.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~35 LoC) · ×1
  • Dead file (~35 LoC) scripts/check-dependencies.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~31 LoC) · ×1
  • Dead file (~31 LoC) packages/kit/src/runtime/client/remote-functions/query-live/index.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/kit/src/runtime/client/remote-functions/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~24 LoC) · ×1
  • Dead file (~24 LoC) packages/kit/src/runtime/client/entry.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~17 LoC) · ×1
  • Dead file (~17 LoC) packages/kit/src/runtime/client/bundle.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~7 LoC) · ×1
  • Dead file (~7 LoC) packages/kit/src/runtime/app/environment/index.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~3 LoC) · ×1
  • Dead file (~3 LoC) packages/kit/src/runtime/client/client-entry.js — no import path from any entry point (1623 application, 207 tooling, 2270 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/kit/src/runtime/client/bundle.js, packages/kit/src/runtime/client/entry.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R8 · Dependency Hygiene · Unused dependency '@netlify/edge-functions' · ×1
  • Unused dependency '@netlify/edge-functions' — Declared in packages/adapter-netlify/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×1
  • Recursive walk over a caller-supplied document has no depth cap packages/kit/src/exports/vite/utils.js:331 — `find_overridden_config` is exported and takes `config: object` from its caller, and it calls itself at line 331 (`find_overridden_config`) with a piece of `config` — and nowhere in `find_overridden_config` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `find_overridden_config` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Minor — 106 finding(s)
IC1 · Incompleteness & stubs · Disabled test · ×36
  • Disabled test packages/adapter-bun/test/apps/basic/test/server.test.js:21 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/adapter-cloudflare/test/apps/workers/test/test.js:31 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/src/runtime/server/page/csp.spec.js:45 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/client.test.js:5 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/client.test.js:12 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/server.test.js:8 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/server.test.js:14 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/server.test.js:40 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/server.test.js:45 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/server.test.js:53 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/server.test.js:66 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/server.test.js:89 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/test.js:99 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/test.js:155 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/test.js:282 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/test.js:306 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/test.js:340 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/test.js:353 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/test.js:684 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/async/test/test.js:1128 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/basics/test/playwright/client.test.js:7 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/basics/test/playwright/cross-platform/client.test.js:7 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/basics/test/playwright/cross-platform/server.test.js:7 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/basics/test/playwright/cross-platform/server.test.js:13 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/kit/test/apps/basics/test/playwright/server.test.js:7 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • + 11 more in this group — see findings.md.
P2 · Observability · Console output used as the logging channel · ×26
  • Console output used as the logging channel packages/adapter-bun/src/handler.js:7 — `packages/adapter-bun/src/handler.js` reports through `console.*` at line 7 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/adapter-bun/src/handler.js:68 — `packages/adapter-bun/src/handler.js` reports through `console.*` at line 68 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/runtime/server/errors.js:108 — `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 108 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/runtime/server/errors.js:110 — `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 110 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/runtime/server/errors.js:112 — `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 112 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/runtime/server/errors.js:129 — `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 129 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/runtime/server/errors.js:141 — `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 141 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/runtime/server/errors.js:147 — `packages/kit/src/runtime/server/errors.js` reports through `console.*` at line 147 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/runtime/server/instance.js:84 — `packages/kit/src/runtime/server/instance.js` reports through `console.*` at line 84 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/runtime/server/instance.js:106 — `packages/kit/src/runtime/server/instance.js` reports through `console.*` at line 106 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/runtime/client/remote-functions/prerender.svelte.js:29 — `packages/kit/src/runtime/client/remote-functions/prerender.svelte.js` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/messages/internal/build.js:57 — `packages/kit/src/messages/internal/build.js` reports through `console.*` at line 57 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/exports/hooks/sequence.js:23 — `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/exports/hooks/sequence.js:27 — `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 27 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/exports/hooks/sequence.js:32 — `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/exports/hooks/sequence.js:36 — `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 36 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/exports/hooks/sequence.js:42 — `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/exports/hooks/sequence.js:45 — `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/exports/hooks/sequence.js:49 — `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/exports/hooks/sequence.js:54 — `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 54 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/exports/hooks/sequence.js:58 — `packages/kit/src/exports/hooks/sequence.js` reports through `console.*` at line 58 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/core/utils.js:43 — `packages/kit/src/core/utils.js` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/core/utils.js:46 — `packages/kit/src/core/utils.js` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/core/utils.js:50 — `packages/kit/src/core/utils.js` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/kit/src/core/sync/write_client_manifest.js:165 — `packages/kit/src/core/sync/write_client_manifest.js` reports through `console.*` at line 165 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • + 1 more in this group — see findings.md.
D19 · Documentation Quality · Documentation · ×7
  • Documentation: no build, run or usage example packages/adapter-auto/README.md:1 — `adapter-auto` is a published package (`package.json` without `"private": true`) and neither `packages/adapter-auto/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/adapter-cloudflare/README.md:1 — `adapter-cloudflare` is a published package (`package.json` without `"private": true`) and neither `packages/adapter-cloudflare/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/adapter-netlify/README.md:1 — `adapter-netlify` is a published package (`package.json` without `"private": true`) and neither `packages/adapter-netlify/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/adapter-node/README.md:1 — `adapter-node` is a published package (`package.json` without `"private": true`) and neither `packages/adapter-node/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/adapter-static/README.md:1 — `adapter-static` is a published package (`package.json` without `"private": true`) and neither `packages/adapter-static/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/adapter-vercel/README.md:1 — `adapter-vercel` is a published package (`package.json` without `"private": true`) and neither `packages/adapter-vercel/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/enhanced-img/README.md:1 — `enhanced-img` is a published package (`package.json` without `"private": true`) and neither `packages/enhanced-img/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
X10 · Duplicated predicate · Duplicated predicate · ×6
  • Duplicated predicate packages/kit/src/runtime/client/client.js:1589 — `action_result?.type === 'success' || action_result?.type === 'failure'` appears character-identically in 2 files — packages/kit/src/runtime/client/client.js, packages/kit/src/runtime/server/page/render.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/kit/src/core/adapt/builder.js:185 — `config.paths.origin || 'http://sveltekit-prerender'` appears character-identically in 2 files — packages/kit/src/core/adapt/builder.js, packages/kit/src/core/postbuild/prerender.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/kit/src/exports/vite/dev/index.js:274 — `req.headers[':authority'] || req.headers.host` appears character-identically in 2 files — packages/kit/src/exports/vite/dev/index.js, packages/kit/src/exports/vite/preview/index.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/kit/src/exports/vite/dev/index.js:67 — `typeof info === 'string' && !SCHEME.test(info)` appears character-identically in 2 files — packages/kit/src/exports/vite/dev/index.js, packages/kit/src/runtime/server/page/render.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/adapter-bun/src/env.js:163 — `url.protocol !== 'http:' && url.protocol !== 'https:'` appears character-identically in 3 files — packages/adapter-bun/src/env.js, REDACTED, packages/kit/src/core/config/options.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/kit/src/utils/imports.js:30 — `value && typeof value === 'object' && typeof value.default === 'string'` appears character-identically in 2 files — packages/kit/src/utils/imports.js, packages/package/src/index.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D24 · Comment Value · redundant comment · ×3
  • redundant comment packages/kit/src/exports/vite/build/index.js:185 — "...and the server instrumentation file" repeats the code it sits on: 3 of its 3 words (server, instrumentation, file) are already in `const server_instrumentation = resolve_entry(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/kit/test/apps/async/test/client.test.js:1138 — "click button to call field.set()" repeats the code it sits on: 4 of its 5 words (click, call, field, set) are already in `await page.click('#set-text-field');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/kit/test/apps/basics/test/vitest/server.spec.js:1091 — 6 comments in this file only repeat the code they sit on (lines 1091, 1181, 1254, 1310, 1400, 1464), for example "Find and verify the resolve.root span". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
IC1 · Incompleteness & stubs · Empty method body · ×3
  • Empty method body packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:147 — `end` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:148 — `recordException` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/adapter-cloudflare/src/virtual-cloudflare-workers.js:161 — `getActiveSpan` has an empty body — confirm it's an intentional no-op and not an unfinished method.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×2
  • No app-layer HTTPS enforcement detected packages/adapter-node/src/index.js:77 — `httpServer.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
  • No app-layer HTTPS enforcement detected packages/adapter-node/src/index.js:91 — `httpServer.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
C2 · Access Controls · Thin authorization enforcement · ×1
  • Thin authorization enforcement — Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 35 significant file(s) lose their only recent owner: packages/kit/src/runtime/server/remote-functions.js, packages/kit/src/core/sync/create_manifest_data/index.js, packages/kit/src/runtime/client/remote-functions/shared.svelte.js, packages/kit/src/runtime/shared.js, packages/kit/src/exports/vite/dev/generate_manifest.js, packages/adapter-node/index.js, packages/kit/src/exports/vite/static_analysis/index.js, packages/kit/src/runtime/server/page/actions.js (+27 more). Pair on, review, or document these before any departure.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found packages/package/package.json:49 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `packages/package/package.json` makes this repository a deployable product (line 49).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 8.3/10. The most over is `packages/kit` (32346 LoC, 187 module-visible types across 44 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D30 · Dependency Vulnerabilities · Low CVE · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 6/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/adapter-netlify`, `packages/adapter-node`, `packages/package`, `packages/test-redirect-importer`, `playgrounds/basic`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST .github/workflows/ci.yml:24 — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
R7 · Dead Code · Unused module-local declaration 'layoutOnlyParams' · ×1
  • Unused module-local declaration 'layoutOnlyParams' packages/kit/src/core/sync/write_types/test/app-types/+page.js:56 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'endpointParams' · ×1
  • Unused module-local declaration 'endpointParams' packages/kit/src/core/sync/write_types/test/app-types/+page.js:61 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'impossible_manifest_routes' · ×1
  • Unused module-local declaration 'impossible_manifest_routes' packages/kit/src/core/sync/write_types/test/app-types/+page.js:72 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'noMatcherLayoutParams' · ×1
  • Unused module-local declaration 'noMatcherLayoutParams' packages/kit/src/core/sync/write_types/test/app-types/+page.js:134 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'matcherParentLayoutParams' · ×1
  • Unused module-local declaration 'matcherParentLayoutParams' packages/kit/src/core/sync/write_types/test/app-types/+page.js:171 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration '_valid' · ×1
  • Unused module-local declaration '_valid' packages/kit/src/core/sync/write_types/test/param-type-inference/resolve-types.js:4 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration '_invalid_string' · ×1
  • Unused module-local declaration '_invalid_string' packages/kit/src/core/sync/write_types/test/param-type-inference/resolve-types.js:8 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration '_invalid_boolean' · ×1
  • Unused module-local declaration '_invalid_boolean' packages/kit/src/core/sync/write_types/test/param-type-inference/resolve-types.js:12 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R8 · Dependency Hygiene · Type-only dependency '@cloudflare/workers-types' in production deps · ×1
  • Type-only dependency '@cloudflare/workers-types' in production deps packages/adapter-cloudflare/files/worker.js:34 — Every import is type-only — move it to devDependencies.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 4/10 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 3/66 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch packages/adapter-auto/index.js:40 — `detect_package_manager` swallows every exception into `return 'npm'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Minor — 19 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×13
  • Outdated (npm): @cloudflare/workers-types — @cloudflare/workers-types is pinned at 5.20260925.1; registry.npmjs.org publishes 5.20261115.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @netlify/types — @netlify/types is pinned at 3.2.0; registry.npmjs.org publishes 3.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @rolldown/pluginutils — @rolldown/pluginutils is pinned at 1.0.1; registry.npmjs.org publishes 1.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @vercel/nft — @vercel/nft is pinned at 1.11.0; registry.npmjs.org publishes 1.11.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): bun-types — bun-types is pinned at 1.4.2; registry.npmjs.org publishes 1.4.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): cookie — cookie is pinned at 2.0.1; registry.npmjs.org publishes 2.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): devalue — devalue is pinned at 5.9.4; registry.npmjs.org publishes 6.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): jsdom — jsdom is pinned at 30.1.0; registry.npmjs.org publishes 31.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): magic-string — magic-string is pinned at 1.4.1; registry.npmjs.org publishes 1.4.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): rolldown — rolldown is pinned at 1.2.9; registry.npmjs.org publishes 1.3.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): svelte2tsx — svelte2tsx is pinned at 0.7.61; registry.npmjs.org publishes 0.7.63 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): vite-imagetools — vite-imagetools is pinned at 12.0.1; registry.npmjs.org publishes 12.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): wrangler — wrangler is pinned at 4.136.1; registry.npmjs.org publishes 4.162.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
D10 · Test Quality · Skipped (documented) · ×4
  • Skipped (documented): (unnamed test) packages/kit/test/apps/basics/test/vitest/server.spec.js:244 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
  • Skipped (documented): (unnamed test) packages/kit/test/apps/basics/test/vitest/server.spec.js:1011 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
  • Skipped (documented): (unnamed test) packages/kit/test/apps/basics/test/vitest/server.spec.js:1019 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
  • Skipped (documented): (unnamed test) packages/kit/test/apps/basics/test/vitest/server.spec.js:1032 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
D24 · Comment Value · doc comments repeat the names · ×2
  • doc comments repeat the names packages/kit/src/runtime/app/forms/client.js:54 — 1 of 132 documented parameters and 0 of 418 summaries in `@sveltejs/kit` only repeat the member or parameter name (e.g. "The form element" for `form_element`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/package/src/utils.js:11 — 0 of 4 documented parameters and 1 of 14 summaries in `@sveltejs/package` only repeat the member or parameter name (e.g. "Resolves aliases" for `resolve_aliases`). Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4bbb4afd2f9c4ec3b3adbbe981d5dbec/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4bbb4afd2f9c4ec3b3adbbe981d5dbec/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .17artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .12artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 9 file(s) — `packages/adapter-bun/index.d.ts`, `packages/adapter-bun/internal.d.ts`, `packages/adapter-netlify/ambient.d.ts`, `packages/kit/src/exports/public.d.ts`, `packages/kit/src/runtime/app/paths/types.d.ts`, … (+4 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1dd61-e6d0-7840-8d02-8a527eacdb7d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md