Public report of remix-run/react-router, published 26 October 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.10.5). Watchdog 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, 26 October 2026, 14:27 UTC · Survey ID cd_cf0c37b9cee74ca6a27af5ceb934f17b

remix-run/react-router

Measured 26 October 2026, 14:00 UTC, at code version bb7c1f0

Regression: 2 dimensions fell since the last survey Code coverage: not measured

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).

CAI score 45out 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.

Architecture 88 Strong Performance 71 Strong Accessibility 70 Strong Maturity 70 Adequate Production Readiness 43 Weak Code Health 40 Weak Security and Compliance 39 Weak

A medium codebase: 55,754 lines of product code in 19 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Security and Compliance, 39

Findings by how serious they are

116 critical 729 serious 221 minor

8 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 14:00 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 Watchdog. It is open to any tool that implements it, and today Watchdog 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. Watchdog works 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 ▸

83of 83 dimensions measured by tools.
974of 1066 findings point to an exact file and line, so you can open each one in the code. The other 92 concern the repository as a whole, such as missing documentation.
83dimensions across 7 lenses, read from 55,754 lines of product code in 19 projects.
Chapters

Executive summary

remix-run/react-router is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because 37 of the dependencies have a known vulnerability and we found no access checks on the code's endpoints or handlers. It scores 45 out of 100, which the At risk rating leaves unchanged.

Security and Compliance, at 39, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is adding access checks, worth about 5 points. Replacing the 13 deprecated dependencies comes next, worth about 3 points.

Forty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirty-nine known security holes in the packages the code depends on can be used by attackers, and nine weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, updating the vulnerable packages and fixing the weaknesses the scanner points to would close these risks. Correcting the flagged pipeline settings would fix the ten weaknesses in the build pipeline's configuration, and setting a waiting period for automatic updates would deal with the three automatic dependency updates that take new releases at once. The two tests that check nothing need to check the result they produce.

The product code is 55,754 lines, about €160,000 to rebuild.

Code Health 40 Weak, capped by Cyclomatic Complexity, Cognitive Complexity, Large Files and Dead Code Architecture 88 Strong Maturity 70 Adequate Production Readiness 43 Weak, capped by Dependency Hygiene and Security & performance tooling Security and Compliance 39 Weak, capped by Static Analysis (SAST), Dependency Vulnerabilities, Supply-chain Provenance & Signing and Access Controls Accessibility 70 Strong Performance 71 Strong

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.
Security and Compliance 39 · counts for 46%Code Health 40 · counts for 25%Production Readiness 43 · counts for 14%Maturity 70 · counts for 8%Accessibility 70 · counts for 4%Performance 71 · counts for 2%Architecture 88 · 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 31%Tests 69%
New since the last survey: 171 findings

These 171 critical or serious findings weren't in the previous survey, on 12 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

Watchdog compares 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: 636 findings

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

  • Churn × Complexity Hotspots · Hotspot: packages/react-router/lib/rsc/browser.tsx packages/react-router/lib/rsc/browser.tsx
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
  • Change Coupling · Change coupling: build.ts ↔ REDACTED packages/react-router-dev/vite/build.ts
  • Supply-chain Provenance & Signing REDACTED
  • Supply-chain Provenance & Signing REDACTED
  • Code Duplication · Duplicated block (26 lines × 2 locations) packages/react-router/lib/router/router.ts
  • Code Duplication · Duplicated block (25 lines × 2 locations) integration/navigation-state-test.ts
  • Code Duplication · Duplicated block (25 lines × 2 locations) integration/single-fetch-test.ts
  • Code Duplication · Duplicated block (25 lines × 2 locations) packages/react-router/lib/dom/lib.tsx
  • Code Duplication · Duplicated block (24 lines × 2 locations) packages/react-router-dev/vite/rsc/virtual-route-modules.ts
  • Code Duplication · Duplicated block (23 lines × 2 locations) integration/navigation-state-test.ts
  • Code Duplication · Duplicated block (23 lines × 2 locations) integration/root-route-test.ts
  • Code Duplication · Duplicated block (23 lines × 2 locations) packages/react-router/lib/rsc/browser.tsx
  • Code Duplication · Duplicated block with local edits (22 matched lines × 2 locations) integration/link-test.ts
  • Code Duplication · Duplicated block (22 lines × 2 locations) integration/root-route-test.ts
  • Code Duplication · Duplicated block (22 lines × 2 locations) integration/vite-prerender-test.ts
  • Code Duplication · Duplicated block with local edits (22 matched lines × 2 locations) packages/create-react-router/copy-template.ts
  • Code Duplication · Duplicated block (22 lines × 2 locations) packages/react-router-dev/vite/remove-exports-test.ts
  • Code Duplication · Duplicated block (22 lines × 2 locations) packages/react-router/lib/router/router.ts
  • Code Duplication · Duplicated block (21 lines × 2 locations) integration/vite-basename-test.ts
  • Code Duplication · Duplicated block (21 lines × 2 locations) packages/react-router/lib/router/router.ts
  • Code Duplication · Duplicated block (20 lines × 2 locations) integration/rsc/rsc-test.ts
  • Code Duplication · Duplicated block (20 lines × 3 locations) integration/single-fetch-test.ts
  • Code Duplication · Duplicated block (20 lines × 2 locations) integration/vite-css-test.ts
  • Code Duplication · Duplicated block (19 lines × 4 locations) integration/prefetch-test.ts
  • Code Duplication · Duplicated block (19 lines × 6 locations) integration/vite-prerender-test.ts
  • Code Duplication · Duplicated block (19 lines × 2 locations) packages/react-router/lib/dom/lib.tsx
  • Code Duplication · Duplicated block (18 lines × 2 locations) integration/action-test.ts
  • Code Duplication · Duplicated block (18 lines × 2 locations) integration/defer-test.ts
  • Code Duplication · Duplicated block (18 lines × 3 locations) integration/navigation-state-test.ts
  • Code Duplication · Duplicated block (18 lines × 2 locations) integration/rsc/rsc-test.ts
  • Code Duplication · Duplicated block (18 lines × 3 locations) integration/split-route-modules-test.ts
  • Code Duplication · Duplicated block (18 lines × 4 locations) integration/vite-prerender-test.ts
  • Code Duplication · Duplicated block (18 lines × 2 locations) integration/vite-server-bundles-test.ts
  • Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (18 lines × 2 locations) packages/react-router/lib/dom/ssr/errorBoundaries.tsx
  • Code Duplication · Duplicated block (18 lines × 2 locations) packages/react-router/lib/dom/ssr/single-fetch.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) integration/helpers/create-fixture.ts
  • Code Duplication · Duplicated block (17 lines × 3 locations) integration/helpers/vite-7-template/app/root.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) integration/middleware-test.ts
  • Code Duplication · Duplicated block (17 lines × 3 locations) integration/single-fetch-test.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) integration/vite-prerender-test.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) integration/vite-prerender-test.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) integration/vite-prerender-test.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/react-router/lib/server-runtime/single-fetch.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) scripts/utils/packages.ts
  • Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) integration/catch-boundary-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) integration/defer-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) integration/error-boundary-v2-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) integration/error-boundary-v2-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) integration/fetcher-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) integration/form-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) integration/headers-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) integration/middleware-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) integration/rsc/rsc-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) integration/rsc/rsc-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) integration/vite-route-added-test.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/react-router-dev/invariant.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/react-router/lib/dom/lib.tsx
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/react-router/lib/dom/ssr/errorBoundaries.tsx
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/catch-boundary-data-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/catch-boundary-test.ts
  • Code Duplication · Duplicated block (15 lines × 6 locations) integration/client-data-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/deduped-route-modules-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/error-boundary-test.ts
  • Code Duplication · Duplicated block (15 lines × 6 locations) integration/error-sanitization-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/fog-of-war-test.ts
  • Code Duplication · Duplicated block (15 lines × 4 locations) integration/middleware-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/middleware-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/single-fetch-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/single-fetch-test.ts
  • Code Duplication · Duplicated block (15 lines × 4 locations) integration/single-fetch-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/single-fetch-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/single-fetch-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/single-fetch-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/vite-css-lazy-loading-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/vite-css-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) integration/vite-spa-mode-test.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/create-react-router/index.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/create-react-router/tsdown.config.ts
  • Code Duplication · Duplicated block (15 lines × 6 locations) packages/react-router-architect/tsdown.config.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/react-router/lib/dom/ssr/fog-of-war.ts
Rebuild cost: about €160,000 · Estimate
Cost to rebuild€53,000 to €270,000, for 888 to 2,816 hours of work, about 1.1 person-years for 1 to 3 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.7 at a score of 45. 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: 55,754 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: Watchdog prices 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
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
Raises the score by about 5 points · Medium effort · Access Controls
2
Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13).
Raises the score by about 3 points · Medium effort · Dependency Hygiene
3
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 1 point · Low effort · Supply-chain Provenance & Signing

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 €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Security and Compliance, at 39 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. Of all the actions in this report, it raises the score most for the work it takes: about 5 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 4.7 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 8% to 19% on every change. The history of the code shows how much it changes: about 40,060 lines over the last 90 days, which is about 162,466 lines a year. At that pace, the extra work comes to an estimated 33.8 to 203.1 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 Watchdog's 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 · 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 @react-router/architect architect @react-router/node node @react-router/architect->@react-router/node react-router react-router @react-router/architect->react-router @react-router/cloudflare cloudflare @react-router/cloudflare->react-router @react-router/dev dev @react-router/dev->@react-router/node @react-router/serve serve @react-router/dev->@react-router/serve @react-router/dev->react-router @react-router/express express @react-router/express->@react-router/node @react-router/express->react-router @react-router/fs-routes fs-routes @react-router/fs-routes->@react-router/dev @react-router/node->react-router @react-router/remix-routes-option-adapter remix-routes-option-adapter @react-router/remix-routes-option-adapter->@react-router/dev @react-router/serve->@react-router/express @react-router/serve->@react-router/node @react-router/serve->react-router create-react-router create-react-router integration integration integration->@react-router/dev integration->@react-router/express integration->@react-router/node integration->react-router integration-rsc-vite integration-rsc-vite integration-rsc-vite->react-router integration-rsc-vite-framework integration-rsc-vite-framework integration-rsc-vite-framework->@react-router/serve integration-rsc-vite-framework->react-router integration-vite-7-template integration-vite-7-template integration-vite-7-template->@react-router/express integration-vite-7-template->@react-router/node integration-vite-7-template->@react-router/serve integration-vite-7-template->react-router integration-vite-8-template integration-vite-8-template integration-vite-8-template->@react-router/express integration-vite-8-template->@react-router/node integration-vite-8-template->@react-router/serve integration-vite-8-template->react-router integration-vite-plugin-cloudflare-template integration-vite-plugin-cloudflare-template integration-vite-plugin-cloudflare-template->react-router react-router-scripts react-router-scripts react-router-scripts->react-router

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

203 modules, with 167 dependencies between them. 2 loops run through 4 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 163 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 integration.helpers.vite2 packages.create-react-router3 packages.create-react-router.prompts-prompt-base4 packages.react-router-architect.server5 packages.react-router-dev.cli6 packages.react-router-dev.config.config7 packages.react-router-dev.config.routes8 packages.react-router.lib.dom.ssr.routes9 packages.react-router.lib.router.history10 packages.react-router.lib.router.matcher11 packages.react-router.lib.rsc.html-stream.browser12 packages.react-router.lib.server-runtime.sessions13 integration.helpers.create-fixture14 integration.helpers.playwright-fixture15 packages16 packages.react-router-architect.sessions17 packages.react-router-cloudflare18 packages.react-router-cloudflare.sessions19 packages.react-router-dev.config20 packages.react-router-dev.vite21 packages.react-router.lib.router.utils22 integration23 integration.helpers24 packages.react-router.lib.dom.ssr.routeModules25 packages.react-router.lib.router.router26 packages.react-router.lib.context27 packages.react-router.lib.dom.dom28 packages.react-router.lib.dom.lib29 packages.react-router.lib.dom.ssr.routes-test-stub30 packages.react-router.lib.rsc31 packages.react-router.lib.components32 packages.react-router.lib.dom33 packages.react-router.lib.hooks34 packages.react-router.lib.router35 packages.react-router.lib36 packages.react-router.lib.dom.ssr.route-discovery37 packages.react-router.lib.dom.ssr.entry38 packages.react-router.lib.dom.ssr39 packages.react-router.lib.server-runtime.build40 packages.react-router.lib.server-runtime
1 integration.helpers.vite
2 packages.create-react-router
3 packages.create-react-router.prompts-prompt-base
4 packages.react-router-architect.server
5 packages.react-router-dev.cli
6 packages.react-router-dev.config.config
7 packages.react-router-dev.config.routes
8 packages.react-router.lib.dom.ssr.routes
9 packages.react-router.lib.router.history
10 packages.react-router.lib.router.matcher
11 packages.react-router.lib.rsc.html-stream.browser
12 packages.react-router.lib.server-runtime.sessions
13 integration.helpers.create-fixture1
14 integration.helpers.playwright-fixture1
15 packages1
16 packages.react-router-architect.sessions1
17 packages.react-router-cloudflare1
18 packages.react-router-cloudflare.sessions1
19 packages.react-router-dev.config24
20 packages.react-router-dev.vite114
21 packages.react-router.lib.router.utils11
22 integration1111
23 integration.helpers21
24 packages.react-router.lib.dom.ssr.routeModules12
25 packages.react-router.lib.router.router316114
26 packages.react-router.lib.context331
27 packages.react-router.lib.dom.dom21
28 packages.react-router.lib.dom.lib12322
29 packages.react-router.lib.dom.ssr.routes-test-stub112
30 packages.react-router.lib.rsc112
31 packages.react-router.lib.components11311
32 packages.react-router.lib.dom4235
33 packages.react-router.lib.hooks21
34 packages.react-router.lib.router122151230111
35 packages.react-router.lib141292
36 packages.react-router.lib.dom.ssr.route-discovery11
37 packages.react-router.lib.dom.ssr.entry111112
38 packages.react-router.lib.dom.ssr1131610126
39 packages.react-router.lib.server-runtime.build11
40 packages.react-router.lib.server-runtime1321413
Uses a module listed above itPart of a loopThe module itself
1 integration.helpers.vite2 packages.create-react-router3 packages.create-react-router.prompts-prompt-base4 packages.react-router-architect.server5 packages.react-router-dev.cli6 packages.react-router-dev.config.config7 packages.react-router-dev.config.routes8 packages.react-router.lib.dom.ssr.routes9 packages.react-router.lib.router.history10 packages.react-router.lib.router.matcher11 packages.react-router.lib.rsc.html-stream.browser12 packages.react-router.lib.server-runtime.sessions13 integration.helpers.create-fixture14 integration.helpers.playwright-fixture15 packages16 packages.react-router-architect.sessions17 packages.react-router-cloudflare18 packages.react-router-cloudflare.sessions19 packages.react-router-dev.config20 packages.react-router-dev.vite21 packages.react-router.lib.router.utils22 integration23 integration.helpers24 packages.react-router.lib.dom.ssr.routeModules25 packages.react-router.lib.router.router26 packages.react-router.lib.context27 packages.react-router.lib.dom.dom28 packages.react-router.lib.dom.lib29 packages.react-router.lib.dom.ssr.routes-test-stub30 packages.react-router.lib.rsc31 packages.react-router.lib.components32 packages.react-router.lib.dom33 packages.react-router.lib.hooks34 packages.react-router.lib.router35 packages.react-router.lib36 packages.react-router.lib.dom.ssr.route-discovery37 packages.react-router.lib.dom.ssr.entry38 packages.react-router.lib.dom.ssr39 packages.react-router.lib.server-runtime.build40 packages.react-router.lib.server-runtimeintegration.helpers.vite1packages.create-react-router2packages.create-react-router.prompts-prompt-base3packages.react-router-architect.server4packages.react-router-dev.cli5packages.react-router-dev.config.config6packages.react-router-dev.config.routes7packages.react-router.lib.dom.ssr.routes8packages.react-router.lib.router.history9packages.react-router.lib.router.matcher10packages.react-router.lib.rsc.html-stream.browser11packages.react-router.lib.server-runtime.sessions12integration.helpers.create-fixture13integration.helpers.playwright-fixture14packages15packages.react-router-architect.sessions16packages.react-router-cloudflare17packages.react-router-cloudflare.sessions18packages.react-router-dev.config19packages.react-router-dev.vite20packages.react-router.lib.router.utils21integration22integration.helpers23packages.react-router.lib.dom.ssr.routeModules24packages.react-router.lib.router.router25packages.react-router.lib.context26packages.react-router.lib.dom.dom27packages.react-router.lib.dom.lib28packages.react-router.lib.dom.ssr.routes-test-stub29packages.react-router.lib.rsc30packages.react-router.lib.components31packages.react-router.lib.dom32packages.react-router.lib.hooks33packages.react-router.lib.router34packages.react-router.lib35packages.react-router.lib.dom.ssr.route-discovery36packages.react-router.lib.dom.ssr.entry37packages.react-router.lib.dom.ssr38packages.react-router.lib.server-runtime.build39packages.react-router.lib.server-runtime40111111241141111112112316114331211232211211211311423521122151230111141292111111121131610126111321413+163 more modules (most-connected shown)

At a glance — Code Health · 40% · Weak · gated by D1, D2, R3, R7 ·

The Good
D3 · TypeScript God Classes 8.0 D17 · TypeScript Explicit Debt 9.9 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 7.4 R1 · React / TS Type Safety 10.0 R10 · React / TS Code Duplication 8.3 R2 · React / TS Cyclomatic Complexity 8.0 X1 · Repo Async correctness 7.9 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 7.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X5 · Repo Nullable reference types 9.5
The Ugly
D1 · TypeScript Cyclomatic Complexity 2.0 D2 · TypeScript Cognitive Complexity 2.0 R3 · React / TS Large Files 3.1 R7 · React / TS Dead Code 0.0 X3 · Repo Exception handling 4.8

At a glance — Architecture · 88% · Strong ·

The Good
D5 · TypeScript Coupling 10.0 D6 · TypeScript Cohesion (LCOM4) 10.0 D23 · TypeScript Boundary Type-Coupling 9.8 D26 · TypeScript Project Cohesion 8.9 D35 · TypeScript Change Coupling 10.0 AX10 · Repo Code composition 9.6 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 9.9 R11 · React / TS Import Boundaries 8.1 R9 · React / TS Circular Imports 8.0
The Bad
D7 · TypeScript Architectural Integrity 6.0

At a glance — Maturity · 70% · Adequate ·

The Good
D16 · TypeScript Bus Factor 8.4 D20 · TypeScript ADR Quality 8.6 D34 · TypeScript Knowledge Freshness 9.5 M2 · Repo Architecture documentation 10.0 M3 · Repo Folder & project structure 10.0
The Bad
D15 · TypeScript Churn × Complexity Hotspots 7.0 M4 · Repo Documentation accuracy 6.0
The Ugly
D25 · TypeScript ADR Conformance 0.0 M1 · Repo Documentation (README) 4.7

At a glance — Readiness · 43% · Weak · gated by R8, P3 ·

The Good
D9 · TypeScript Test Distribution 10.0 D10 · TypeScript Test Quality 9.3 D12 · TypeScript Dependency Hygiene 7.0 D13 · TypeScript REDACTED Scanning 10.0 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 R6 · React / TS Tooling 10.0
The Ugly
P2 · Repo Observability 4.5 P3 · Repo Security & performance tooling 3.0 R4 · React / TS Test Coverage 4.4 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 39% · Weak · gated by D29, D30, D36, C2 ·

The Good
D28 · TypeScript Secrets (history) 7.0 D31 · TypeScript IaC & Container Security 10.0 D37 · TypeScript Vulnerability-disclosure Policy 10.0 D43 · TypeScript Malicious Dependencies 10.0 D44 · TypeScript Platform End-of-Life 10.0 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0
The Ugly
D29 · TypeScript Static Analysis (SAST) 0.1 D30 · TypeScript Dependency Vulnerabilities 0.0 D36 · TypeScript Supply-chain Provenance & Signing 0.0 C2 · Repo Access Controls 0.0 X24 · Repo Document value interpolated into markup unescaped 4.6

At a glance — Accessibility · 70% · Strong ·

The Good
AC2 · Repo Forms & labels 10.0 AC5 · Repo ARIA correctness 10.0
The Bad
AC3 · Repo Page structure 5.9 AC6 · Repo Visual & motion safety 6.6 AC7 · Repo A11y enforcement 6.0

At a glance — Performance · 71% · Strong ·

The Good
PF1 · Repo Benchmark discipline 8.5
The Bad
PF3 · Repo Async & latency hygiene 6.0

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 — Injection90High / Critical
A03:2025 — Software Supply Chain Failures66High / Critical
A07:2025 — Authentication Failures4High / Critical

Roadmap

First, secure the application by implementing a global authentication guard with explicit public opt-outs and named role permissions. Next, address security and stability by resolving high-severity dependency vulnerabilities and removing deprecated packages. Finally, improve maintainability by deleting dead code and cleaning up unused or misclassified dependencies.

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

Do thisHelpsEffortDimension
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.+5.3 ptsMediumAccess Controls
Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13).+3.0 ptsMediumDependency Hygiene
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.+1.4 ptsLowSupply-chain Provenance & Signing
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with stub-test.tsx (2).+1.4 ptsLowTest Quality
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.+2.3 ptsMediumDead Code
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+2.1 ptsMediumDependency Hygiene
Resolve the 37 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (36), REDACTED.+2.0 ptsMediumDependency Vulnerabilities
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED.+1.0 ptsLowSecrets (history)

File quality

Per-file score 0–10 — a quality signature. Of 145 files carrying findings, judged against the Production bar: 4% slop · 59% mixed · 37% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
packages/react-router/__tests__/dom/stub-test.tsx4.1MixedTest Quality: No assertions (empty test): errors work
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED

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 — 116

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 — 729

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 — 221

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

Could not be resolved — 8

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

Watchdog 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. 83 of 83 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 83 dimensions across the health lenses
D1D2D3D5D6D7D9D10D12D13D14D15D16D17D20D23D25D26D28D29D30D31D34D35D36D37D43D44AC2AC3AC5AC6AC7AX10AX3AX4AX6C2GD1IC1M1M2M3M4P1P10P2P3P4P6PF1PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X5

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, 974 of 1066 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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
Watchdog 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
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement—◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a17883-2031-7dab-b6e7-5ca4b56d3c75.

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.

  • D11 Test Reliability — not measured this run — Watchdog 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 scored — the JavaScript/TypeScript suite (jest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
  • D19 Documentation Quality — not measured this run — Watchdog 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D19 Documentation Quality — not measured this run — Watchdog 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — Watchdog 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. D21's deterministic naming 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. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — Watchdog 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.
  • D24 Comment Value — not measured this run — Watchdog 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `integration/helpers/rsc-vite-framework/app/routes.ts`, `integration/helpers/rsc-vite/src/routes.ts`, `integration/helpers/vite-7-template/app/routes.ts`, `integration/helpers/vite-8-template/app/routes.ts`, `integration/helpers/vite-plugin-cloudflare-template/app/routes.ts`, … (+47 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.
  • AXR1 Runtime accessibility — not measured this run — Watchdog 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 did not expose a crawlable HTTP endpoint in time — no runtime evidence.
  • M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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). 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.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 344 further occurrence(s) are not listed individually; the score already reflects all 384.
  • R3 Large Files — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
  • R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 139 further occurrence(s) are not listed individually; the score already reflects all 179.
  • R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 103 further occurrence(s) are not listed individually; the score already reflects all 143.
  • X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
  • X4 Structured logging — not measured this run — Watchdog 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: 24 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
  • 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.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • 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 REDACTED Scanning: REDACTED 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.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • 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.
  • D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
  • 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.
  • 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.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • 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.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • 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.0 / 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.0 / 10 · rule-coverage 100% · ceiling Prevented

69 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was plugin.reactRouterVitePlugin at 224. A further 2 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 route-chunks.omitChunkedExports at 25 — they are counted neither in the figure above nor in this dimension's score.

router.createRouter::startNavigation (cyclomatic 47) · ×9packages/react-router/lib/router/router.ts:1943
plugin.reactRouterVitePlugin (cyclomatic 224)REDACTED:657
plugin.reactRouterRSCVitePlugin (cyclomatic 113)REDACTED:45
config.resolveConfig (cyclomatic 61)packages/react-router-dev/config/config.ts:473
server.ssr.routeRSCServerRequest (cyclomatic 50)packages/react-router/lib/rsc/server.ssr.tsx:90

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

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with plugin.reactRouterVitePlugin (cyclomatic 224). — Refactoring it lifts Cyclomatic Complexity from 2.0 to about 3.2/10.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

96 method(s) exceeded the cognitive complexity threshold of 15; the worst was plugin.reactRouterVitePlugin at 152.

router.createRouter::handleLoaders (cognitive 50) · ×10packages/react-router/lib/router/router.ts:2442
plugin.reactRouterVitePlugin (cognitive 152)REDACTED:657
plugin.reactRouterRSCVitePlugin (cognitive 111)REDACTED:45
config.resolveConfig (cognitive 83)packages/react-router-dev/config/config.ts:473
RouteDiscoveryRuntime.discover (cognitive 76)packages/react-router/lib/dom/ssr/route-discovery.ts:292

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

What to do

  1. Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with plugin.reactRouterVitePlugin (cognitive 152), plugin.reactRouterRSCVitePlugin (cognitive 111), config.resolveConfig (cognitive 83). — 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 5 together lifts Cognitive Complexity from 2.0 to about 3.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes8.0 / 10Strong✓ 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 8.0 / 10 · rule-coverage 100% · ceiling Prevented

39 god class(es) detected.

FunctionTooLong: router.createRouter · ×22packages/react-router/lib/router/router.ts:1045
FileTooLong: router/router.ts · ×16packages/react-router/lib/router/router.ts
ClassTooLong: ShouldRevalidateFunctionArgspackages/react-router/lib/router/utils.ts:386

What to do

  1. Resolve the 22 FunctionTooLong finding(s) in God Classes — start with router.ts (4), server.ts (3), REDACTED (2). — One of this dimension's main actionable groups (22 warning-level).
  2. Resolve the 16 FileTooLong finding(s) in God Classes — start with REDACTED (2), components.tsx (2), router.ts. — One of this dimension's main actionable groups (16 warning-level).
  3. Resolve the 1 ClassTooLong finding(s) in God Classes — start with utils.ts. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.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

17 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.

✓ 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 13 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D7 · Architectural Integrity6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

Classify ADR enforcement: useBlocker · ×22decisions/0001-use-blocker.md

What to do

  1. Resolve the 22 Classify ADR enforcement finding(s) in Architectural Integrity — start with 0001-use-blocker.md, 0001-use-npm-to-manage-npm-dependencies-for-deno-projects.md, 0002-do-not-clone-request.md. — One of this dimension's main actionable groups (22 recommendation-level).
  2. Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

3380 test methods: 2496 unit, 884 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 3380 `it`/`test` case(s) across 242 test file(s) declaring at least one; its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.3 / 10Adequategated by 2 critical findings✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Prevented

19 skipped, 124 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3378 tests.

No assertions (empty test): errors work · ×2packages/react-router/__tests__/dom/stub-test.tsx:208
No assertions: does not immediately call listeners · ×122packages/react-router/__tests__/router/browser-test.ts:70
Skipped test: (unnamed test) · ×19integration/browser-entry-test.ts:14
Fixed-sleep synchronisation: Vite / dev / route exports modified offscreenintegration/vite-route-exports-modified-offscreen-test.ts:59
Mock-dominated test: client-side redirects permit explicit external redirects to %s · ×4packages/react-router/__tests__/external-navigation-test.tsx:325

What to do

  1. Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with stub-test.tsx (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 122 No assertions finding(s) in Test Quality — start with typegen-test.ts (22), browser-test.ts (15), hash-test.ts (15). — One of this dimension's main actionable groups (122 warning-level).
  3. Resolve the 19 Skipped test finding(s) in Test Quality — start with client-data-test.ts (4), rsc-nojs-test.ts (4), rsc-test.ts (2). — One of this dimension's main actionable groups (19 warning-level).
  4. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D12 · Dependency Hygiene7.0 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

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

68 outdated direct production npm dependency(ies) of 101 graded, 4 pinning defect(s), across 34 REDACTED (18 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.

Floating npm dependency: @react-router/node · ×3
One package at two majors across the workspace: express
Deprecated: @babel/plugin-proposal-class-properties · ×13REDACTED:1977
Outdated (npm): @types/nodeintegration/helpers/rsc-vite-framework/package.json:18
Outdated (npm): @architect/functions · ×67

What to do

  1. Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13). — One of this dimension's main actionable groups (13 recommendation-level).
  2. Resolve the 3 Floating npm dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D13 · REDACTED 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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 101 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 101 production dependency(ies) this repository's committed lockfile resolves, across 18 product REDACTED manifest(s). Its 276 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots7.0 / 10Adequate✓ 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 7.0 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: packages/react-router/lib/router/router.ts (20×412=8240); REDACTED (4×224=896); REDACTED (4×113=452)

Hotspot: packages/react-router/lib/router/router.ts · ×14packages/react-router/lib/router/router.ts:1045

What to do

  1. Resolve the 14 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED (2), components.tsx (2), router.ts. — One of this dimension's main actionable groups (14 warning-level).

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

D16 · Bus Factor8.4 / 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 8.4 / 10 · rule-coverage 100% · ceiling Documented

15 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is scripts/changes/changes.ts. Counted over 96 of the 270 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.9 / 10Stronggated by 33 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.9 / 10 · rule-coverage 100% · ceiling Prevented

33 deducted task-comment markers across 55033 LoC (0.1/KLoC) → score 9.9. 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 · ×31scripts/docs.ts:721
FixmeComment · ×2packages/react-router/lib/rsc/browser.tsx:367

What to do

  1. Resolve the 31 TodoComment finding(s) in Explicit Debt — start with hooks.tsx (5), router.ts (4), context.ts (2). — One of this dimension's main actionable groups (31 warning-level).
  2. Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with browser.tsx, router.ts. — One of this dimension's main actionable groups (2 warning-level).
  3. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D20 · ADR Quality8.6 / 10Strong✓ Tool-verified

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

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

8 of 22 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question). How well each record argues its case is not measured.

ADR has no Consequences section · ×7decisions/0001-use-blocker.md:1detected by adr-integrity
ADR declares no statusdecisions/0016-plan-remove-agnostic-types.md:1detected by adr-integrity

What to do

  1. Resolve the 7 ADR has no Consequences section finding(s) in ADR Quality — start with 0001-use-blocker.md, 0003-data-strategy.md, 0005-remixing-react-router.md. — One of this dimension's main actionable groups (7 recommendation-level).
  2. Resolve the 1 ADR declares no status finding(s) in ADR Quality — start with 0016-plan-remove-agnostic-types.md. — 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-Coupling9.8 / 10Stronggated by 5 serious findings✓ 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 9.8 / 10 · rule-coverage 100% · ceiling Verified

5 domain type(s) cross context boundaries across 27 contexts.

Cross-context type ServerMode (react-router → integration) · ×3integration/helpers/create-fixture.ts:121
Cross-context type PackageManager (react-router-dev → create-react-router)packages/create-react-router/index.ts:187
Cross-context type State (react-router-fs-routes → react-router)packages/react-router/lib/router/history.ts:65

What to do

  1. Resolve the 3 Cross-context type ServerMode (react-router → integration) finding(s) in Boundary Type-Coupling — start with create-fixture.ts (3). — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 Cross-context type PackageManager (react-router-dev →… finding(s) in Boundary Type-Coupling — start with index.ts. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Cross-context type State (react-router-fs-routes → react-router) finding(s) in Boundary Type-Coupling — start with history.ts. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D25 · ADR Conformance0.0 / 10Critical✓ Tool-verified

What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.

Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.

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

1 of 1 checkable records are broken by the code (1 of 19 binding records state a rule in checkable form; prose decisions are unverifiable).

ADR not followed: Lazy Route Modules · ×2decisions/0002-lazy-route-modules.md:49detected by adr-prohibition

What to do

  1. Resolve the 2 ADR not followed finding(s) in ADR Conformance — start with 0002-lazy-route-modules.md (2). — One of this dimension's main actionable groups (2 recommendation-level).
  2. Enforce ADR Conformance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D26 · Project Cohesion8.9 / 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, LLM-independent.

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

1 of 19 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.

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

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

Method: REDACTED 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 7.0 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)0.1 / 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 0.1 / 10 · rule-coverage 100% · ceiling Documented

90 finding(s): 0 critical, 69 high, 13 medium, 8 low. 45 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 71 file(s) — `integration/action-test.ts` (line 15), `integration/catch-boundary-data-test.ts` (line 15), `integration/client-data-test.ts` (line 16), `integration/deduped-route-modules-test.ts` (line 11), `integration/helpers/create-fixture.ts` (line 119), … (+66 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 10 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

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

What to do

  1. Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
  2. Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
  3. No action in Static Analysis (SAST) — all 45 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (45 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ 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.

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

54 finding(s): 1 critical, 38 high, 11 medium, 4 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 37 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (36), REDACTED. — One of this dimension's main actionable groups (37 issue-level).
  2. Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 High vulnerability 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 Freshness9.5 / 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 9.5 / 10 · rule-coverage 100% · ceiling Documented

5 of 96 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 96 of the 270 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×5REDACTED:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling10.0 / 10Stronggated by 1 serious finding✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: data.ts↔server.ts 54%

Change coupling: data.ts ↔ server.tspackages/react-router/lib/server-runtime/data.ts:1

What to do

  1. Resolve the 1 Change coupling finding(s) in Change Coupling — start with data.ts. — One of this dimension's main actionable groups (1 warning-level).

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

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.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. Scored 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. SCORED, not informational.

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.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 41 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC3 · Page structure5.9 / 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>. (×11) — integration/helpers/rsc-vite/src/routes/root.tsx:5, playground/framework-express/app/root.tsx:5, playground/framework-spa/app/root.tsx:5, …
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component. — tutorials/address-book/app/root.tsx:51

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 safety6.6 / 10Adequate✓ Tool-verified

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.

  • `#search-spinner` moves (`animation: spin 1s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — tutorials/address-book/app/app.css:182
  • `#loading-splash-spinner` moves (`animation: spin 1s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — tutorials/address-book/app/app.css:435

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement6.0 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add jest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 115 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Accessibility linting is already configured — assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition9.6 / 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.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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.

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `Router` declares 19 required operations: `match`, `initialize`, `subscribe`, `enableScrollRestoration`, `navigate`, `navigate`, `fetch`, `revalidate`, `createHref`, `encodeLocation`, `getFetcher`, `resetFetcher`, `deleteFetcher`, `dispose`, `getBlocker`, `deleteBlocker`, `patchRoutes`, `_internalSetRoutes`, `_internalSetStateDoNotUseOrYouWillBreakYourApp`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 19 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/react-router/lib/router/router.ts:94

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
C2 · Access Controls0.0 / 10Critical✓ 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.

  • This repository serves requests — express() (packages/react-router-serve/cli.ts:192) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — packages/react-router-serve/cli.ts:192

What to do

  • Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
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 & stubs7.4 / 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.

  • `introStep` 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/create-react-router/index.ts:199
  • Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — packages/react-router/lib/types/route-data.ts:171
  • `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — scripts/changes/migrate-changesets.ts:123
  • `bumpVersion` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — scripts/experimental.ts:37
  • `publishPackages` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — scripts/experimental.ts:92
  • `commentOnIssue` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — scripts/release-comments.ts:155
  • `deleteContact` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — tutorials/address-book/app/data.ts:94
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×20) — integration/browser-entry-test.ts:14, integration/cli-test.ts:283, integration/client-data-test.ts:130, …
  • `serverLoad` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/react-router/lib/dom/ssr/route-discovery.ts:431

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)4.7 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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

  • The root README is 82 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.

What to do

  • Expand the README with getting-started, architecture overview and a project map.
  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 20 of 31 project(s) that lack one — worth up to 1.3 pts.
M2 · Architecture documentation10.0 / 10Exemplary✓ 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.

What to do

  • Grow the ADR log (currently 23) — reach 50 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

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

M4 · Documentation accuracy6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

  • docs/upgrading/component-routes.md names Vite 8, but the manifest declares `vite` ^7.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/upgrading/component-routes.md:32
  • docs/upgrading/router-provider.md names Vite 8, but the manifest declares `vite` ^7.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/upgrading/router-provider.md:30

What to do

  • Reconcile the README with reality: docs/upgrading/component-routes.md names Vite 8, but the manifest declares `vite` ^7.0.0; docs/upgrading/router-provider.md names Vite 8, but the manifest declares `vite` ^7.0.0.
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 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 · Observability4.5 / 10Weak✓ 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 1/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `integration`, `integration/helpers/rsc-vite`, `integration/helpers/rsc-vite-framework`, `packages/create-react-router`, `packages/react-router-serve`.
  • `packages/react-router-dev/invariant.ts` reports through `console.*` at line 13 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/react-router-dev/invariant.ts:13
  • `packages/react-router-dev/vite/dev.ts` 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/react-router-dev/vite/dev.ts:57
  • `REDACTED` reports through `console.*` at line 2149 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:2149
  • `REDACTED` reports through `console.*` at line 3161 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:3161
  • `packages/react-router-dev/vite/styles.ts` reports through `console.*` at line 80 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/react-router-dev/vite/styles.ts:80
  • `packages/react-router-dev/vite/styles.ts` reports through `console.*` at line 86 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/react-router-dev/vite/styles.ts:86
  • `packages/react-router-dev/vite/styles.ts` reports through `console.*` at line 93 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/react-router-dev/vite/styles.ts:93
  • `packages/react-router-dev/vite/styles.ts` reports through `console.*` at line 105 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/react-router-dev/vite/styles.ts:105
  • `packages/react-router-dev/config/config.ts` reports through `console.*` at line 939 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/react-router-dev/config/config.ts:939
  • `packages/react-router-dev/config/config.ts` reports through `console.*` at line 1111 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/react-router-dev/config/config.ts:1111
  • `packages/react-router-dev/config/defaults/entry.server.node.tsx` reports through `console.*` at line 80 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/react-router-dev/config/defaults/entry.server.node.tsx:80
  • `packages/react-router-dev/config/defaults/entry.server.web.tsx` 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/react-router-dev/config/defaults/entry.server.web.tsx:36

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.
  • Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
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 896938 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.

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.
  • Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • 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.

  • The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download 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.

PF1 · Benchmark discipline8.5 / 10Strong✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

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 the language 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.

  • `readFileSync` in `requestDocument` 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. (×4) — integration/helpers/create-fixture.ts:142, integration/helpers/create-fixture.ts:180, integration/helpers/create-fixture.ts:182, …
  • `existsSync` in `requestDocument` 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) — integration/helpers/create-fixture.ts:179, integration/helpers/create-fixture.ts:181
  • `readFileSync` in `requestResource` 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. — integration/helpers/create-fixture.ts:191
  • `readFileSync` in `requestSingleFetchData` 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. — integration/helpers/create-fixture.ts:195
  • `existsSync` in `app.get("*")` 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. (×4) — integration/helpers/create-fixture.ts:362, integration/helpers/create-fixture.ts:364, integration/helpers/create-fixture.ts:368, …
  • `fs.statSync` in `copyTemplateFromLocalFilePath` 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/create-react-router/copy-template.ts:133
  • `existsSync` in `copyAgentSkillsToAppDirStep` 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/create-react-router/index.ts:337, packages/create-react-router/index.ts:347
  • `existsSync` in `gitInitQuestionStep` 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/create-react-router/index.ts:496
  • `existsSync` in `gitInitStep` 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/create-react-router/index.ts:521
  • `existsSync` in `updatePackageJSON` 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/create-react-router/index.ts:703
  • `existsSync` in `generateEntry` 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/react-router-dev/cli/commands.ts:170
  • `existsSync` in `checkForEntry` 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/react-router-dev/cli/commands.ts:239
  • `fs.existsSync` in `resolveConfig` 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/react-router-dev/config/config.ts:490
  • `execSync` in `resolveEntryFiles` 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/react-router-dev/config/config.ts:1123
  • `readdirSync` in `generateSriManifest` 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. — REDACTED:914
  • `existsSync` in `callback to middlewares.use` 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. (×4) — REDACTED:1830, REDACTED:1839, REDACTED:436, …
  • `existsSync` in `handler` 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) — REDACTED:1905, REDACTED:1913
  • `existsSync` in `finalize` 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) — REDACTED:2830, REDACTED:2833
  • `existsSync` in `callback to viteManifestPaths.map` 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. — REDACTED:3546
  • `readFileSync` in `callback to flatMap` 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. — REDACTED:3788
  • `fs.existsSync` in `flatRoutes` 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/react-router-fs-routes/index.ts:40
  • `fs.existsSync` in `run` 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/react-router-serve/cli.ts:239
  • `fs.readFileSync` in `parseDocComments` 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. — scripts/docs.ts:541

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.3 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): 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. Deterministic.

  • 14 duplicated blocks under packages/react-router/lib/ have copies in at least two of the sibling directories dom, router, rsc, server-runtime — 12 of them are reported below, and 2 are 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 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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/react-router/lib/dom/ssr/errorBoundaries.tsx:10
  • 12 duplicated blocks under packages/ have copies in at least two of the sibling directories create-react-router, react-router, react-router-architect, react-router-cloudflare, react-router-dev, react-router-express (+4 more sibling(s) not listed) — 11 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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/react-router-fs-routes/manifest.ts:16
  • 6 duplicated blocks under the repository root have copies in at least two of the sibling directories integration, packages, scripts, tutorials — 3 of them are reported below, and 3 are 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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. — integration/helpers/rsc-vite/src/entry.ssr.tsx:8
  • packages/react-router/lib/rsc/server.ssr.tsx:172 · packages/react-router/lib/rsc/server.ssr.tsx:353 — the two spans are one implementation copied and then locally edited — 437 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/react-router/lib/rsc/server.ssr.tsx:172
  • integration/fog-of-war-test.ts:306 · integration/fog-of-war-test.ts:1234 — the two spans are one implementation copied and then locally edited — 534 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. — integration/fog-of-war-test.ts:306
  • packages/react-router/lib/dom/ssr/errorBoundaries.tsx:10 · packages/react-router/lib/rsc/errorBoundaries.tsx:7 — the two spans are one implementation copied and then locally edited — 344 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/react-router/lib/dom/ssr/errorBoundaries.tsx:10
  • packages/create-react-router/prompts-confirm.ts:48 · packages/create-react-router/prompts-multi-select.ts:54 — the two spans are one implementation copied and then locally edited — 402 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/create-react-router/prompts-confirm.ts:48
  • integration/prefetch-test.ts:264 · integration/prefetch-test.ts:367 — the two spans are one implementation copied and then locally edited — 293 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. — integration/prefetch-test.ts:264
  • integration/route-config-test.ts:68 · integration/route-config-test.ts:129 — 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. — integration/route-config-test.ts:68
  • packages/react-router-dev/vite/static/refresh-utils.mjs:98 · packages/react-router-dev/vite/static/rsc-refresh-utils.mjs:53 — the two spans are one implementation copied and then locally edited — 293 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/react-router-dev/vite/static/refresh-utils.mjs:98
  • packages/react-router/lib/server-runtime/single-fetch.ts:58 · packages/react-router/lib/server-runtime/single-fetch.ts:141 — the two spans are one implementation copied and then locally edited — 258 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/react-router/lib/server-runtime/single-fetch.ts:58
  • integration/split-route-modules-test.ts:320 · integration/split-route-modules-test.ts:427 — the two spans are one implementation copied and then locally edited — 361 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. — integration/split-route-modules-test.ts:320
  • packages/react-router-fs-routes/manifest.ts:16 · packages/react-router-remix-routes-option-adapter/manifest.ts:16 — 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/react-router-fs-routes/manifest.ts:16
  • packages/react-router/lib/dom/ssr/fog-of-war.ts:155 · packages/react-router/lib/rsc/browser.tsx:790 — 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/react-router/lib/dom/ssr/fog-of-war.ts:155
  • integration/error-sanitization-test.ts:265 · integration/error-sanitization-test.ts:428 — the two spans are one implementation copied and then locally edited — 293 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. — integration/error-sanitization-test.ts:265
  • packages/create-react-router/prompts-confirm.ts:77 · packages/create-react-router/prompts-select.ts:119 — 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/create-react-router/prompts-confirm.ts:77
  • integration/rsc-client-version-test.ts:141 · integration/rsc-client-version-test.ts:245 — the two spans are one implementation copied and then locally edited — 237 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. — integration/rsc-client-version-test.ts:141
  • packages/create-react-router/prompts-multi-select.ts:34 · packages/create-react-router/prompts-select.ts:41 — the two spans are one implementation copied and then locally edited — 230 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/create-react-router/prompts-multi-select.ts:34
  • integration/rsc-client-version-test.ts:203 · integration/rsc-client-version-test.ts:292 — the two spans are one implementation copied and then locally edited — 265 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. — integration/rsc-client-version-test.ts:203
  • packages/react-router/lib/router/matcher-route-pattern.ts:173 · packages/react-router/lib/router/utils.ts:1221 — the two spans are one implementation copied and then locally edited — 175 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/react-router/lib/router/matcher-route-pattern.ts:173
  • integration/fs-routes-test.ts:232 · integration/fs-routes-test.ts:287 — 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. — integration/fs-routes-test.ts:232
  • integration/fog-of-war-test.ts:987 · integration/fog-of-war-test.ts:1075 — 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. — integration/fog-of-war-test.ts:987
  • REDACTED:400 · REDACTED:438 — 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. — REDACTED:400
  • packages/react-router/lib/router/router.ts:2920 · packages/react-router/lib/router/router.ts:3292 — 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/react-router/lib/router/router.ts:2920
  • integration/vite-dot-server-test.ts:93 · integration/vite-dot-server-test.ts:158 — 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. — integration/vite-dot-server-test.ts:93
  • packages/react-router/lib/components.tsx:715 · REDACTED:195 — the two spans are one implementation copied and then locally edited — 155 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/react-router/lib/components.tsx:715
  • integration/error-boundary-test.ts:716 · integration/error-boundary-test.ts:787 — 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. — integration/error-boundary-test.ts:716
  • integration/middleware-test.ts:1830 · integration/middleware-test.ts:2746 — 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. — integration/middleware-test.ts:1830
  • integration/fog-of-war-test.ts:817 · integration/fog-of-war-test.ts:904 — 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. — integration/fog-of-war-test.ts:817
  • integration/middleware-test.ts:2867 · integration/middleware-test.ts:2904 — 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. — integration/middleware-test.ts:2867
  • integration/rsc/rsc-test.ts:243 · integration/rsc/rsc-test.ts:2398 — 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. — integration/rsc/rsc-test.ts:243
  • integration/vite-prerender-test.ts:1664 · integration/vite-prerender-test.ts:1817 — 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. — integration/vite-prerender-test.ts:1664
  • packages/react-router/lib/router/router.ts:2968 · packages/react-router/lib/router/router.ts:3330 — 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/react-router/lib/router/router.ts:2968
  • integration/root-route-test.ts:194 · integration/root-route-test.ts:322 — 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. — integration/root-route-test.ts:194
  • integration/rsc/rsc-nojs-test.ts:221 · integration/rsc/rsc-test.ts:1900 · integration/rsc/rsc-test.ts:1938 — the 3 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. — integration/rsc/rsc-nojs-test.ts:221
  • integration/vite-hmr-hdr-rsc-test.ts:159 · integration/vite-hmr-hdr-rsc-test.ts:224 — 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. — integration/vite-hmr-hdr-rsc-test.ts:159
  • REDACTED:1596 · REDACTED:379 — 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. — REDACTED:1596
  • packages/react-router/lib/components.tsx:938 · packages/react-router/lib/dom/lib.tsx:839 · packages/react-router/lib/dom/lib.tsx:930 · packages/react-router/lib/dom/lib.tsx:1017 — 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/react-router/lib/components.tsx:938
  • integration/deduped-route-modules-test.ts:209 · integration/deduped-route-modules-test.ts:253 — the two spans are one implementation copied and then locally edited — 194 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. — integration/deduped-route-modules-test.ts:209
  • integration/middleware-test.ts:438 · integration/middleware-test.ts:1122 — 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. — integration/middleware-test.ts:438

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 Boundaries8.1 / 10Strong✓ 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/react-router-architect/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead. — packages/react-router-architect/typedoc.mjs:1
  • packages/react-router-cloudflare/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead. — packages/react-router-cloudflare/typedoc.mjs:1
  • packages/react-router-dev/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead. — packages/react-router-dev/typedoc.mjs:1
  • packages/react-router-express/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead. — packages/react-router-express/typedoc.mjs:1
  • packages/react-router-fs-routes/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead. — packages/react-router-fs-routes/typedoc.mjs:1
  • packages/react-router-node/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead. — packages/react-router-node/typedoc.mjs:1
  • packages/react-router-remix-routes-option-adapter/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead. — packages/react-router-remix-routes-option-adapter/typedoc.mjs:1
  • packages/react-router-serve/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead. — packages/react-router-serve/typedoc.mjs:1
  • packages/react-router/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead. — packages/react-router/typedoc.mjs:1

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.

  • resolveConfig has cyclomatic complexity 65 and cognitive complexity 90; 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/react-router-dev/config/config.ts:473
  • startNavigation has cyclomatic complexity 48 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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/react-router/lib/router/router.ts:1943
  • requestHandler has cyclomatic complexity 40 and cognitive complexity 55; 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/react-router/lib/server-runtime/server.ts:83
  • handleLoaders has cyclomatic complexity 40 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/react-router/lib/router/router.ts:2442
  • discover has cyclomatic complexity 34 and cognitive complexity 74; 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/react-router/lib/dom/ssr/route-discovery.ts:292
  • handleFetcherAction has cyclomatic complexity 34 and cognitive complexity 48; 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/react-router/lib/router/router.ts:2888
  • flatRoutesUniversal has cyclomatic complexity 32 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. — REDACTED:127
  • createRouter has cyclomatic complexity 32 and cognitive complexity 45; 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/react-router/lib/router/router.ts:1045
  • navigate has cyclomatic complexity 30 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/react-router/lib/router/router.ts:1699
  • routeRSCServerRequest has cyclomatic complexity 29 and cognitive complexity 41; 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/react-router/lib/rsc/server.ssr.tsx:90
  • completeNavigation has cyclomatic complexity 29 and cognitive complexity 30; 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/react-router/lib/router/router.ts:1542
  • normalizeNavigateOptions has cyclomatic complexity 27 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/react-router/lib/router/router.ts:5394
  • action has cyclomatic complexity 27 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/create-react-router/utils.ts:253
  • main has cyclomatic complexity 26 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. — scripts/changes/publish.ts:182
  • useRoutesImpl has cyclomatic complexity 26 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. — packages/react-router/lib/hooks.tsx:765
  • NavLinkWithRef has cyclomatic complexity 26 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. — packages/react-router/lib/dom/lib.tsx:1631
  • handleAction has cyclomatic complexity 24 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/react-router/lib/router/router.ts:2244
  • startRedirectNavigation has cyclomatic complexity 24 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. — packages/react-router/lib/router/router.ts:3428
  • validateDestructuredExports has cyclomatic complexity 23 and cognitive complexity 42; 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/react-router-dev/vite/remove-exports.ts:161
  • submit has cyclomatic complexity 23 and cognitive complexity 42; 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/react-router/lib/router/router.ts:4869

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files3.1 / 10Weak✓ 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/react-router/lib/router/router.ts has 7215 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/react-router/lib/router/router.ts:1
  • integration/single-fetch-test.ts has 4194 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/single-fetch-test.ts:1
  • REDACTED has 3595 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/react-router/lib/dom/lib.tsx has 3235 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/react-router/lib/dom/lib.tsx:1
  • integration/vite-prerender-test.ts has 2931 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/vite-prerender-test.ts:1
  • integration/middleware-test.ts has 2715 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/middleware-test.ts:1
  • integration/rsc/rsc-test.ts has 2483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/rsc/rsc-test.ts:1
  • packages/react-router/lib/router/utils.ts has 2272 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/react-router/lib/router/utils.ts:1
  • packages/react-router/lib/hooks.tsx has 2069 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/react-router/lib/hooks.tsx:1
  • packages/react-router/lib/components.tsx has 1946 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/react-router/lib/components.tsx:1
  • integration/fog-of-war-test.ts has 1774 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/fog-of-war-test.ts:1
  • integration/client-data-test.ts has 1633 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/client-data-test.ts:1
  • packages/react-router-dev/vite/route-chunks-test.ts has 1569 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/react-router-dev/vite/route-chunks-test.ts:1
  • packages/react-router/lib/rsc/server.rsc.ts has 1430 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/react-router/lib/rsc/server.rsc.ts:1
  • integration/vite-spa-mode-test.ts has 1239 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/vite-spa-mode-test.ts:1
  • packages/react-router-dev/config/config.ts has 1156 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/react-router-dev/config/config.ts:1
  • packages/react-router/lib/rsc/browser.tsx has 1081 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/react-router/lib/rsc/browser.tsx:1
  • integration/form-test.ts has 1011 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/form-test.ts:1
  • packages/react-router/lib/dom/ssr/components.tsx has 955 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/react-router/lib/dom/ssr/components.tsx:1
  • REDACTED has 913 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
  • integration/error-boundary-test.ts has 903 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/error-boundary-test.ts:1
  • integration/browser-entry-test.ts has 890 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/browser-entry-test.ts:1
  • packages/react-router-dev/vite/route-chunks.ts has 872 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/react-router-dev/vite/route-chunks.ts:1
  • packages/react-router-dev/vite/remove-exports-test.ts has 824 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/react-router-dev/vite/remove-exports-test.ts:1
  • integration/typegen-test.ts 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. — integration/typegen-test.ts:1
  • packages/react-router/lib/dom/ssr/single-fetch.tsx has 786 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/react-router/lib/dom/ssr/single-fetch.tsx:1
  • packages/create-react-router/index.ts has 771 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/create-react-router/index.ts:1
  • integration/vite-api-only-test.ts has 754 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/vite-api-only-test.ts:1
  • packages/react-router/lib/router/history.ts has 728 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/react-router/lib/router/history.ts:1
  • packages/react-router/lib/server-runtime/server.ts has 707 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/react-router/lib/server-runtime/server.ts:1
  • packages/react-router/lib/router/instrumentation.ts has 685 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/react-router/lib/router/instrumentation.ts:1
  • integration/vite-basename-test.ts has 683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/vite-basename-test.ts:1
  • scripts/docs.ts has 682 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/docs.ts:1
  • packages/react-router/lib/dom/ssr/route-discovery.ts has 655 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/react-router/lib/dom/ssr/route-discovery.ts:1
  • integration/prefetch-test.ts has 645 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/prefetch-test.ts:1
  • integration/error-sanitization-test.ts has 644 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/error-sanitization-test.ts:1
  • packages/react-router/lib/dom/ssr/routes.tsx has 643 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/react-router/lib/dom/ssr/routes.tsx:1
  • integration/defer-test.ts has 627 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/defer-test.ts:1
  • packages/react-router/lib/rsc/server.ssr.tsx has 613 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/react-router/lib/rsc/server.ssr.tsx:1
  • integration/link-test.ts has 610 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/link-test.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage4.4 / 10Weak✓ 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.

  • 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. (×40) — integration/single-fetch-test.ts:1, integration/vite-prerender-test.ts:1, integration/middleware-test.ts: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 REDACTED 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: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code0.0 / 10Critical✓ 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.

  • 11 file(s) (~204 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: integration/helpers/rsc-vite/server.js imports './dist/rsc/index.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — integration/helpers/rsc-vite
  • 5 file(s) (~69 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: integration/helpers/rsc-vite-framework/start.js imports './build/server/index.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — integration/helpers/rsc-vite-framework
  • Unreachable from the 120 application, 46 tooling and 194 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (120 application, 46 tooling, 194 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 (×37) — integration/single-fetch-test.ts, integration/vite-prerender-test.ts, integration/middleware-test.ts, …

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 Hygiene0.0 / 10Critical✓ 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.

  • Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — jest/setup-globals.js:1
  • Declared in integration/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.
  • Declared in integration/helpers/vite-7-template/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.
  • Declared in integration/helpers/vite-8-template/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. — integration/helpers/create-fixture.ts:11

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports8.0 / 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/react-router/lib/dom/ssr/components.tsx → packages/react-router/lib/dom/ssr/fog-of-war.ts → packages/react-router/lib/dom/ssr/routes.tsx → packages/react-router/lib/dom/ssr/errorBoundaries.tsx → packages/react-router/lib/dom/ssr/components.tsx (one verified cycle inside a mutually-dependent group of 5 files) — packages/react-router/lib/dom/ssr/components.tsx:37

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. The server controls — HTTPS enforcement, HSTS, cookie flags, 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.

  • `app.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.) (×4) — integration/helpers/rsc-vite-framework/start.js:17, integration/helpers/rsc-vite/server.js:24, packages/react-router-serve/cli.ts:265, …

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 correctness7.9 / 10Strong✓ Tool-verified

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.

  • The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. — integration/helpers/stream.ts:15

What to do

  • `async` Promise executor
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.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. 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 document10.0 / 10Exemplary○ Nothing flagged

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.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation7.0 / 10Strong✓ 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 2/4 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.
  • `instrumentedFetch` 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/react-router/lib/router/instrumentation.ts:472
  • `downloadAndExtractTarball` 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/create-react-router/copy-template.ts:206

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.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped4.6 / 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.

  • `criticalCss` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. — packages/react-router/lib/dom/ssr/components.tsx:278
  • `contextScript` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. — packages/react-router/lib/dom/ssr/components.tsx:953
  • `routeModulesScript` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. — packages/react-router/lib/dom/ssr/components.tsx:959
  • `JSON.stringify({integrity:sri,})` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. — packages/react-router/lib/dom/ssr/components.tsx:1001

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.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. 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 handling4.8 / 10Weak✓ 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. (×30) — scripts/utils/git.ts:74, scripts/utils/packages.ts:57, scripts/utils/packages.ts:147, …
  • `.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. (×10) — packages/react-router-node/stream.ts:38, packages/react-router-node/stream.ts:145, packages/react-router-node/stream.ts:219, …

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 types9.5 / 10Exemplary✓ 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.

  • ~1.3 `!` null assertions per 1k TypeScript source lines — 79 assertion(s) across the 59709 source line(s) of the 217 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/react-router/lib/router/router.ts (15), packages/react-router/lib/dom-export/hydrated-router.tsx (6), REDACTED (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

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 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 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
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
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
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 45 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.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.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 Health40%Weak — gated by D1, D2, R3, R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture88%StrongStrongest area.
Maturity70%AdequateAcceptable, with room to improve.
Readiness43%Weak — gated by R8, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security39%Weak — gated by D29, D30, D36, C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility70%StrongSolid.
Performance71%StrongSolid.
Unscored — 2 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.

  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 6 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 — 46 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.
  • 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
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • 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 did not expose a crawlable HTTP endpoint in time — no runtime evidence 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 — No tests discovered
  • 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.
  • D19 Documentation Quality — D19 reads .NET projects as units only; 19 folder(s) declared by REDACTED were not judged for an overview, an example or the map.
  • D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript not measured.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
  • D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 52 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
  • 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.
  • D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (FAIL packages/react-router/__tests__/dom/data-browser-router-test.tsx), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
  • 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
  • P12 CI test-gate honesty — 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'.
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: packages/react-router-serve/cli.ts:192 (express()))
  • 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • 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.
  • 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.
  • 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.
  • 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 — 116 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 20 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×37
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 12 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D10 · Test Quality · No assertions (empty test) · ×2
  • No assertions (empty test): errors work packages/react-router/__tests__/dom/stub-test.tsx:208 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): errors work with prop packages/react-router/__tests__/dom/stub-test.tsx:230 — Test method has an empty body — it asserts nothing and exercises no code.
D28 · Secrets (history) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · Document without a <title> · ×1
  • Document without a <title> tutorials/address-book/app/root.tsx:51 — A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
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
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import '@jest/globals' · ×1
  • Unlisted import '@jest/globals' jest/setup-globals.js:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (4 files) · ×1
  • Import cycle (4 files) packages/react-router/lib/dom/ssr/components.tsx:37 — packages/react-router/lib/dom/ssr/components.tsx → packages/react-router/lib/dom/ssr/fog-of-war.ts → packages/react-router/lib/dom/ssr/routes.tsx → packages/react-router/lib/dom/ssr/errorBoundaries.tsx → packages/react-router/lib/dom/ssr/components.tsx (one verified cycle inside a mutually-dependent group of 5 files)
Serious — 729 finding(s)
D10 · Test Quality · No assertions · ×122
  • No assertions: does not immediately call listeners packages/react-router/__tests__/router/browser-test.ts:70 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls listeners only for POP actions packages/react-router/__tests__/router/browser-test.ts:74 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: has the "default" key packages/react-router/__tests__/router/browser-test.ts:80 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the new location packages/react-router/__tests__/router/browser-test.ts:86 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the new location packages/react-router/__tests__/router/browser-test.ts:92 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the new location packages/react-router/__tests__/router/browser-test.ts:98 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: re-throws when using non-serializable state packages/react-router/__tests__/router/browser-test.ts:102 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: reuses the current location pathname packages/react-router/__tests__/router/browser-test.ts:108 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: normalizes the pathname relative to the current location packages/react-router/__tests__/router/browser-test.ts:114 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the new location packages/react-router/__tests__/router/browser-test.ts:120 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the new location packages/react-router/__tests__/router/browser-test.ts:126 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the new location packages/react-router/__tests__/router/browser-test.ts:132 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: produces different location objects packages/react-router/__tests__/router/browser-test.ts:138 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the previous location packages/react-router/__tests__/router/browser-test.ts:144 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the next location packages/react-router/__tests__/router/browser-test.ts:150 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: does not immediately call listeners packages/react-router/__tests__/router/hash-test.ts:85 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls listeners only for POP actions packages/react-router/__tests__/router/hash-test.ts:89 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: has the "default" key packages/react-router/__tests__/router/hash-test.ts:95 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the new location packages/react-router/__tests__/router/hash-test.ts:101 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the new location packages/react-router/__tests__/router/hash-test.ts:107 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the new location packages/react-router/__tests__/router/hash-test.ts:113 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: re-throws when using non-serializable state packages/react-router/__tests__/router/hash-test.ts:117 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: reuses the current location pathname packages/react-router/__tests__/router/hash-test.ts:123 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: issues a warning packages/react-router/__tests__/router/hash-test.ts:129 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: calls change listeners with the new location packages/react-router/__tests__/router/hash-test.ts:135 — 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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.
  • + 97 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file integration/single-fetch-test.ts: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 integration/vite-prerender-test.ts: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 integration/middleware-test.ts: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 integration/rsc/rsc-test.ts: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 integration/fog-of-war-test.ts: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 integration/client-data-test.ts: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/react-router-dev/vite/route-chunks-test.ts: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 integration/vite-spa-mode-test.ts: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 integration/form-test.ts: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 integration/error-boundary-test.ts: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 integration/browser-entry-test.ts: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 integration/typegen-test.ts: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/react-router-dev/vite/remove-exports-test.ts: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 integration/vite-api-only-test.ts: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 scripts/docs.ts: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 integration/vite-basename-test.ts: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 integration/prefetch-test.ts: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 integration/error-sanitization-test.ts: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 integration/defer-test.ts: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 integration/link-test.ts: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 integration/vite-server-bundles-test.ts: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 integration/vite-dev-test.ts: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 integration/split-route-modules-test.ts: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 REDACTED: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 integration/fetcher-test.ts: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.
  • + 15 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×40
  • Swallowed exception (empty catch) scripts/utils/git.ts:74 — 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) scripts/utils/packages.ts:57 — 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) scripts/utils/packages.ts:147 — 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/react-router-node/stream.ts:38 — `.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/react-router-node/stream.ts:39 — 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/react-router-node/stream.ts:48 — 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/react-router-node/stream.ts:145 — `.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/react-router-node/stream.ts:219 — `.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/react-router-node/stream.ts:220 — 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) REDACTED:1946 — 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/react-router-cloudflare/worker.ts:100 — 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/react-router/lib/errors.ts: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/react-router/lib/errors.ts:94 — 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/react-router/lib/components.tsx:1798 — `.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/react-router/lib/server-runtime/dev.ts:28 — 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/react-router/lib/server-runtime/server.ts:125 — 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/react-router/lib/server-runtime/server.ts:601 — 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/react-router/lib/rsc/browser.tsx:241 — `.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/react-router/lib/rsc/server.ssr.tsx:458 — 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/react-router/lib/rsc/html-stream/server.ts:41 — `.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/react-router/lib/rsc/html-stream/server.ts:43 — `.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/react-router/lib/router/history.ts:541 — 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/react-router/lib/router/instrumentation.ts:549 — 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/react-router/lib/router/navigation.ts:50 — 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/react-router/lib/router/router.ts:6246 — `.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.
  • + 15 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×36
  • Sync-over-async blocking integration/helpers/create-fixture.ts:142 — `readFileSync` in `requestDocument` 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 integration/helpers/create-fixture.ts:179 — `existsSync` in `requestDocument` 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 integration/helpers/create-fixture.ts:180 — `readFileSync` in `requestDocument` 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 integration/helpers/create-fixture.ts:181 — `existsSync` in `requestDocument` 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 integration/helpers/create-fixture.ts:182 — `readFileSync` in `requestDocument` 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 integration/helpers/create-fixture.ts:183 — `readFileSync` in `requestDocument` 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 integration/helpers/create-fixture.ts:191 — `readFileSync` in `requestResource` 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 integration/helpers/create-fixture.ts:195 — `readFileSync` in `requestSingleFetchData` 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 integration/helpers/create-fixture.ts:362 — `existsSync` in `app.get("*")` 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 integration/helpers/create-fixture.ts:364 — `existsSync` in `app.get("*")` 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 integration/helpers/create-fixture.ts:368 — `existsSync` in `app.get("*")` 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 integration/helpers/create-fixture.ts:429 — `existsSync` in `app.get("*")` 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/create-react-router/copy-template.ts:133 — `fs.statSync` in `copyTemplateFromLocalFilePath` 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/create-react-router/index.ts:337 — `existsSync` in `copyAgentSkillsToAppDirStep` 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/create-react-router/index.ts:347 — `existsSync` in `copyAgentSkillsToAppDirStep` 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/create-react-router/index.ts:496 — `existsSync` in `gitInitQuestionStep` 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/create-react-router/index.ts:521 — `existsSync` in `gitInitStep` 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/create-react-router/index.ts:703 — `existsSync` in `updatePackageJSON` 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/react-router-dev/cli/commands.ts:170 — `existsSync` in `generateEntry` 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/react-router-dev/cli/commands.ts:239 — `existsSync` in `checkForEntry` 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/react-router-dev/config/config.ts:490 — `fs.existsSync` in `resolveConfig` 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/react-router-dev/config/config.ts:1123 — `execSync` in `resolveEntryFiles` 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 REDACTED:914 — `readdirSync` in `generateSriManifest` 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 REDACTED:1830 — `existsSync` in `callback to middlewares.use` 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 REDACTED:1839 — `existsSync` in `callback to middlewares.use` 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.
  • + 11 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×31
  • TodoComment scripts/docs.ts:721 — // TODO: Handle variable statements for forwardRef components — 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/react-router-dev/vite/styles.ts:108 — // static and dynamic imports? TODO investigate, submit fix — 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/react-router-dev/cli/run.ts:220 — // TODO: simplify getting started guide — 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/react-router/lib/context.ts:84 — // TODO: (v9) Change the useFetcher data from `any` to `unknown` — 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/react-router/lib/context.ts:148 — // TODO: Re-introduce a singular `FutureConfig` once we land our first — 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/react-router/lib/components.tsx:1019 — // TODO: This error is probably because they somehow have 2 versions of — 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/react-router/lib/hooks.tsx:103 — // TODO: This error is probably because they somehow have 2 versions of the — 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/react-router/lib/hooks.tsx:167 — // TODO: This error is probably because they somehow have 2 versions of the — 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/react-router/lib/hooks.tsx:203 — // TODO: This error is probably because they somehow have 2 versions of the — 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/react-router/lib/hooks.tsx:384 — // TODO: This error is probably because they somehow have 2 versions of the — 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/react-router/lib/hooks.tsx:778 — // TODO: This error is probably because they somehow have 2 versions of the — 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/react-router/lib/server-runtime/single-fetch.ts:320 — // TODO(v3): Consider removing or making this official public API — 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/react-router/lib/rsc/server.rsc.ts:498 — // TODO: This isn't ideal but we can't do it through `lazy()` in the router, — 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/react-router/lib/rsc/server.rsc.ts:1303 — // TODO: DRY this up once it's fully fleshed out — 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/react-router/lib/rsc/browser.tsx:526 — // TODO: Confirm that it's correct for us to have multiple rendered routes — 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/react-router/lib/router/history.ts:54 — // TODO: (v9) Change the Location generic default from `any` to `unknown` and — 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/react-router/lib/router/history.ts:583 — // TODO: This could be cleaned up. push/replace should probably just take — 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/react-router/lib/router/router.ts:364 — // TODO: (v9) should we consider renaming this `navigationType` to align with — 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/react-router/lib/router/router.ts:2755 — // TODO: (v9) change `RouteData` to use `unknown` instead of `any` — 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/react-router/lib/router/router.ts:4230 — // TODO: Remove setRoutes, it's temporary to avoid dealing with — 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/react-router/lib/router/router.ts:7650 — // TODO: This should probably check against GET and HEAD, and consider any other — 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/react-router/lib/router/utils.ts:1510 — // TODO: Can this as be avoided? — 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/react-router/lib/dom/global.ts:20 — // TODO: (v9) Can this go away in favor of "just use remix"? — 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/react-router/lib/dom/lib.tsx:2830 — // TODO: (v9) Change the useFetcher generic default from `any` to `unknown` — 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/react-router/lib/dom/ssr/links.ts:211 — // TODO: this is really similar to stuff in router.ts, maybe somebody smarter — 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.
  • + 6 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×22
  • FunctionTooLong: router.createRouter packages/react-router/lib/router/router.ts:1045 — FunctionTooLong — createRouter runs 1968 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1868 over it, 19.68× 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: router.createStaticHandler packages/react-router/lib/router/router.ts:4292 — FunctionTooLong — createStaticHandler runs 631 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 531 over it, 6.31× 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: plugin.reactRouterRSCVitePlugin REDACTED:45 — FunctionTooLong — reactRouterRSCVitePlugin runs 569 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 469 over it, 5.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: components.RouterProvider packages/react-router/lib/components.tsx:413 — FunctionTooLong — RouterProvider runs 262 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 162 over it, 2.62× 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: virtual-route-modules.virtualRouteModulesPlugin packages/react-router-dev/vite/rsc/virtual-route-modules.ts:86 — FunctionTooLong — virtualRouteModulesPlugin runs 261 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 161 over it, 2.61× 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: server.ssr.routeRSCServerRequest packages/react-router/lib/rsc/server.ssr.tsx:90 — FunctionTooLong — routeRSCServerRequest runs 245 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 145 over it, 2.45× 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: routes.createClientRoutes packages/react-router/lib/dom/ssr/routes.tsx:226 — FunctionTooLong — createClientRoutes 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: router.getMatchesToLoad packages/react-router/lib/router/router.ts:5538 — FunctionTooLong — getMatchesToLoad runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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: server.derive packages/react-router/lib/server-runtime/server.ts:59 — FunctionTooLong — derive runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× 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: components.Scripts packages/react-router/lib/dom/ssr/components.tsx:806 — FunctionTooLong — Scripts runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: server.derive.requestHandler packages/react-router/lib/server-runtime/server.ts:83 — FunctionTooLong — derive.requestHandler runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× 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: browser.createRouterFromPayload packages/react-router/lib/rsc/browser.tsx:254 — FunctionTooLong — createRouterFromPayload runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: instrumentation.getRouteInstrumentationUpdates packages/react-router/lib/router/instrumentation.ts:195 — FunctionTooLong — getRouteInstrumentationUpdates runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: router.createStaticHandler.submit packages/react-router/lib/router/router.ts:4869 — FunctionTooLong — createStaticHandler.submit runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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 REDACTED:205 — FunctionTooLong — prerender runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: plugin.getEnvironmentOptionsResolvers REDACTED:3649 — FunctionTooLong — getEnvironmentOptionsResolvers runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: server.handleDocumentRequest packages/react-router/lib/server-runtime/server.ts:465 — FunctionTooLong — handleDocumentRequest runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: browser.RSCHydratedRouter packages/react-router/lib/rsc/browser.tsx:724 — FunctionTooLong — RSCHydratedRouter runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× 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: hydrated-router.createHydratedRouter packages/react-router/lib/dom-export/hydrated-router.tsx:86 — FunctionTooLong — createHydratedRouter 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: server.rsc.matchRSCServerRequest packages/react-router/lib/rsc/server.rsc.ts:404 — FunctionTooLong — matchRSCServerRequest 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: virtual-route-config.createVirtualRouteConfig packages/react-router-dev/vite/rsc/virtual-route-config.ts:6 — FunctionTooLong — createVirtualRouteConfig runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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: publish.main scripts/changes/publish.ts:182 — FunctionTooLong — main runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
D10 · Test Quality · Skipped test · ×19
  • Skipped test: (unnamed test) integration/browser-entry-test.ts:14 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/cli-test.ts:283 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/client-data-test.ts:130 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/client-data-test.ts:135 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/client-data-test.ts:1199 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/client-data-test.ts:1480 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/deduped-route-modules-test.ts:248 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/link-test.ts:612 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/manifest-reload-recovery-test.ts:172 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/route-config-test.ts:21 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/vite-basename-test.ts:527 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/vite-hmr-hdr-test.ts:86 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/vite-route-added-test.ts:42 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/rsc/rsc-nojs-test.ts:176 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/rsc/rsc-nojs-test.ts:201 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/rsc/rsc-nojs-test.ts:236 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/rsc/rsc-nojs-test.ts:270 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/rsc/rsc-test.ts:1915 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) integration/rsc/rsc-test.ts:1953 — Skipped — switched off by test.skip
D3 · God Classes · FileTooLong · ×16
  • FileTooLong: router/router.ts packages/react-router/lib/router/router.ts — FileTooLong — 4770 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4270 over it, 9.54× 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: REDACTED REDACTED — FileTooLong — 2610 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2110 over it, 5.22× 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: router/utils.ts packages/react-router/lib/router/utils.ts — FileTooLong — 1105 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: ShouldRevalidateFunctionArgs (386-2201). The bar is 500 significant lines; this is 605 over it, 2.21× 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.
  • FileTooLong: rsc/server.rsc.ts packages/react-router/lib/rsc/server.rsc.ts — FileTooLong — 1068 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 568 over it, 2.14× 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: dom/lib.tsx packages/react-router/lib/dom/lib.tsx — FileTooLong — 1023 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 523 over it, 2.05× 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: lib/components.tsx packages/react-router/lib/components.tsx — FileTooLong — 874 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 374 over it, 1.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: lib/hooks.tsx packages/react-router/lib/hooks.tsx — FileTooLong — 865 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 365 over it, 1.73× 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: config/config.ts packages/react-router-dev/config/config.ts — FileTooLong — 750 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 250 over it, 1.50× 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: rsc/browser.tsx packages/react-router/lib/rsc/browser.tsx — FileTooLong — 726 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 226 over it, 1.45× 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: REDACTED REDACTED — FileTooLong — 670 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: reactRouterRSCVitePlugin (45-889). The bar is 500 significant lines; this is 170 over it, 1.34× 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.
  • FileTooLong: create-react-router/index.ts packages/create-react-router/index.ts — FileTooLong — 623 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 123 over it, 1.25× 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: ssr/components.tsx packages/react-router/lib/dom/ssr/components.tsx — FileTooLong — 608 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 108 over it, 1.22× 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: vite/route-chunks.ts packages/react-router-dev/vite/route-chunks.ts — FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 53 over it, 1.11× 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-runtime/server.ts packages/react-router/lib/server-runtime/server.ts — FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 22 over it, 1.04× 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: router/instrumentation.ts packages/react-router/lib/router/instrumentation.ts — FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 19 over it, 1.04× 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: ssr/single-fetch.tsx packages/react-router/lib/dom/ssr/single-fetch.tsx — FileTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 11 over it, 1.02× 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×14
  • Hotspot: packages/react-router/lib/router/router.ts packages/react-router/lib/router/router.ts:1045 — packages/react-router/lib/router/router.ts changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 412 in router.createRouter at line 1045. 7 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router/lib/router/router.ts`: 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:657 — REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 224 in plugin.reactRouterVitePlugin at line 657. 1 of those changes was a fix/bug commit, and the other 3 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04: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: REDACTED REDACTED:45 — REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 113 in plugin.reactRouterRSCVitePlugin at line 45. 1 of those changes was a fix/bug commit, and the other 3 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04: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/react-router/lib/components.tsx packages/react-router/lib/components.tsx:413 — packages/react-router/lib/components.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in components.RouterProvider at line 413. 2 of those changes were fix/bug commits, and the other 5 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router/lib/components.tsx`: 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/react-router/lib/hooks.tsx packages/react-router/lib/hooks.tsx:765 — packages/react-router/lib/hooks.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in hooks.useRoutesImpl at line 765. 1 of those changes was a fix/bug commit, and the other 6 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router/lib/hooks.tsx`: 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/react-router/lib/rsc/server.ssr.tsx packages/react-router/lib/rsc/server.ssr.tsx:90 — packages/react-router/lib/rsc/server.ssr.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in server.ssr.routeRSCServerRequest at line 90. 1 of those changes was a fix/bug commit, and the other 3 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router/lib/rsc/server.ssr.tsx`: 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/react-router/lib/server-runtime/server.ts packages/react-router/lib/server-runtime/server.ts:83 — packages/react-router/lib/server-runtime/server.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in server.derive.requestHandler at line 83. 1 of those changes was a fix/bug commit, and the other 3 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router/lib/server-runtime/server.ts`: 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/react-router-dev/config/config.ts packages/react-router-dev/config/config.ts:473 — packages/react-router-dev/config/config.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 61 in config.resolveConfig at line 473. 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router-dev/config/config.ts`: 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/react-router/lib/dom/lib.tsx packages/react-router/lib/dom/lib.tsx:3060 — packages/react-router/lib/dom/lib.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in lib.useScrollRestoration at line 3060. 4 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router/lib/dom/lib.tsx`: 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/react-router/lib/dom/ssr/single-fetch.tsx packages/react-router/lib/dom/ssr/single-fetch.tsx:621 — packages/react-router/lib/dom/ssr/single-fetch.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in single-fetch.fetchAndDecodeViaTurboStream at line 621. 2 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router/lib/dom/ssr/single-fetch.tsx`: 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/react-router/lib/dom/ssr/components.tsx packages/react-router/lib/dom/ssr/components.tsx:595 — packages/react-router/lib/dom/ssr/components.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in components.Meta at line 595. 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router/lib/dom/ssr/components.tsx`: 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:205 — REDACTED changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in prerender.prerender at line 205. 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04: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/react-router/lib/rsc/server.rsc.ts packages/react-router/lib/rsc/server.rsc.ts:844 — packages/react-router/lib/rsc/server.rsc.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in server.rsc.generateRenderResponse at line 844. 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router/lib/rsc/server.rsc.ts`: 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/react-router-serve/cli.ts packages/react-router-serve/cli.ts:131 — packages/react-router-serve/cli.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in cli.run at line 131. 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-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 16:11:26 -04:00' --until='2026-10-23 16:11:26 -04:00' --full-history --no-merges -- packages/react-router-serve/cli.ts`: 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.
AC3 · Page structure · Page without a main landmark · ×11
  • Page without a main landmark integration/helpers/rsc-vite/src/routes/root.tsx:5 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark playground/framework-express/app/root.tsx:5 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark playground/framework-spa/app/root.tsx:5 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark playground/framework-vite-7/app/root.tsx:12 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark playground/framework/app/root.tsx:12 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark playground/middleware/app/root.tsx:33 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark playground/performance/app/root.tsx:5 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark playground/rsc-vite/src/routes/root/root.client.tsx:74 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark playground/split-route-modules-spa/app/root.tsx:5 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark playground/split-route-modules/app/root.tsx:5 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark tutorials/address-book/app/root.tsx:51 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D30 · Dependency Vulnerabilities · Medium CVE · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D2 · Cognitive Complexity · router.createRouter · ×10
  • router.createRouter::handleLoaders (cognitive 50) packages/react-router/lib/router/router.ts:2442 — router.createRouter::handleLoaders has cognitive complexity 50 (threshold 15). Drivers by points: if/else 20 (30 pts), boolean chains 11, ternaries 5 (9 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. This shape REPEATS in the file: 10 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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.
  • router.createRouter::handleFetcherAction (cognitive 48) packages/react-router/lib/router/router.ts:2888 — router.createRouter::handleFetcherAction has cognitive complexity 48 (threshold 15). Drivers by points: if/else 28 (38 pts), boolean chains 7, loops 1 (2 pts), 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: 10 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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.
  • router.createRouter::startNavigation (cognitive 42) packages/react-router/lib/router/router.ts:1943 — router.createRouter::startNavigation has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 22, if/else 11 (15 pts), ternaries 5 (nesting depth added 4). 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. This shape REPEATS in the file: 10 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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.
  • router.createRouter::handleAction (cognitive 39) packages/react-router/lib/router/router.ts:2244 — router.createRouter::handleAction has cognitive complexity 39 (threshold 15). Drivers by points: if/else 19 (29 pts), boolean chains 5, loops 1 (3 pts), ternaries 1 (2 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. This shape REPEATS in the file: 10 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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.
  • router.createRouter::discoverRoutes (cognitive 33) packages/react-router/lib/router/router.ts:4058 — router.createRouter::discoverRoutes has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (28 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (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. This shape REPEATS in the file: 10 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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.
  • router.createRouter::navigate (cognitive 30) packages/react-router/lib/router/router.ts:1699 — router.createRouter::navigate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 9, ternaries 6 (9 pts) (nesting depth added 5). 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. This shape REPEATS in the file: 10 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::startNavigation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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.
  • router.createRouter::completeNavigation (cognitive 29) packages/react-router/lib/router/router.ts:1542 — router.createRouter::completeNavigation has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 8, ternaries 2 (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. This shape REPEATS in the file: 10 other methods here (router.createRouter, router.createRouter::navigate, router.createRouter::startNavigation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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.
  • router.createRouter::startRedirectNavigation (cognitive 27) packages/react-router/lib/router/router.ts:3428 — router.createRouter::startRedirectNavigation has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 7, ternaries 3 (5 pts) (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. This shape REPEATS in the file: 10 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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.
  • router.createRouter::handleFetcherLoader (cognitive 25) packages/react-router/lib/router/router.ts:3262 — router.createRouter::handleFetcherLoader has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 5). 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. This shape REPEATS in the file: 10 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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.
  • router.createRouter::callDataStrategy (cognitive 17) packages/react-router/lib/router/router.ts:3574 — router.createRouter::callDataStrategy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), boolean chains 2, error handling 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. This shape REPEATS in the file: 10 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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 · router.createRouter · ×9
  • router.createRouter::startNavigation (cyclomatic 47) packages/react-router/lib/router/router.ts:1943 — router.createRouter::startNavigation has cyclomatic complexity 47 (threshold 15). 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. This shape REPEATS in the file: 9 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 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.
  • router.createRouter::handleLoaders (cyclomatic 40) packages/react-router/lib/router/router.ts:2442 — router.createRouter::handleLoaders 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: 9 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 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.
  • router.createRouter::handleFetcherAction (cyclomatic 34) packages/react-router/lib/router/router.ts:2888 — router.createRouter::handleFetcherAction has cyclomatic complexity 34 (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: 9 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 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.
  • router.createRouter::completeNavigation (cyclomatic 29) packages/react-router/lib/router/router.ts:1542 — router.createRouter::completeNavigation has cyclomatic complexity 29 (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. This shape REPEATS in the file: 9 other methods here (router.createRouter, router.createRouter::navigate, router.createRouter::startNavigation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 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.
  • router.createRouter::navigate (cyclomatic 27) packages/react-router/lib/router/router.ts:1699 — router.createRouter::navigate has cyclomatic complexity 27 (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. This shape REPEATS in the file: 9 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::startNavigation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 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.
  • router.createRouter::handleAction (cyclomatic 24) packages/react-router/lib/router/router.ts:2244 — router.createRouter::handleAction has cyclomatic complexity 24 (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: 9 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 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.
  • router.createRouter::startRedirectNavigation (cyclomatic 24) packages/react-router/lib/router/router.ts:3428 — router.createRouter::startRedirectNavigation has cyclomatic complexity 24 (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: 9 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 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.
  • router.createRouter::handleFetcherLoader (cyclomatic 19) packages/react-router/lib/router/router.ts:3262 — router.createRouter::handleFetcherLoader has cyclomatic complexity 19 (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. This shape REPEATS in the file: 9 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 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.
  • router.createRouter::discoverRoutes (cyclomatic 16) packages/react-router/lib/router/router.ts:4058 — router.createRouter::discoverRoutes 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: 9 other methods here (router.createRouter, router.createRouter::completeNavigation, router.createRouter::navigate, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 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.
R11 · Import Boundaries · Boundary violation [package · ×9
  • Boundary violation [package:relative-cross-package] packages/react-router-architect/typedoc.mjs:1 — packages/react-router-architect/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] packages/react-router-cloudflare/typedoc.mjs:1 — packages/react-router-cloudflare/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] packages/react-router-dev/typedoc.mjs:1 — packages/react-router-dev/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] packages/react-router-express/typedoc.mjs:1 — packages/react-router-express/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] packages/react-router-fs-routes/typedoc.mjs:1 — packages/react-router-fs-routes/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] packages/react-router-node/typedoc.mjs:1 — packages/react-router-node/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] packages/react-router-remix-routes-option-adapter/typedoc.mjs:1 — packages/react-router-remix-routes-option-adapter/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] packages/react-router-serve/typedoc.mjs:1 — packages/react-router-serve/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] packages/react-router/typedoc.mjs:1 — packages/react-router/typedoc.mjs:1 reaches into another package with a relative path (../../typedoc.mjs) — import the package by name instead.
D29 · Static Analysis (SAST) · REDACTED · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Fake-async · ×6
  • Fake-async — async method never awaits packages/create-react-router/index.ts:199 — `introStep` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits scripts/changes/migrate-changesets.ts:123 — `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits scripts/experimental.ts:37 — `bumpVersion` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits scripts/experimental.ts:92 — `publishPackages` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits scripts/release-comments.ts:155 — `commentOnIssue` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits tutorials/address-book/app/data.ts:94 — `deleteContact` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×5
  • Duplicated block (27 lines × 2 locations) integration/fog-of-war-test.ts:817 — integration/fog-of-war-test.ts:817 · integration/fog-of-war-test.ts:904 — 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.
  • Duplicated block (27 lines × 2 locations) integration/middleware-test.ts:2867 — integration/middleware-test.ts:2867 · integration/middleware-test.ts:2904 — 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.
  • Duplicated block (27 lines × 2 locations) integration/rsc/rsc-test.ts:243 — integration/rsc/rsc-test.ts:243 · integration/rsc/rsc-test.ts:2398 — 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 (27 lines × 2 locations) integration/vite-prerender-test.ts:1664 — integration/vite-prerender-test.ts:1664 · integration/vite-prerender-test.ts:1817 — 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 (27 lines × 2 locations) packages/react-router/lib/router/router.ts:2968 — packages/react-router/lib/router/router.ts:2968 · packages/react-router/lib/router/router.ts:3330 — 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.
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×4
  • Untrusted text written into markup unescaped packages/react-router/lib/dom/ssr/components.tsx:278 — `criticalCss` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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/react-router/lib/dom/ssr/components.tsx:953 — `contextScript` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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/react-router/lib/dom/ssr/components.tsx:959 — `routeModulesScript` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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/react-router/lib/dom/ssr/components.tsx:1001 — `JSON.stringify({integrity:sri,})` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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.
D12 · Dependency Hygiene · Floating npm dependency · ×3
  • Floating npm dependency: @react-router/node — `@react-router/node` is declared as `*` in tutorials/address-book/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @react-router/serve — `@react-router/serve` is declared as `*` in tutorials/address-book/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: react-router — `react-router` is declared as `*` in tutorials/address-book/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
D23 · Boundary Type-Coupling · Cross-context type ServerMode (react-router → integration) · ×3
  • Cross-context type ServerMode (react-router → integration) integration/helpers/create-fixture.ts:121 — ServerMode (context react-router) is exposed in integration's public surface via create-fixture.createFixture — couples the contexts.
  • Cross-context type ServerMode (react-router → integration) integration/helpers/create-fixture.ts:296 — ServerMode (context react-router) is exposed in integration's public surface via create-fixture.createAppFixture — couples the contexts.
  • Cross-context type ServerMode (react-router → integration) integration/helpers/create-fixture.ts:475 — ServerMode (context react-router) is exposed in integration's public surface via create-fixture.createFixtureProject — couples the contexts.
R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×3
  • Duplicated block (32 lines × 2 locations) integration/fog-of-war-test.ts:987 — integration/fog-of-war-test.ts:987 · integration/fog-of-war-test.ts:1075 — 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 (32 lines × 2 locations) REDACTED:400 — REDACTED:400 · REDACTED:438 — 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 (32 lines × 2 locations) packages/react-router/lib/router/router.ts:2920 — packages/react-router/lib/router/router.ts:2920 · packages/react-router/lib/router/router.ts:3292 — 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 (26 lines × 2 locations) · ×3
  • Duplicated block (26 lines × 2 locations) integration/root-route-test.ts:194 — integration/root-route-test.ts:194 · integration/root-route-test.ts:322 — 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 (26 lines × 2 locations) integration/vite-hmr-hdr-rsc-test.ts:159 — integration/vite-hmr-hdr-rsc-test.ts:159 · integration/vite-hmr-hdr-rsc-test.ts:224 — 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 (26 lines × 2 locations) REDACTED:1596 — REDACTED:1596 · REDACTED:379 — 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.
R8 · Dependency Hygiene · Unused dependency 'isbot' · ×3
  • Unused dependency 'isbot' — Declared in integration/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.
  • Unused dependency 'isbot' — Declared in integration/helpers/vite-7-template/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.
  • Unused dependency 'isbot' — Declared in integration/helpers/vite-8-template/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.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×2
  • Animation without a prefers-reduced-motion guard tutorials/address-book/app/app.css:182 — `#search-spinner` moves (`animation: spin 1s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard tutorials/address-book/app/app.css:435 — `#loading-splash-spinner` moves (`animation: spin 1s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D17 · Explicit Debt · FixmeComment · ×2
  • FixmeComment packages/react-router/lib/rsc/browser.tsx:367 — // FIXME: Pass `build.ssr` into this function — 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.
  • FixmeComment packages/react-router/lib/router/router.ts:1398 — // FIXME: This feels gross. How can we cleanup the lines between — 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.
R10 · Code Duplication · Duplicated block (38 lines × 2 locations) · ×2
  • Duplicated block (38 lines × 2 locations) packages/react-router-fs-routes/manifest.ts:16 — packages/react-router-fs-routes/manifest.ts:16 · packages/react-router-remix-routes-option-adapter/manifest.ts:16 — 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 (38 lines × 2 locations) packages/react-router/lib/dom/ssr/fog-of-war.ts:155 — packages/react-router/lib/dom/ssr/fog-of-war.ts:155 · packages/react-router/lib/rsc/browser.tsx:790 — 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 (36 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (36 matched lines × 2 locations) integration/rsc-client-version-test.ts:141 — integration/rsc-client-version-test.ts:141 · integration/rsc-client-version-test.ts:245 — the two spans are one implementation copied and then locally edited — 237 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 (36 matched lines × 2 locations) packages/create-react-router/prompts-multi-select.ts:34 — packages/create-react-router/prompts-multi-select.ts:34 · packages/create-react-router/prompts-select.ts:41 — the two spans are one implementation copied and then locally edited — 230 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.
R7 · Dead Code · Dead file (~933 LoC) · ×2
  • Dead file (~933 LoC) integration/typegen-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~933 LoC) packages/react-router-dev/vite/remove-exports-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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
X2 · Cancellation propagation · Async function without AbortSignal · ×2
  • Async function without AbortSignal: instrumentedFetch packages/react-router/lib/router/instrumentation.ts:472 — `instrumentedFetch` 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: downloadAndExtractTarball packages/create-react-router/copy-template.ts:206 — `downloadAndExtractTarball` 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 })`.
C2 · Access Controls · No authorization · ×1
  • No authorization packages/react-router-serve/cli.ts:192 — This repository serves requests — express() (packages/react-router-serve/cli.ts:192) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected.
D1 · Cyclomatic Complexity · plugin.reactRouterVitePlugin (cyclomatic 224) · ×1
  • plugin.reactRouterVitePlugin (cyclomatic 224) REDACTED:657 — plugin.reactRouterVitePlugin has cyclomatic complexity 224 (threshold 15). Of this number, 122 points are the body's own statements and 102 belong to 23 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 · plugin.reactRouterRSCVitePlugin (cyclomatic 113) · ×1
  • plugin.reactRouterRSCVitePlugin (cyclomatic 113) REDACTED:45 — plugin.reactRouterRSCVitePlugin has cyclomatic complexity 113 (threshold 15). Of this number, 70 points are the body's own statements and 43 belong to 10 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 · config.resolveConfig (cyclomatic 61) · ×1
  • config.resolveConfig (cyclomatic 61) packages/react-router-dev/config/config.ts:473 — config.resolveConfig has cyclomatic complexity 61 (threshold 15). Of this number, 57 points are the body's own statements and 4 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 · server.ssr.routeRSCServerRequest (cyclomatic 50) · ×1
  • server.ssr.routeRSCServerRequest (cyclomatic 50) packages/react-router/lib/rsc/server.ssr.tsx:90 — server.ssr.routeRSCServerRequest has cyclomatic complexity 50 (threshold 15). Of this number, 46 points are the body's own statements and 4 belong to 4 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 · components.RouterProvider (cyclomatic 41) · ×1
  • components.RouterProvider (cyclomatic 41) packages/react-router/lib/components.tsx:413 — components.RouterProvider has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 3 of the 41 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 443, 594, 620, …). 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 · hooks._renderMatches (cyclomatic 41) · ×1
  • hooks._renderMatches (cyclomatic 41) packages/react-router/lib/hooks.tsx:1228 — hooks._renderMatches has cyclomatic complexity 41 (threshold 15). Of this number, 23 points are the body's own statements and 18 belong to 3 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 · server.derive.requestHandler (cyclomatic 41) · ×1
  • server.derive.requestHandler (cyclomatic 41) packages/react-router/lib/server-runtime/server.ts:83 — server.derive.requestHandler has cyclomatic complexity 41 (threshold 15). Of this number, 40 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 · routes.createClientRoutes (cyclomatic 38) · ×1
  • routes.createClientRoutes (cyclomatic 38) packages/react-router/lib/dom/ssr/routes.tsx:226 — routes.createClientRoutes has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 2 of the 38 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 240, 352, 271, …). 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 · remove-exports.removeExports (cyclomatic 37) · ×1
  • remove-exports.removeExports (cyclomatic 37) packages/react-router-dev/vite/remove-exports.ts:9 — remove-exports.removeExports has cyclomatic complexity 37 (threshold 15). Of this number, 32 points are the body's own statements and 5 belong 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 · RouteDiscoveryRuntime.discover (cyclomatic 35) · ×1
  • RouteDiscoveryRuntime.discover (cyclomatic 35) packages/react-router/lib/dom/ssr/route-discovery.ts:292 — RouteDiscoveryRuntime.discover has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs 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 · flatRoutes.flatRoutesUniversal (cyclomatic 32) · ×1
  • flatRoutes.flatRoutesUniversal (cyclomatic 32) REDACTED:127 — flatRoutes.flatRoutesUniversal 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 · router.createRouter (cyclomatic 32) · ×1
  • router.createRouter (cyclomatic 32) packages/react-router/lib/router/router.ts:1045 — router.createRouter 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. This shape REPEATS in the file: 9 other methods here (router.createRouter::completeNavigation, router.createRouter::navigate, router.createRouter::startNavigation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 10 times rather than 10 independent problems. Splitting this body alone leaves the other 9 exactly as they are. Where these are variations on one operation, the change that clears all 10 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 · hooks.useRoutesImpl (cyclomatic 30) · ×1
  • hooks.useRoutesImpl (cyclomatic 30) packages/react-router/lib/hooks.tsx:765 — hooks.useRoutesImpl has cyclomatic complexity 30 (threshold 15). Of this number, 27 points are the body's own statements and 3 belong to one function literal inside it that branches. 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 · copy-template.downloadAndExtractTarball (cyclomatic 28) · ×1
  • copy-template.downloadAndExtractTarball (cyclomatic 28) packages/create-react-router/copy-template.ts:206 — copy-template.downloadAndExtractTarball has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs 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 · instrumentation.getRouteInstrumentationUpdates (cyclomatic 28) · ×1
  • instrumentation.getRouteInstrumentationUpdates (cyclomatic 28) packages/react-router/lib/router/instrumentation.ts:195 — instrumentation.getRouteInstrumentationUpdates has cyclomatic complexity 28 (threshold 15). Of this number, 21 points are the body's own statements and 7 belong to one function literal inside it that branches. 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 · router.createStaticHandler.query (cyclomatic 28) · ×1
  • router.createStaticHandler.query (cyclomatic 28) packages/react-router/lib/router/router.ts:4368 — router.createStaticHandler.query has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong 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 · utils.action (cyclomatic 27) · ×1
  • utils.action (cyclomatic 27) packages/create-react-router/utils.ts:253 — utils.action has cyclomatic complexity 27 (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 · router.normalizeNavigateOptions (cyclomatic 27) · ×1
  • router.normalizeNavigateOptions (cyclomatic 27) packages/react-router/lib/router/router.ts:5394 — router.normalizeNavigateOptions has cyclomatic complexity 27 (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 · lib.NavLink (cyclomatic 26) · ×1
  • lib.NavLink (cyclomatic 26) packages/react-router/lib/dom/lib.tsx:1631 — lib.NavLink has cyclomatic complexity 26 (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 · publish.main (cyclomatic 26) · ×1
  • publish.main (cyclomatic 26) scripts/changes/publish.ts:182 — publish.main 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 · docs.generateMarkdownForComment (cyclomatic 26) · ×1
  • docs.generateMarkdownForComment (cyclomatic 26) scripts/docs.ts:415 — docs.generateMarkdownForComment has cyclomatic complexity 26 (threshold 15). Of this number, 17 points are the body's own statements and 9 belong 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 · route-chunks.getExportDependencies (cyclomatic 25) · ×1
  • route-chunks.getExportDependencies (cyclomatic 25) packages/react-router-dev/vite/route-chunks.ts:87 — route-chunks.getExportDependencies has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 96, 100, 147, …). 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 · router.getMatchesToLoad (cyclomatic 25) · ×1
  • router.getMatchesToLoad (cyclomatic 25) packages/react-router/lib/router/router.ts:5538 — router.getMatchesToLoad has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 5698). 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.
D1 · Cyclomatic Complexity · remove-exports.validateDestructuredExports (cyclomatic 23) · ×1
  • remove-exports.validateDestructuredExports (cyclomatic 23) packages/react-router-dev/vite/remove-exports.ts:161 — remove-exports.validateDestructuredExports 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 · flatRoutes.getRouteSegments (cyclomatic 23) · ×1
  • flatRoutes.getRouteSegments (cyclomatic 23) REDACTED:351 — flatRoutes.getRouteSegments has cyclomatic complexity 23 (threshold 15). Of this number, 19 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 · router.createStaticHandler.queryRoute (cyclomatic 23) · ×1
  • router.createStaticHandler.queryRoute (cyclomatic 23) packages/react-router/lib/router/router.ts:4658 — router.createStaticHandler.queryRoute has cyclomatic complexity 23 (threshold 15). Of this number, 13 points are the body's own statements and 10 belong to 3 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 · router.createStaticHandler.submit (cyclomatic 23) · ×1
  • router.createStaticHandler.submit (cyclomatic 23) packages/react-router/lib/router/router.ts:4869 — router.createStaticHandler.submit 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 · dom.getFormSubmissionInfo (cyclomatic 23) · ×1
  • dom.getFormSubmissionInfo (cyclomatic 23) packages/react-router/lib/dom/dom.ts:269 — dom.getFormSubmissionInfo 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 · components.Scripts (cyclomatic 22) · ×1
  • components.Scripts (cyclomatic 22) packages/react-router/lib/dom/ssr/components.tsx:806 — components.Scripts has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 belong 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 · migrate-changesets.main (cyclomatic 22) · ×1
  • migrate-changesets.main (cyclomatic 22) scripts/changes/migrate-changesets.ts:123 — migrate-changesets.main has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs 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 · docs.processTypedocModule (cyclomatic 22) · ×1
  • docs.processTypedocModule (cyclomatic 22) scripts/docs.ts:245 — docs.processTypedocModule has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 253, 310, 326, …). 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 · prerender.prerender (cyclomatic 21) · ×1
  • prerender.prerender (cyclomatic 21) REDACTED:205 — prerender.prerender has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (prerenderRequest::attempt, prerender, writePrerenderFile, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · router.processRouteLoaderData (cyclomatic 21) · ×1
  • router.processRouteLoaderData (cyclomatic 21) packages/react-router/lib/router/router.ts:7196 — router.processRouteLoaderData has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 7220). 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.
D1 · Cyclomatic Complexity · config.createConfigLoader.onChange (cyclomatic 20) · ×1
  • config.createConfigLoader.onChange (cyclomatic 20) packages/react-router-dev/config/config.ts:922 — config.createConfigLoader.onChange 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 2 function literals inside it that branch (lines 942, 937). 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 · fileStorage.createFileSessionStorage (cyclomatic 20) · ×1
  • fileStorage.createFileSessionStorage (cyclomatic 20) packages/react-router-node/sessions/fileStorage.ts:31 — fileStorage.createFileSessionStorage 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 · single-fetch.singleFetchLoaderNavigationStrategy (cyclomatic 20) · ×1
  • single-fetch.singleFetchLoaderNavigationStrategy (cyclomatic 20) packages/react-router/lib/dom/ssr/single-fetch.tsx:377 — single-fetch.singleFetchLoaderNavigationStrategy has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to one function literal inside it that branches. 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 · history.getUrlBasedHistory (cyclomatic 19) · ×1
  • history.getUrlBasedHistory (cyclomatic 19) packages/react-router/lib/router/history.ts:652 — history.getUrlBasedHistory has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (push, replace, handlePop, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · utils.resolveTo (cyclomatic 19) · ×1
  • utils.resolveTo (cyclomatic 19) packages/react-router/lib/router/utils.ts:2012 — utils.resolveTo has cyclomatic complexity 19 (threshold 15). 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 · headers.getDocumentHeadersImpl (cyclomatic 19) · ×1
  • headers.getDocumentHeadersImpl (cyclomatic 19) packages/react-router/lib/server-runtime/headers.ts:21 — headers.getDocumentHeadersImpl has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 56, 40). 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 · components.Meta (cyclomatic 19) · ×1
  • components.Meta (cyclomatic 19) packages/react-router/lib/dom/ssr/components.tsx:595 — components.Meta has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 669). 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.
D1 · Cyclomatic Complexity · cli.run (cyclomatic 18) · ×1
  • cli.run (cyclomatic 18) packages/react-router-serve/cli.ts:131 — cli.run has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 3 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 · history.createMemoryHistory (cyclomatic 18) · ×1
  • history.createMemoryHistory (cyclomatic 18) packages/react-router/lib/router/history.ts:251 — history.createMemoryHistory has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 3 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 · router.normalizeTo (cyclomatic 18) · ×1
  • router.normalizeTo (cyclomatic 18) packages/react-router/lib/router/router.ts:5323 — router.normalizeTo 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 · server.rsc.processServerAction (cyclomatic 18) · ×1
  • server.rsc.processServerAction (cyclomatic 18) packages/react-router/lib/rsc/server.rsc.ts:680 — server.rsc.processServerAction has cyclomatic complexity 18 (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 · browser.createCallServer (cyclomatic 18) · ×1
  • browser.createCallServer (cyclomatic 18) packages/react-router/lib/rsc/browser.tsx:112 — browser.createCallServer has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 151, 209, 244, …). 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 · run.run (cyclomatic 17) · ×1
  • run.run (cyclomatic 17) packages/react-router-dev/cli/run.ts:105 — run.run has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. 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 · plugin.validateSsrFalsePrerenderExports (cyclomatic 17) · ×1
  • plugin.validateSsrFalsePrerenderExports (cyclomatic 17) REDACTED:3228 — plugin.validateSsrFalsePrerenderExports 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 · single-fetch.singleFetchLoaders (cyclomatic 17) · ×1
  • single-fetch.singleFetchLoaders (cyclomatic 17) packages/react-router/lib/server-runtime/single-fetch.ts:127 — single-fetch.singleFetchLoaders has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 6 function items inside it that branch (staticContextToResponse, a function literal at line 184, a function literal at line 141, …). 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 · server.handleDocumentRequest (cyclomatic 17) · ×1
  • server.handleDocumentRequest (cyclomatic 17) packages/react-router/lib/server-runtime/server.ts:465 — server.handleDocumentRequest has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (renderHtml, a function literal at line 491, a function literal at line 525). 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 · router.createStaticHandler.loadRouteData (cyclomatic 17) · ×1
  • router.createStaticHandler.loadRouteData (cyclomatic 17) packages/react-router/lib/router/router.ts:5065 — router.createStaticHandler.loadRouteData has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · router.callLoaderOrAction (cyclomatic 17) · ×1
  • router.callLoaderOrAction (cyclomatic 17) packages/react-router/lib/router/router.ts:6819 — router.callLoaderOrAction has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 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 · browser.createRouterFromPayload (cyclomatic 17) · ×1
  • browser.createRouterFromPayload (cyclomatic 17) packages/react-router/lib/rsc/browser.tsx:254 — browser.createRouterFromPayload has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 4 function literals 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 · lib.Link (cyclomatic 17) · ×1
  • lib.Link (cyclomatic 17) packages/react-router/lib/dom/lib.tsx:1322 — lib.Link has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. 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 · lib.useScrollRestoration (cyclomatic 17) · ×1
  • lib.useScrollRestoration (cyclomatic 17) packages/react-router/lib/dom/lib.tsx:3060 — lib.useScrollRestoration has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 3147, 3095, 3118, …). 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 · prerender.nodeHttpFetch (cyclomatic 16) · ×1
  • prerender.nodeHttpFetch (cyclomatic 16) REDACTED:455 — prerender.nodeHttpFetch has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 488, 472, 519). 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 · virtual-route-modules.virtualRouteModulesPlugin.createClientRouteEntry (cyclomatic 16) · ×1
  • virtual-route-modules.virtualRouteModulesPlugin.createClientRouteEntry (cyclomatic 16) packages/react-router-dev/vite/rsc/virtual-route-modules.ts:112 — virtual-route-modules.virtualRouteModulesPlugin.createClientRouteEntry 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 · single-fetch.fetchAndDecodeViaTurboStream (cyclomatic 16) · ×1
  • single-fetch.fetchAndDecodeViaTurboStream (cyclomatic 16) packages/react-router/lib/dom/ssr/single-fetch.tsx:621 — single-fetch.fetchAndDecodeViaTurboStream has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 625). 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.
D1 · Cyclomatic Complexity · browser.getFetchAndDecodeViaRSC (cyclomatic 16) · ×1
  • browser.getFetchAndDecodeViaRSC (cyclomatic 16) packages/react-router/lib/rsc/browser.tsx:558 — browser.getFetchAndDecodeViaRSC has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 564). 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.
D1 · Cyclomatic Complexity · server.ssr.RSCStaticRouter (cyclomatic 16) · ×1
  • server.ssr.RSCStaticRouter (cyclomatic 16) packages/react-router/lib/rsc/server.ssr.tsx:529 — server.ssr.RSCStaticRouter has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong 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 · pr.main (cyclomatic 16) · ×1
  • pr.main (cyclomatic 16) scripts/changes/pr.ts:53 — pr.main 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.
D10 · Test Quality · Fixed-sleep synchronisation · ×1
  • Fixed-sleep synchronisation: Vite / dev / route exports modified offscreen integration/vite-route-exports-modified-offscreen-test.ts:59 — This test starts work it did not wait for (`edit`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 200))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
D12 · Dependency Hygiene · One package at two majors across the workspace · ×1
  • One package at two majors across the workspace: express — `express` is maintained at 2 different major versions inside this one repository — major 4 in integration/helpers/rsc-vite-framework/package.json, integration/helpers/rsc-vite/package.json, integration/helpers/vite-7-template/package.json (+3 more); major 5 in packages/react-router-serve/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
D2 · Cognitive Complexity · plugin.reactRouterVitePlugin (cognitive 152) · ×1
  • plugin.reactRouterVitePlugin (cognitive 152) REDACTED:657 — plugin.reactRouterVitePlugin has cognitive complexity 152 (threshold 15). Drivers by points: if/else 120 (163 pts), boolean chains 48, ternaries 27 (46 pts), loops 9 (11 pts), error handling 5 (8 pts), match/switch 1 (nesting depth added 67). 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 (plugin.reactRouterVitePlugin::generateReactRouterManifestsForBuild) 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.reactRouterRSCVitePlugin (cognitive 111) · ×1
  • plugin.reactRouterRSCVitePlugin (cognitive 111) REDACTED:45 — plugin.reactRouterRSCVitePlugin has cognitive complexity 111 (threshold 15). Drivers by points: if/else 37 (44 pts), ternaries 25 (41 pts), boolean chains 16, error handling 2 (5 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 28). Of this number, 66 points are the body's own statements and 45 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 · config.resolveConfig (cognitive 83) · ×1
  • config.resolveConfig (cognitive 83) packages/react-router-dev/config/config.ts:473 — config.resolveConfig has cognitive complexity 83 (threshold 15). Drivers by points: if/else 35 (56 pts), boolean chains 17, error handling 3 (6 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 26). Of this number, 80 points are the body's own statements and 3 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 · RouteDiscoveryRuntime.discover (cognitive 76) · ×1
  • RouteDiscoveryRuntime.discover (cognitive 76) packages/react-router/lib/dom/ssr/route-discovery.ts:292 — RouteDiscoveryRuntime.discover has cognitive complexity 76 (threshold 15). Drivers by points: if/else 28 (62 pts), error handling 3 (6 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 40). Of this number, 74 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 · server.ssr.routeRSCServerRequest (cognitive 72) · ×1
  • server.ssr.routeRSCServerRequest (cognitive 72) packages/react-router/lib/rsc/server.ssr.tsx:90 — server.ssr.routeRSCServerRequest has cognitive complexity 72 (threshold 15). Drivers by points: if/else 28 (50 pts), ternaries 4 (7 pts), boolean chains 6, loops 4 (6 pts), error handling 2 (3 pts) (nesting depth added 28). Of this number, 66 points are the body's own statements and 6 belong to 4 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 · hooks._renderMatches (cognitive 60) · ×1
  • hooks._renderMatches (cognitive 60) packages/react-router/lib/hooks.tsx:1228 — hooks._renderMatches has cognitive complexity 60 (threshold 15). Drivers by points: if/else 22 (42 pts), boolean chains 14, loops 1 (2 pts), ternaries 2 (nesting depth added 21). Of this number, 40 points are the body's own statements and 20 belong to 3 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 · server.derive.requestHandler (cognitive 51) · ×1
  • server.derive.requestHandler (cognitive 51) packages/react-router/lib/server-runtime/server.ts:83 — server.derive.requestHandler has cognitive complexity 51 (threshold 15). Drivers by points: if/else 22 (33 pts), boolean chains 10, error handling 2 (4 pts), ternaries 2 (4 pts) (nesting depth added 15). Of this number, 50 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 · remove-exports.removeExports (cognitive 50) · ×1
  • remove-exports.removeExports (cognitive 50) packages/react-router-dev/vite/remove-exports.ts:9 — remove-exports.removeExports has cognitive complexity 50 (threshold 15). Drivers by points: if/else 18 (37 pts), boolean chains 11, loops 1 (2 pts) (nesting depth added 20). 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 · flatRoutes.flatRoutesUniversal (cognitive 49) · ×1
  • flatRoutes.flatRoutesUniversal (cognitive 49) REDACTED:127 — flatRoutes.flatRoutesUniversal has cognitive complexity 49 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 8 (14 pts), boolean chains 7, ternaries 2 (4 pts) (nesting depth added 20). 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 · router.createStaticHandler.query (cognitive 48) · ×1
  • router.createStaticHandler.query (cognitive 48) packages/react-router/lib/router/router.ts:4368 — router.createStaticHandler.query has cognitive complexity 48 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 6 (15 pts), boolean chains 7, error handling 2 (5 pts) (nesting depth added 21). Of this number, 17 points are the body's own statements and 31 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 · components.RouterProvider (cognitive 47) · ×1
  • components.RouterProvider (cognitive 47) packages/react-router/lib/components.tsx:413 — components.RouterProvider has cognitive complexity 47 (threshold 15). Drivers by points: if/else 22 (30 pts), boolean chains 16, ternaries 1 (nesting depth added 8). Most of this is not in the body itself: 2 of the 47 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 443, 594, 611, …). 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 · flatRoutes.getRouteSegments (cognitive 46) · ×1
  • flatRoutes.getRouteSegments (cognitive 46) REDACTED:351 — flatRoutes.getRouteSegments has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (41 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 25). Of this number, 42 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 · router.createRouter (cognitive 45) · ×1
  • router.createRouter (cognitive 45) packages/react-router/lib/router/router.ts:1045 — router.createRouter has cognitive complexity 45 (threshold 15). Drivers by points: if/else 224 (315 pts), boolean chains 129, ternaries 35 (50 pts), loops 9 (14 pts), error handling 2 (3 pts) (nesting depth added 112). 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: 10 other methods here (router.createRouter::completeNavigation, router.createRouter::navigate, router.createRouter::startNavigation, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 11 times rather than 11 independent problems. Splitting this body alone leaves the other 10 exactly as they are. Where these are variations on one operation, the change that clears all 11 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 · router.createStaticHandler.submit (cognitive 44) · ×1
  • router.createStaticHandler.submit (cognitive 44) packages/react-router/lib/router/router.ts:4869 — router.createStaticHandler.submit has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 11 (27 pts), if/else 11 (15 pts), boolean chains 2 (nesting depth added 20). 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 · remove-exports.validateDestructuredExports (cognitive 42) · ×1
  • remove-exports.validateDestructuredExports (cognitive 42) packages/react-router-dev/vite/remove-exports.ts:161 — remove-exports.validateDestructuredExports has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (31 pts), boolean chains 7, loops 2 (4 pts) (nesting depth added 22). 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 · route-chunks.getExportDependencies (cognitive 42) · ×1
  • route-chunks.getExportDependencies (cognitive 42) packages/react-router-dev/vite/route-chunks.ts:87 — route-chunks.getExportDependencies has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 6 (13 pts), boolean chains 5 (nesting depth added 19). None of this is in the body itself: all 42 points belong to 4 function literals inside it that branch (lines 96, 100, 117, …). 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 · docs.processTypedocModule (cognitive 42) · ×1
  • docs.processTypedocModule (cognitive 42) scripts/docs.ts:245 — docs.processTypedocModule has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 6 (21 pts), if/else 12 (19 pts), boolean chains 2 (nesting depth added 22). None of this is in the body itself: all 42 points belong to 4 function literals inside it that branch (lines 253, 326, 310, …). 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 · router.normalizeNavigateOptions (cognitive 41) · ×1
  • router.normalizeNavigateOptions (cognitive 41) packages/react-router/lib/router/router.ts:5394 — router.normalizeNavigateOptions has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (19 pts), ternaries 3 (10 pts), boolean chains 7, error handling 2 (5 pts) (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 · publish.main (cognitive 37) · ×1
  • publish.main (cognitive 37) scripts/changes/publish.ts:182 — publish.main has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (20 pts), loops 6 (9 pts), ternaries 5 (7 pts), boolean chains 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 · docs.generateMarkdownForComment (cognitive 37) · ×1
  • docs.generateMarkdownForComment (cognitive 37) scripts/docs.ts:415 — docs.generateMarkdownForComment has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 7, ternaries 3 (7 pts), loops 1 (2 pts) (nesting depth added 12). Of this number, 18 points are the body's own statements and 19 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 · server.rsc.processServerAction (cognitive 36) · ×1
  • server.rsc.processServerAction (cognitive 36) packages/react-router/lib/rsc/server.rsc.ts:680 — server.rsc.processServerAction has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (23 pts), ternaries 3 (6 pts), error handling 2 (5 pts), boolean chains 2 (nesting depth added 20). 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 · migrate-changesets.main (cognitive 35) · ×1
  • migrate-changesets.main (cognitive 35) scripts/changes/migrate-changesets.ts:123 — migrate-changesets.main has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 4 (8 pts), ternaries 2, boolean chains 1 (nesting depth added 17). Of this number, 34 points are the body's own statements and 1 belongs 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 · utils.action (cognitive 33) · ×1
  • utils.action (cognitive 33) packages/create-react-router/utils.ts:253 — utils.action has cognitive complexity 33 (threshold 15). Drivers by points: if/else 25 (32 pts), boolean chains 1 (nesting depth added 7). 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 · copy-template.downloadAndExtractTarball (cognitive 32) · ×1
  • copy-template.downloadAndExtractTarball (cognitive 32) packages/create-react-router/copy-template.ts:206 — copy-template.downloadAndExtractTarball has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 7, ternaries 3 (6 pts), error handling 1 (nesting depth added 8). Of this number, 30 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 · components.Scripts (cognitive 31) · ×1
  • components.Scripts (cognitive 31) packages/react-router/lib/dom/ssr/components.tsx:806 — components.Scripts has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 14 (23 pts), if/else 4 (5 pts), boolean chains 3 (nesting depth added 10). Most of this is not in the body itself: 12 of the 31 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 845, 869). 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 · ProgressReporter.onEnd (cognitive 30) · ×1
  • ProgressReporter.onEnd (cognitive 30) integration/reporters/progress.ts:70 — ProgressReporter.onEnd has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (5 pts), boolean chains 4 (nesting depth added 14). Of this number, 29 points are the body's own statements and 1 belongs 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 · instrumentation.getRouteInstrumentationUpdates (cognitive 30) · ×1
  • instrumentation.getRouteInstrumentationUpdates (cognitive 30) packages/react-router/lib/router/instrumentation.ts:195 — instrumentation.getRouteInstrumentationUpdates has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 10 (nesting depth added 4). Of this number, 23 points are the body's own statements and 7 belong to one function literal inside it that branches. 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 · router.processRouteLoaderData (cognitive 30) · ×1
  • router.processRouteLoaderData (cognitive 30) packages/react-router/lib/router/router.ts:7196 — router.processRouteLoaderData has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 5, ternaries 1 (nesting depth added 10). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to one function literal inside it that branches (line 7220). 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 · with-props.decorateComponentExportsWithProps (cognitive 29) · ×1
  • with-props.decorateComponentExportsWithProps (cognitive 29) packages/react-router-dev/vite/with-props.ts:15 — with-props.decorateComponentExportsWithProps has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (24 pts), ternaries 2 (5 pts) (nesting depth added 16). Of this number, 20 points are the body's own statements and 9 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.getAllDynamicCssFiles (cognitive 28) · ×1
  • plugin.getAllDynamicCssFiles (cognitive 28) REDACTED:436 — plugin.getAllDynamicCssFiles has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 4 (13 pts), boolean chains 1 (nesting depth added 18). Most of this is not in the body itself: 3 of the 28 points are its own statements and the rest belongs to one function item inside it that branches (walk). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · plugin.validateSsrFalsePrerenderExports (cognitive 28) · ×1
  • plugin.validateSsrFalsePrerenderExports (cognitive 28) REDACTED:3228 — plugin.validateSsrFalsePrerenderExports has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 3 (5 pts), boolean chains 3, ternaries 1 (3 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 · hooks.useRoutesImpl (cognitive 27) · ×1
  • hooks.useRoutesImpl (cognitive 27) packages/react-router/lib/hooks.tsx:765 — hooks.useRoutesImpl has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 11, if/else 10 (11 pts), ternaries 4 (5 pts) (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, 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 · router.getMatchesToLoad (cognitive 27) · ×1
  • router.getMatchesToLoad (cognitive 27) packages/react-router/lib/router/router.ts:5538 — router.getMatchesToLoad has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 6, ternaries 3 (4 pts) (nesting depth added 4). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 5698). 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 · browser.createCallServer (cognitive 27) · ×1
  • browser.createCallServer (cognitive 27) packages/react-router/lib/rsc/browser.tsx:112 — browser.createCallServer has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 11). None of this is in the body itself: all 27 points belong to 4 function literals inside it that branch (lines 151, 209, 244, …). 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 · config.createConfigLoader.onChange (cognitive 26) · ×1
  • config.createConfigLoader.onChange (cognitive 26) packages/react-router-dev/config/config.ts:922 — config.createConfigLoader.onChange has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (10 pts), ternaries 2 (4 pts), loops 1 (2 pts) (nesting depth added 7). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 942, 937). 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 · fileStorage.createFileSessionStorage (cognitive 26) · ×1
  • fileStorage.createFileSessionStorage (cognitive 26) packages/react-router-node/sessions/fileStorage.ts:31 — fileStorage.createFileSessionStorage has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (18 pts), error handling 4 (5 pts), boolean chains 1, loops 1, ternaries 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 · routes.createClientRoutes (cognitive 26) · ×1
  • routes.createClientRoutes (cognitive 26) packages/react-router/lib/dom/ssr/routes.tsx:226 — routes.createClientRoutes has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 8, ternaries 3 (5 pts) (nesting depth added 5). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 240, 271, 450, …). 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 · router.callLoaderOrAction (cognitive 26) · ×1
  • router.callLoaderOrAction (cognitive 26) packages/react-router/lib/router/router.ts:6819 — router.callLoaderOrAction has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 5 (7 pts), error handling 2, boolean chains 1 (nesting depth added 7). Of this number, 22 points are the body's own statements and 4 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 · router.convertDataStrategyResultToDataResult (cognitive 26) · ×1
  • router.convertDataStrategyResultToDataResult (cognitive 26) packages/react-router/lib/router/router.ts:6971 — router.convertDataStrategyResultToDataResult has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 5 (14 pts), if/else 6 (10 pts), error handling 1 (2 pts) (nesting depth added 14). 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 · dom.getFormSubmissionInfo (cognitive 26) · ×1
  • dom.getFormSubmissionInfo (cognitive 26) packages/react-router/lib/dom/dom.ts:269 — dom.getFormSubmissionInfo has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 9, ternaries 1 (4 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 · lib.useScrollRestoration (cognitive 26) · ×1
  • lib.useScrollRestoration (cognitive 26) packages/react-router/lib/dom/lib.tsx:3060 — lib.useScrollRestoration has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (16 pts), error handling 3 (5 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 3147, 3095, 3118, …). 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 · router.createStaticHandler.queryRoute (cognitive 25) · ×1
  • router.createStaticHandler.queryRoute (cognitive 25) packages/react-router/lib/router/router.ts:4658 — router.createStaticHandler.queryRoute has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 4 (7 pts), boolean chains 5 (nesting depth added 5). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 3 function items inside it that branch (handleQueryResult, a function literal at line 4719, a function literal at line 4743). 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 · cli.run (cognitive 24) · ×1
  • cli.run (cognitive 24) packages/react-router-serve/cli.ts:131 — cli.run has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (14 pts), ternaries 4 (6 pts), boolean chains 4 (nesting depth added 3). Of this number, 14 points are the body's own statements and 10 belong to 3 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 · server.handleDocumentRequest (cognitive 24) · ×1
  • server.handleDocumentRequest (cognitive 24) packages/react-router/lib/server-runtime/server.ts:465 — server.handleDocumentRequest has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 6 (10 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 7 of the 24 points are its own statements and the rest belongs to 3 function items inside it that branch (renderHtml, a function literal at line 491, a function literal at line 525). 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 · router.loadLazyRoute (cognitive 24) · ×1
  • router.loadLazyRoute (cognitive 24) packages/react-router/lib/router/router.ts:6145 — router.loadLazyRoute has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 10). Of this number, 14 points are the body's own statements and 10 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 · lib.deserializeErrors (cognitive 24) · ×1
  • lib.deserializeErrors (cognitive 24) packages/react-router/lib/dom/lib.tsx:721 — lib.deserializeErrors has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 1 (5 pts), boolean chains 3, 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 · single-fetch.fetchAndDecodeViaTurboStream (cognitive 23) · ×1
  • single-fetch.fetchAndDecodeViaTurboStream (cognitive 23) packages/react-router/lib/dom/ssr/single-fetch.tsx:621 — single-fetch.fetchAndDecodeViaTurboStream has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 4, error handling 1 (nesting depth added 4). None of this is in the body itself: all 23 points belong to one function literal inside it that branches (line 625). 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 · routes.createStaticHandlerDataRoutes (cognitive 23) · ×1
  • routes.createStaticHandlerDataRoutes (cognitive 23) packages/react-router/lib/server-runtime/routes.ts:48 — routes.createStaticHandlerDataRoutes has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 5 (7 pts), boolean chains 4 (nesting depth added 8). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 66, 56). 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 · router.patchRoutesImpl (cognitive 23) · ×1
  • router.patchRoutesImpl (cognitive 23) packages/react-router/lib/router/router.ts:5924 — router.patchRoutesImpl has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (9 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 8). 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, 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 · server.rsc.generateRenderResponse (cognitive 23) · ×1
  • server.rsc.generateRenderResponse (cognitive 23) packages/react-router/lib/rsc/server.rsc.ts:844 — server.rsc.generateRenderResponse has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 4 (7 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 9). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 884). 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 · single-fetch.singleFetchLoaderNavigationStrategy (cognitive 22) · ×1
  • single-fetch.singleFetchLoaderNavigationStrategy (cognitive 22) packages/react-router/lib/dom/ssr/single-fetch.tsx:377 — single-fetch.singleFetchLoaderNavigationStrategy has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (7 pts), error handling 3 (5 pts), ternaries 1 (2 pts) (nesting depth added 4). Of this number, 11 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 · changes.parsePackageChanges (cognitive 22) · ×1
  • changes.parsePackageChanges (cognitive 22) scripts/changes/changes.ts:60 — changes.parsePackageChanges has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 3, loops 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 · MultiSelectPrompt.render (cognitive 21) · ×1
  • MultiSelectPrompt.render (cognitive 21) packages/create-react-router/prompts-multi-select.ts:147 — MultiSelectPrompt.render has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (16 pts), if/else 5 (nesting depth added 10). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 174, 163). 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 · prerender.prerender (cognitive 21) · ×1
  • prerender.prerender (cognitive 21) REDACTED:205 — prerender.prerender has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 4 (5 pts), boolean chains 2, error handling 2, loops 2 (nesting depth added 3). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (prerenderRequest::attempt, prerender, writePrerenderFile, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · utils.resolveTo (cognitive 21) · ×1
  • utils.resolveTo (cognitive 21) packages/react-router/lib/router/utils.ts:2012 — utils.resolveTo has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts), loops 1 (3 pts), ternaries 1 (nesting depth added 3). 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 · hooks.RSCErrorHandler (cognitive 21) · ×1
  • hooks.RSCErrorHandler (cognitive 21) packages/react-router/lib/hooks.tsx:1145 — hooks.RSCErrorHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 4 (nesting depth added 10). 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 · server.handleManifestRequest (cognitive 21) · ×1
  • server.handleManifestRequest (cognitive 21) packages/react-router/lib/server-runtime/server.ts:384 — server.handleManifestRequest has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (6 pts), boolean chains 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 · components.Meta (cognitive 21) · ×1
  • components.Meta (cognitive 21) packages/react-router/lib/dom/ssr/components.tsx:595 — components.Meta has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, error handling 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 5). 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 669). 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 · pr.main (cognitive 21) · ×1
  • pr.main (cognitive 21) scripts/changes/pr.ts:53 — pr.main has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 4, loops 2 (3 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 5). 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 · headers.getDocumentHeadersImpl (cognitive 20) · ×1
  • headers.getDocumentHeadersImpl (cognitive 20) packages/react-router/lib/server-runtime/headers.ts:21 — headers.getDocumentHeadersImpl has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 7, ternaries 4 (5 pts) (nesting depth added 3). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 56, 40). 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 · changes.parseAllChangeFiles (cognitive 20) · ×1
  • changes.parseAllChangeFiles (cognitive 20) scripts/changes/changes.ts:218 — changes.parseAllChangeFiles has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4 (5 pts), ternaries 2 (3 pts), boolean chains 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 · (anonymous) (cognitive 20) · ×1
  • (anonymous) (cognitive 20) packages/react-router-dev/vite/static/refresh-utils.mjs:13 — (anonymous) has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 3 (5 pts), other 3, loops 1 (2 pts), boolean chains 1 (nesting depth added 9). 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 · SelectPrompt.render (cognitive 19) · ×1
  • SelectPrompt.render (cognitive 19) packages/create-react-router/prompts-select.ts:173 — SelectPrompt.render has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (14 pts), if/else 5 (nesting depth added 8). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 203). 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 · plugin.reactRouterVitePlugin · ×1
  • plugin.reactRouterVitePlugin::generateReactRouterManifestsForBuild (cognitive 19) REDACTED:952 — plugin.reactRouterVitePlugin::generateReactRouterManifestsForBuild has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (8 pts), boolean chains 5, if/else 3 (5 pts), 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. This shape REPEATS in the file: one other method here (plugin.reactRouterVitePlugin) 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 · history.getUrlBasedHistory (cognitive 19) · ×1
  • history.getUrlBasedHistory (cognitive 19) packages/react-router/lib/router/history.ts:652 — history.getUrlBasedHistory has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 3, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (push, replace, handlePop, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · single-fetch.bubbleMiddlewareErrors (cognitive 19) · ×1
  • single-fetch.bubbleMiddlewareErrors (cognitive 19) packages/react-router/lib/dom/ssr/single-fetch.tsx:512 — single-fetch.bubbleMiddlewareErrors has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 1 (2 pts), error handling 1 (nesting depth added 11). 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, 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 · single-fetch.singleFetchLoaders (cognitive 19) · ×1
  • single-fetch.singleFetchLoaders (cognitive 19) packages/react-router/lib/server-runtime/single-fetch.ts:127 — single-fetch.singleFetchLoaders has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 4, loops 2 (3 pts), ternaries 3, error handling 2 (nesting depth added 3). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 6 function items inside it that branch (staticContextToResponse, a function literal at line 184, a function literal at line 141, …). 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 · router.normalizeTo (cognitive 19) · ×1
  • router.normalizeTo (cognitive 19) packages/react-router/lib/router/router.ts:5323 — router.normalizeTo has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, loops 1 (2 pts), ternaries 1 (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 · lib.NavLink (cognitive 19) · ×1
  • lib.NavLink (cognitive 19) packages/react-router/lib/dom/lib.tsx:1631 — lib.NavLink has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, ternaries 6, if/else 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 · utils.defaultMapRouteProperties (cognitive 18) · ×1
  • utils.defaultMapRouteProperties (cognitive 18) packages/react-router/lib/router/utils.ts:956 — utils.defaultMapRouteProperties has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (18 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 · links.getNewMatchesForLinks (cognitive 18) · ×1
  • links.getNewMatchesForLinks (cognitive 18) packages/react-router/lib/dom/ssr/links.ts:179 — links.getNewMatchesForLinks has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 6 (nesting depth added 5). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 214, matchPathChanged, isNew, …). 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 · docs.simplifyComment (cognitive 18) · ×1
  • docs.simplifyComment (cognitive 18) scripts/docs.ts:578 — docs.simplifyComment has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 1 (nesting depth added 5). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 622). 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 · branch.updatePackageDependencies (cognitive 18) · ×1
  • branch.updatePackageDependencies (cognitive 18) scripts/previews/branch.ts:94 — branch.updatePackageDependencies has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (8 pts), ternaries 1 (5 pts), loops 2 (4 pts), boolean chains 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.
D2 · Cognitive Complexity · commands.generateEntry (cognitive 17) · ×1
  • commands.generateEntry (cognitive 17) packages/react-router-dev/cli/commands.ts:93 — commands.generateEntry has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 3 (6 pts), boolean chains 1 (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 · styles.getStylesForFiles (cognitive 17) · ×1
  • styles.getStylesForFiles (cognitive 17) packages/react-router-dev/vite/styles.ts:50 — styles.getStylesForFiles has cognitive complexity 17 (threshold 15). Drivers by points: error handling 3 (7 pts), if/else 3 (6 pts), boolean chains 2, loops 2 (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 · prerender.nodeHttpFetch (cognitive 17) · ×1
  • prerender.nodeHttpFetch (cognitive 17) REDACTED:455 — prerender.nodeHttpFetch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (6 pts), boolean chains 4, loops 2 (4 pts), ternaries 3 (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 3 function literals inside it that branch (lines 488, 472, 519). 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 · refresh-utils.enqueueUpdate (cognitive 17) · ×1
  • refresh-utils.enqueueUpdate (cognitive 17) packages/react-router-dev/vite/static/refresh-utils.mjs:13 — refresh-utils.enqueueUpdate has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 3 (5 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). Of this number, 16 points are the body's own statements and 1 belongs 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 · router.createStaticHandler.loadRouteData (cognitive 17) · ×1
  • router.createStaticHandler.loadRouteData (cognitive 17) packages/react-router/lib/router/router.ts:5065 — router.createStaticHandler.loadRouteData has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 5, ternaries 2 (4 pts) (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, 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 · browser.getFetchAndDecodeViaRSC (cognitive 17) · ×1
  • browser.getFetchAndDecodeViaRSC (cognitive 17) packages/react-router/lib/rsc/browser.tsx:558 — browser.getFetchAndDecodeViaRSC has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, loops 2 (3 pts), error handling 1, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 564). 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 · browser.createRouteFromServerManifest (cognitive 17) · ×1
  • browser.createRouteFromServerManifest (cognitive 17) packages/react-router/lib/rsc/browser.tsx:907 — browser.createRouteFromServerManifest has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 4, ternaries 3 (4 pts) (nesting depth added 6). Of this number, 9 points are the body's own statements and 8 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 · server.ssr.RSCStaticRouter (cognitive 17) · ×1
  • server.ssr.RSCStaticRouter (cognitive 17) packages/react-router/lib/rsc/server.ssr.tsx:529 — server.ssr.RSCStaticRouter has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (7 pts), loops 1, ternaries 1 (nesting depth added 2). Of this number, 12 points are the body's own statements and 5 belong 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.
D2 · Cognitive Complexity · index.copyTempDirToAppDirStep (cognitive 16) · ×1
  • index.copyTempDirToAppDirStep (cognitive 16) packages/create-react-router/index.ts:361 — index.copyTempDirToAppDirStep has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (16 pts) (nesting depth added 7). Of this number, 14 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 · route-chunks.hasChunkableExport (cognitive 16) · ×1
  • route-chunks.hasChunkableExport (cognitive 16) packages/react-router-dev/vite/route-chunks.ts:468 — route-chunks.hasChunkableExport has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (3 pts) (nesting depth added 7). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 478). 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 · plugin.getEnvironmentOptionsResolvers (cognitive 16) · ×1
  • plugin.getEnvironmentOptionsResolvers (cognitive 16) REDACTED:3649 — plugin.getEnvironmentOptionsResolvers has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, ternaries 4 (5 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 2). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (getBaseOptions, getBaseServerOptions, a function literal at line 3779, …). 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 · virtual-route-modules.virtualRouteModulesPlugin.createClientRouteEntry (cognitive 16) · ×1
  • virtual-route-modules.virtualRouteModulesPlugin.createClientRouteEntry (cognitive 16) packages/react-router-dev/vite/rsc/virtual-route-modules.ts:112 — virtual-route-modules.virtualRouteModulesPlugin.createClientRouteEntry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 7, loops 1 (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 · routes.getRouteComponents (cognitive 16) · ×1
  • routes.getRouteComponents (cognitive 16) packages/react-router/lib/dom/ssr/routes.tsx:69 — routes.getRouteComponents has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (12 pts), boolean chains 3, if/else 1 (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.
D23 · Boundary Type-Coupling · Cross-context type PackageManager (react-router-dev → create-react-router) · ×1
  • Cross-context type PackageManager (react-router-dev → create-react-router) packages/create-react-router/index.ts:187 — PackageManager (context react-router-dev) is exposed in create-react-router's public surface via Context.pkgManager — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type State (react-router-fs-routes → react-router) · ×1
  • Cross-context type State (react-router-fs-routes → react-router) packages/react-router/lib/router/history.ts:65 — State (context react-router-fs-routes) is exposed in react-router's public surface via Location.state — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: ShouldRevalidateFunctionArgs packages/react-router/lib/router/utils.ts:386 — ClassTooLong — 861 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 461 over it, 2.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: data.ts ↔ server.ts packages/react-router/lib/server-runtime/data.ts:1 — `packages/react-router/lib/server-runtime/data.ts` and `packages/react-router/lib/server-runtime/server.ts` change together 54% of the time (19 of the 35 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 19 shared commits counted here, the most recent 3 are `339997f0` feat: remove future.v8_passThroughRequests flag (#15079); `d827bb92` Add support for `future.unstable_passThroughRequests` (#14775); `adadca55` Add unstable_instrumentations API (#14412) — run `git show` on any of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×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
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (FAIL packages/react-router/__tests__/dom/data-browser-router-test.tsx), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
IC1 · Incompleteness & stubs · Both branches are identical · ×1
  • Both branches are identical — the condition decides nothing packages/react-router/lib/types/route-data.ts:171 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (14 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (14 clone groups) packages/react-router/lib/dom/ssr/errorBoundaries.tsx:10 — 14 duplicated blocks under packages/react-router/lib/ have copies in at least two of the sibling directories dom, router, rsc, server-runtime — 12 of them are reported below, and 2 are 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 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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 · Duplication concentrated across 10 sibling directories (12 clone groups) · ×1
  • Duplication concentrated across 10 sibling directories (12 clone groups) packages/react-router-fs-routes/manifest.ts:16 — 12 duplicated blocks under packages/ have copies in at least two of the sibling directories create-react-router, react-router, react-router-architect, react-router-cloudflare, react-router-dev, react-router-express (+4 more sibling(s) not listed) — 11 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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 · Duplication concentrated across 4 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (6 clone groups) integration/helpers/rsc-vite/src/entry.ssr.tsx:8 — 6 duplicated blocks under the repository root have copies in at least two of the sibling directories integration, packages, scripts, tutorials — 3 of them are reported below, and 3 are 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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 (94 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (94 matched lines × 2 locations) packages/react-router/lib/rsc/server.ssr.tsx:172 — packages/react-router/lib/rsc/server.ssr.tsx:172 · packages/react-router/lib/rsc/server.ssr.tsx:353 — the two spans are one implementation copied and then locally edited — 437 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 (91 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (91 matched lines × 2 locations) integration/fog-of-war-test.ts:306 — integration/fog-of-war-test.ts:306 · integration/fog-of-war-test.ts:1234 — the two spans are one implementation copied and then locally edited — 534 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 (80 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (80 matched lines × 2 locations) packages/react-router/lib/dom/ssr/errorBoundaries.tsx:10 — packages/react-router/lib/dom/ssr/errorBoundaries.tsx:10 · packages/react-router/lib/rsc/errorBoundaries.tsx:7 — the two spans are one implementation copied and then locally edited — 344 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 (74 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (74 matched lines × 2 locations) packages/create-react-router/prompts-confirm.ts:48 — packages/create-react-router/prompts-confirm.ts:48 · packages/create-react-router/prompts-multi-select.ts:54 — the two spans are one implementation copied and then locally edited — 402 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 (56 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (56 matched lines × 2 locations) integration/prefetch-test.ts:264 — integration/prefetch-test.ts:264 · integration/prefetch-test.ts:367 — the two spans are one implementation copied and then locally edited — 293 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 (42 lines × 2 locations) · ×1
  • Duplicated block (42 lines × 2 locations) integration/route-config-test.ts:68 — integration/route-config-test.ts:68 · integration/route-config-test.ts:129 — 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 (42 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (42 matched lines × 2 locations) packages/react-router-dev/vite/static/refresh-utils.mjs:98 — packages/react-router-dev/vite/static/refresh-utils.mjs:98 · packages/react-router-dev/vite/static/rsc-refresh-utils.mjs:53 — the two spans are one implementation copied and then locally edited — 293 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 (41 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (41 matched lines × 2 locations) packages/react-router/lib/server-runtime/single-fetch.ts:58 — packages/react-router/lib/server-runtime/single-fetch.ts:58 · packages/react-router/lib/server-runtime/single-fetch.ts:141 — the two spans are one implementation copied and then locally edited — 258 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 (40 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (40 matched lines × 2 locations) integration/split-route-modules-test.ts:320 — integration/split-route-modules-test.ts:320 · integration/split-route-modules-test.ts:427 — the two spans are one implementation copied and then locally edited — 361 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 (37 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (37 matched lines × 2 locations) integration/error-sanitization-test.ts:265 — integration/error-sanitization-test.ts:265 · integration/error-sanitization-test.ts:428 — the two spans are one implementation copied and then locally edited — 293 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 (37 lines × 2 locations) · ×1
  • Duplicated block (37 lines × 2 locations) packages/create-react-router/prompts-confirm.ts:77 — packages/create-react-router/prompts-confirm.ts:77 · packages/create-react-router/prompts-select.ts:119 — 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) integration/rsc-client-version-test.ts:203 — integration/rsc-client-version-test.ts:203 · integration/rsc-client-version-test.ts:292 — the two spans are one implementation copied and then locally edited — 265 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 (34 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (34 matched lines × 2 locations) packages/react-router/lib/router/matcher-route-pattern.ts:173 — packages/react-router/lib/router/matcher-route-pattern.ts:173 · packages/react-router/lib/router/utils.ts:1221 — the two spans are one implementation copied and then locally edited — 175 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 (33 lines × 2 locations) · ×1
  • Duplicated block (33 lines × 2 locations) integration/fs-routes-test.ts:232 — integration/fs-routes-test.ts:232 · integration/fs-routes-test.ts:287 — 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 (31 lines × 2 locations) · ×1
  • Duplicated block (31 lines × 2 locations) integration/vite-dot-server-test.ts:93 — integration/vite-dot-server-test.ts:93 · integration/vite-dot-server-test.ts:158 — 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 (31 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (31 matched lines × 2 locations) packages/react-router/lib/components.tsx:715 — packages/react-router/lib/components.tsx:715 · REDACTED:195 — the two spans are one implementation copied and then locally edited — 155 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 (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) integration/error-boundary-test.ts:716 — integration/error-boundary-test.ts:716 · integration/error-boundary-test.ts:787 — 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 (28 lines × 2 locations) · ×1
  • Duplicated block (28 lines × 2 locations) integration/middleware-test.ts:1830 — integration/middleware-test.ts:1830 · integration/middleware-test.ts:2746 — 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 (26 lines × 3 locations) · ×1
  • Duplicated block (26 lines × 3 locations) integration/rsc/rsc-nojs-test.ts:221 — integration/rsc/rsc-nojs-test.ts:221 · integration/rsc/rsc-test.ts:1900 · integration/rsc/rsc-test.ts:1938 — the 3 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 (26 lines × 4 locations) · ×1
  • Duplicated block (26 lines × 4 locations) packages/react-router/lib/components.tsx:938 — packages/react-router/lib/components.tsx:938 · packages/react-router/lib/dom/lib.tsx:839 · packages/react-router/lib/dom/lib.tsx:930 · packages/react-router/lib/dom/lib.tsx:1017 — 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 with local edits (25 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (25 matched lines × 2 locations) integration/deduped-route-modules-test.ts:209 — integration/deduped-route-modules-test.ts:209 · integration/deduped-route-modules-test.ts:253 — the two spans are one implementation copied and then locally edited — 194 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 (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) integration/middleware-test.ts:438 — integration/middleware-test.ts:438 · integration/middleware-test.ts:1122 — 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.
R2 · Cyclomatic Complexity · Complex function resolveConfig (cyclomatic 65, cognitive 90) · ×1
  • Complex function resolveConfig (cyclomatic 65, cognitive 90) packages/react-router-dev/config/config.ts:473 — resolveConfig has cyclomatic complexity 65 and cognitive complexity 90; 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 startNavigation (cyclomatic 48, cognitive 43) · ×1
  • Complex function startNavigation (cyclomatic 48, cognitive 43) packages/react-router/lib/router/router.ts:1943 — startNavigation has cyclomatic complexity 48 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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 requestHandler (cyclomatic 40, cognitive 55) · ×1
  • Complex function requestHandler (cyclomatic 40, cognitive 55) packages/react-router/lib/server-runtime/server.ts:83 — requestHandler has cyclomatic complexity 40 and cognitive complexity 55; 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 handleLoaders (cyclomatic 40, cognitive 51) · ×1
  • Complex function handleLoaders (cyclomatic 40, cognitive 51) packages/react-router/lib/router/router.ts:2442 — handleLoaders has cyclomatic complexity 40 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 discover (cyclomatic 34, cognitive 74) · ×1
  • Complex function discover (cyclomatic 34, cognitive 74) packages/react-router/lib/dom/ssr/route-discovery.ts:292 — discover has cyclomatic complexity 34 and cognitive complexity 74; 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 handleFetcherAction (cyclomatic 34, cognitive 48) · ×1
  • Complex function handleFetcherAction (cyclomatic 34, cognitive 48) packages/react-router/lib/router/router.ts:2888 — handleFetcherAction has cyclomatic complexity 34 and cognitive complexity 48; 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 flatRoutesUniversal (cyclomatic 32, cognitive 51) · ×1
  • Complex function flatRoutesUniversal (cyclomatic 32, cognitive 51) REDACTED:127 — flatRoutesUniversal has cyclomatic complexity 32 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 createRouter (cyclomatic 32, cognitive 45) · ×1
  • Complex function createRouter (cyclomatic 32, cognitive 45) packages/react-router/lib/router/router.ts:1045 — createRouter has cyclomatic complexity 32 and cognitive complexity 45; 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 30, cognitive 32) · ×1
  • Complex function navigate (cyclomatic 30, cognitive 32) packages/react-router/lib/router/router.ts:1699 — navigate has cyclomatic complexity 30 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 routeRSCServerRequest (cyclomatic 29, cognitive 41) · ×1
  • Complex function routeRSCServerRequest (cyclomatic 29, cognitive 41) packages/react-router/lib/rsc/server.ssr.tsx:90 — routeRSCServerRequest has cyclomatic complexity 29 and cognitive complexity 41; 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 completeNavigation (cyclomatic 29, cognitive 30) · ×1
  • Complex function completeNavigation (cyclomatic 29, cognitive 30) packages/react-router/lib/router/router.ts:1542 — completeNavigation has cyclomatic complexity 29 and cognitive complexity 30; 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 normalizeNavigateOptions (cyclomatic 27, cognitive 40) · ×1
  • Complex function normalizeNavigateOptions (cyclomatic 27, cognitive 40) packages/react-router/lib/router/router.ts:5394 — normalizeNavigateOptions has cyclomatic complexity 27 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 action (cyclomatic 27, cognitive 33) · ×1
  • Complex function action (cyclomatic 27, cognitive 33) packages/create-react-router/utils.ts:253 — action has cyclomatic complexity 27 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 main (cyclomatic 26, cognitive 37) · ×1
  • Complex function main (cyclomatic 26, cognitive 37) scripts/changes/publish.ts:182 — main has cyclomatic complexity 26 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 useRoutesImpl (cyclomatic 26, cognitive 28) · ×1
  • Complex function useRoutesImpl (cyclomatic 26, cognitive 28) packages/react-router/lib/hooks.tsx:765 — useRoutesImpl has cyclomatic complexity 26 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 NavLinkWithRef (cyclomatic 26, cognitive 27) · ×1
  • Complex function NavLinkWithRef (cyclomatic 26, cognitive 27) packages/react-router/lib/dom/lib.tsx:1631 — NavLinkWithRef has cyclomatic complexity 26 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 handleAction (cyclomatic 24, cognitive 39) · ×1
  • Complex function handleAction (cyclomatic 24, cognitive 39) packages/react-router/lib/router/router.ts:2244 — handleAction has cyclomatic complexity 24 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 startRedirectNavigation (cyclomatic 24, cognitive 27) · ×1
  • Complex function startRedirectNavigation (cyclomatic 24, cognitive 27) packages/react-router/lib/router/router.ts:3428 — startRedirectNavigation has cyclomatic complexity 24 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 validateDestructuredExports (cyclomatic 23, cognitive 42) · ×1
  • Complex function validateDestructuredExports (cyclomatic 23, cognitive 42) packages/react-router-dev/vite/remove-exports.ts:161 — validateDestructuredExports has cyclomatic complexity 23 and cognitive complexity 42; 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 submit (cyclomatic 23, cognitive 42) · ×1
  • Complex function submit (cyclomatic 23, cognitive 42) packages/react-router/lib/router/router.ts:4869 — submit has cyclomatic complexity 23 and cognitive complexity 42; 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/react-router/lib/router/router.ts · ×1
  • packages/react-router/lib/router/router.ts: 7215 lines of code packages/react-router/lib/router/router.ts:1 — packages/react-router/lib/router/router.ts has 7215 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 · integration/single-fetch-test.ts · ×1
  • integration/single-fetch-test.ts: 4194 lines of code integration/single-fetch-test.ts:1 — integration/single-fetch-test.ts has 4194 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: 3595 lines of code REDACTED:1 — REDACTED has 3595 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/react-router/lib/dom/lib.tsx · ×1
  • packages/react-router/lib/dom/lib.tsx: 3235 lines of code packages/react-router/lib/dom/lib.tsx:1 — packages/react-router/lib/dom/lib.tsx has 3235 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 · integration/vite-prerender-test.ts · ×1
  • integration/vite-prerender-test.ts: 2931 lines of code integration/vite-prerender-test.ts:1 — integration/vite-prerender-test.ts has 2931 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 · integration/middleware-test.ts · ×1
  • integration/middleware-test.ts: 2715 lines of code integration/middleware-test.ts:1 — integration/middleware-test.ts has 2715 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 · integration/rsc/rsc-test.ts · ×1
  • integration/rsc/rsc-test.ts: 2483 lines of code integration/rsc/rsc-test.ts:1 — integration/rsc/rsc-test.ts has 2483 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/react-router/lib/router/utils.ts · ×1
  • packages/react-router/lib/router/utils.ts: 2272 lines of code packages/react-router/lib/router/utils.ts:1 — packages/react-router/lib/router/utils.ts has 2272 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/react-router/lib/hooks.tsx · ×1
  • packages/react-router/lib/hooks.tsx: 2069 lines of code packages/react-router/lib/hooks.tsx:1 — packages/react-router/lib/hooks.tsx has 2069 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/react-router/lib/components.tsx · ×1
  • packages/react-router/lib/components.tsx: 1946 lines of code packages/react-router/lib/components.tsx:1 — packages/react-router/lib/components.tsx has 1946 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 · integration/fog-of-war-test.ts · ×1
  • integration/fog-of-war-test.ts: 1774 lines of code integration/fog-of-war-test.ts:1 — integration/fog-of-war-test.ts has 1774 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 · integration/client-data-test.ts · ×1
  • integration/client-data-test.ts: 1633 lines of code integration/client-data-test.ts:1 — integration/client-data-test.ts has 1633 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/react-router-dev/vite/route-chunks-test.ts · ×1
  • packages/react-router-dev/vite/route-chunks-test.ts: 1569 lines of code packages/react-router-dev/vite/route-chunks-test.ts:1 — packages/react-router-dev/vite/route-chunks-test.ts has 1569 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/react-router/lib/rsc/server.rsc.ts · ×1
  • packages/react-router/lib/rsc/server.rsc.ts: 1430 lines of code packages/react-router/lib/rsc/server.rsc.ts:1 — packages/react-router/lib/rsc/server.rsc.ts has 1430 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 · integration/vite-spa-mode-test.ts · ×1
  • integration/vite-spa-mode-test.ts: 1239 lines of code integration/vite-spa-mode-test.ts:1 — integration/vite-spa-mode-test.ts has 1239 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/react-router-dev/config/config.ts · ×1
  • packages/react-router-dev/config/config.ts: 1156 lines of code packages/react-router-dev/config/config.ts:1 — packages/react-router-dev/config/config.ts has 1156 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/react-router/lib/rsc/browser.tsx · ×1
  • packages/react-router/lib/rsc/browser.tsx: 1081 lines of code packages/react-router/lib/rsc/browser.tsx:1 — packages/react-router/lib/rsc/browser.tsx has 1081 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 · integration/form-test.ts · ×1
  • integration/form-test.ts: 1011 lines of code integration/form-test.ts:1 — integration/form-test.ts has 1011 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/react-router/lib/dom/ssr/components.tsx · ×1
  • packages/react-router/lib/dom/ssr/components.tsx: 955 lines of code packages/react-router/lib/dom/ssr/components.tsx:1 — packages/react-router/lib/dom/ssr/components.tsx has 955 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: 913 lines of code REDACTED:1 — REDACTED has 913 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 · integration/error-boundary-test.ts · ×1
  • integration/error-boundary-test.ts: 903 lines of code integration/error-boundary-test.ts:1 — integration/error-boundary-test.ts has 903 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 · integration/browser-entry-test.ts · ×1
  • integration/browser-entry-test.ts: 890 lines of code integration/browser-entry-test.ts:1 — integration/browser-entry-test.ts has 890 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/react-router-dev/vite/route-chunks.ts · ×1
  • packages/react-router-dev/vite/route-chunks.ts: 872 lines of code packages/react-router-dev/vite/route-chunks.ts:1 — packages/react-router-dev/vite/route-chunks.ts has 872 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/react-router-dev/vite/remove-exports-test.ts · ×1
  • packages/react-router-dev/vite/remove-exports-test.ts: 824 lines of code packages/react-router-dev/vite/remove-exports-test.ts:1 — packages/react-router-dev/vite/remove-exports-test.ts has 824 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 · integration/typegen-test.ts · ×1
  • integration/typegen-test.ts: 819 lines of code integration/typegen-test.ts:1 — integration/typegen-test.ts 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/react-router/lib/dom/ssr/single-fetch.tsx · ×1
  • packages/react-router/lib/dom/ssr/single-fetch.tsx: 786 lines of code packages/react-router/lib/dom/ssr/single-fetch.tsx:1 — packages/react-router/lib/dom/ssr/single-fetch.tsx has 786 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/create-react-router/index.ts · ×1
  • packages/create-react-router/index.ts: 771 lines of code packages/create-react-router/index.ts:1 — packages/create-react-router/index.ts has 771 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 · integration/vite-api-only-test.ts · ×1
  • integration/vite-api-only-test.ts: 754 lines of code integration/vite-api-only-test.ts:1 — integration/vite-api-only-test.ts has 754 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/react-router/lib/router/history.ts · ×1
  • packages/react-router/lib/router/history.ts: 728 lines of code packages/react-router/lib/router/history.ts:1 — packages/react-router/lib/router/history.ts has 728 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/react-router/lib/server-runtime/server.ts · ×1
  • packages/react-router/lib/server-runtime/server.ts: 707 lines of code packages/react-router/lib/server-runtime/server.ts:1 — packages/react-router/lib/server-runtime/server.ts has 707 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/react-router/lib/router/instrumentation.ts · ×1
  • packages/react-router/lib/router/instrumentation.ts: 685 lines of code packages/react-router/lib/router/instrumentation.ts:1 — packages/react-router/lib/router/instrumentation.ts has 685 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 · integration/vite-basename-test.ts · ×1
  • integration/vite-basename-test.ts: 683 lines of code integration/vite-basename-test.ts:1 — integration/vite-basename-test.ts has 683 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 · scripts/docs.ts · ×1
  • scripts/docs.ts: 682 lines of code scripts/docs.ts:1 — scripts/docs.ts has 682 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/react-router/lib/dom/ssr/route-discovery.ts · ×1
  • packages/react-router/lib/dom/ssr/route-discovery.ts: 655 lines of code packages/react-router/lib/dom/ssr/route-discovery.ts:1 — packages/react-router/lib/dom/ssr/route-discovery.ts has 655 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 · integration/prefetch-test.ts · ×1
  • integration/prefetch-test.ts: 645 lines of code integration/prefetch-test.ts:1 — integration/prefetch-test.ts has 645 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 · integration/error-sanitization-test.ts · ×1
  • integration/error-sanitization-test.ts: 644 lines of code integration/error-sanitization-test.ts:1 — integration/error-sanitization-test.ts has 644 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/react-router/lib/dom/ssr/routes.tsx · ×1
  • packages/react-router/lib/dom/ssr/routes.tsx: 643 lines of code packages/react-router/lib/dom/ssr/routes.tsx:1 — packages/react-router/lib/dom/ssr/routes.tsx has 643 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 · integration/defer-test.ts · ×1
  • integration/defer-test.ts: 627 lines of code integration/defer-test.ts:1 — integration/defer-test.ts has 627 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/react-router/lib/rsc/server.ssr.tsx · ×1
  • packages/react-router/lib/rsc/server.ssr.tsx: 613 lines of code packages/react-router/lib/rsc/server.ssr.tsx:1 — packages/react-router/lib/rsc/server.ssr.tsx has 613 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 · integration/link-test.ts · ×1
  • integration/link-test.ts: 610 lines of code integration/link-test.ts:1 — integration/link-test.ts has 610 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~4662 LoC) · ×1
  • Dead file (~4662 LoC) integration/single-fetch-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~3208 LoC) · ×1
  • Dead file (~3208 LoC) integration/vite-prerender-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~2947 LoC) · ×1
  • Dead file (~2947 LoC) integration/middleware-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~2832 LoC) · ×1
  • Dead file (~2832 LoC) integration/rsc/rsc-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~1933 LoC) · ×1
  • Dead file (~1933 LoC) integration/fog-of-war-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~1775 LoC) · ×1
  • Dead file (~1775 LoC) integration/client-data-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~1686 LoC) · ×1
  • Dead file (~1686 LoC) packages/react-router-dev/vite/route-chunks-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~1368 LoC) · ×1
  • Dead file (~1368 LoC) integration/vite-spa-mode-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~1142 LoC) · ×1
  • Dead file (~1142 LoC) integration/form-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~1020 LoC) · ×1
  • Dead file (~1020 LoC) integration/error-boundary-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~979 LoC) · ×1
  • Dead file (~979 LoC) integration/browser-entry-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~839 LoC) · ×1
  • Dead file (~839 LoC) integration/vite-api-only-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~762 LoC) · ×1
  • Dead file (~762 LoC) integration/vite-basename-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~725 LoC) · ×1
  • Dead file (~725 LoC) integration/prefetch-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~711 LoC) · ×1
  • Dead file (~711 LoC) integration/error-sanitization-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~699 LoC) · ×1
  • Dead file (~699 LoC) integration/defer-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~667 LoC) · ×1
  • Dead file (~667 LoC) integration/link-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~657 LoC) · ×1
  • Dead file (~657 LoC) integration/vite-server-bundles-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~642 LoC) · ×1
  • Dead file (~642 LoC) integration/vite-dev-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~619 LoC) · ×1
  • Dead file (~619 LoC) integration/split-route-modules-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~593 LoC) · ×1
  • Dead file (~593 LoC) integration/fetcher-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~585 LoC) · ×1
  • Dead file (~585 LoC) integration/vite-css-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~522 LoC) · ×1
  • Dead file (~522 LoC) integration/vite-build-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~518 LoC) · ×1
  • Dead file (~518 LoC) integration/cli-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~486 LoC) · ×1
  • Dead file (~486 LoC) integration/vite-preview-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~472 LoC) · ×1
  • Dead file (~472 LoC) integration/headers-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~467 LoC) · ×1
  • Dead file (~467 LoC) integration/navigation-state-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~454 LoC) · ×1
  • Dead file (~454 LoC) integration/fs-routes-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~414 LoC) · ×1
  • Dead file (~414 LoC) integration/root-route-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~397 LoC) · ×1
  • Dead file (~397 LoC) integration/resource-routes-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~392 LoC) · ×1
  • Dead file (~392 LoC) integration/vite-hmr-hdr-rsc-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~381 LoC) · ×1
  • Dead file (~381 LoC) integration/route-discovery-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~379 LoC) · ×1
  • Dead file (~379 LoC) integration/catch-boundary-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~367 LoC) · ×1
  • Dead file (~367 LoC) integration/revalidate-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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 (~362 LoC) · ×1
  • Dead file (~362 LoC) integration/vite-hmr-hdr-test.ts — no import path from any entry point (120 application, 46 tooling, 194 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
X1 · Async correctness · `async` Promise executor · ×1
  • `async` Promise executor integration/helpers/stream.ts:15 — The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
Minor — 154 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate REDACTED:1010 — `!hasClientAction || hasRouteChunkByExportName.clientAction` appears character-identically in 2 files — REDACTED, packages/react-router-dev/vite/rsc/virtual-route-modules.ts. 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 REDACTED:1012 — `!hasClientLoader || hasRouteChunkByExportName.clientLoader` appears character-identically in 2 files — REDACTED, packages/react-router-dev/vite/rsc/virtual-route-modules.ts. 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 REDACTED:1014 — `!hasClientMiddleware || hasRouteChunkByExportName.clientMiddleware` appears character-identically in 2 files — REDACTED, packages/react-router-dev/vite/rsc/virtual-route-modules.ts. 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 REDACTED:1017 — `!hasHydrateFallback || hasRouteChunkByExportName.HydrateFallback` appears character-identically in 2 files — REDACTED, packages/react-router-dev/vite/rsc/virtual-route-modules.ts. 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/react-router/lib/dom/ssr/components.tsx:490 — `!manifestRoute || !manifestRoute.hasLoader` appears character-identically in 2 files — packages/react-router/lib/dom/ssr/components.tsx, packages/react-router/lib/dom/ssr/links.ts. 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/create-react-router/prompts-multi-select.ts:41 — `!opts.choices || !Array.isArray(opts.choices) || opts.choices.length < 1` appears character-identically in 2 files — packages/create-react-router/prompts-multi-select.ts, packages/create-react-router/prompts-select.ts. 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 REDACTED:3529 — `!relativePath.startsWith("..") && !path.isAbsolute(relativePath)` appears character-identically in 2 files — REDACTED, packages/react-router-dev/vite/resolve-file-url.ts. 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/react-router-dev/config/defaults/entry.server.node.tsx:34 — `(userAgent && isbot(userAgent)) || routerContext.isSpaMode` appears character-identically in 2 files — packages/react-router-dev/config/defaults/entry.server.node.tsx, packages/react-router-dev/config/defaults/entry.server.web.tsx. 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/react-router/lib/dom/ssr/data.ts:16 — `contentType && /\bapplication\/json\b/.test(contentType)` appears character-identically in 3 files — packages/react-router/lib/dom/ssr/data.ts, packages/react-router/lib/router/router.ts, packages/react-router/lib/server-runtime/server.ts. 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/react-router/lib/server-runtime/sessions.ts:296 — `cookieHeader && (await cookie.parse(cookieHeader, options))` appears character-identically in 2 files — packages/react-router/lib/server-runtime/sessions.ts, packages/react-router/lib/server-runtime/sessions/cookieStorage.ts. 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/react-router-dev/vite/static/refresh-utils.mjs:134 — `hasExports && allExportsAreHandledOrUnchanged` appears character-identically in 2 files — packages/react-router-dev/vite/static/refresh-utils.mjs, packages/react-router-dev/vite/static/rsc-refresh-utils.mjs. 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/react-router-dev/vite/static/refresh-utils.mjs:107 — `key in nextExports || acceptExports.includes(key)` appears character-identically in 2 files — packages/react-router-dev/vite/static/refresh-utils.mjs, packages/react-router-dev/vite/static/rsc-refresh-utils.mjs. 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/react-router-dev/vite/static/refresh-utils.mjs:115 — `key in prevExports || acceptExports.includes(key)` appears character-identically in 2 files — packages/react-router-dev/vite/static/refresh-utils.mjs, packages/react-router-dev/vite/static/rsc-refresh-utils.mjs. 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/react-router/lib/dom/ssr/fog-of-war.ts:448 — `patch && (!patch.parentId || !patches[patch.parentId])` appears character-identically in 2 files — packages/react-router/lib/dom/ssr/fog-of-war.ts, packages/react-router/lib/dom/ssr/route-discovery.ts. 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/react-router/lib/router/matcher-route-pattern.ts:251 — `path === "*" || !path.endsWith("*") || path.endsWith("/*")` appears character-identically in 2 files — packages/react-router/lib/router/matcher-route-pattern.ts, packages/react-router/lib/router/utils.ts. 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/react-router/lib/router/matcher-route-pattern.ts:258 — `path.endsWith("*") && path !== "*" && !path.endsWith("/*")` appears character-identically in 2 files — packages/react-router/lib/router/matcher-route-pattern.ts, packages/react-router/lib/router/utils.ts. 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/react-router/lib/router/matcher-route-pattern.ts:402 — `pathname.slice(matchedPathname.length) || "/"` appears character-identically in 2 files — packages/react-router/lib/router/matcher-route-pattern.ts, packages/react-router/lib/router/utils.ts. 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/react-router/lib/rsc/browser.tsx:888 — `payload.routeDiscovery.manifestPath || defaultManifestPath` appears character-identically in 2 files — packages/react-router/lib/rsc/browser.tsx, packages/react-router/lib/rsc/server.ssr.tsx. 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/react-router-dev/vite/build.ts:74 — `plugin.name === "react-router" || plugin.name === "react-router/rsc"` appears character-identically in 2 files — packages/react-router-dev/vite/build.ts, packages/react-router-dev/vite/dev.ts. 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 playground/rsc-vite-7-framework/app/routes/mdx-glob.$post/posts/posts.ts:32 — `post.frontmatter && typeof post.frontmatter === "object" && "title" in post.frontmatter && typeof post.frontmatter.title === "string"` appears character-identically in 2 files — playground/rsc-vite-7-framework/app/routes/mdx-glob.$post/posts/posts.ts, playground/rsc-vite-framework/app/routes/mdx-glob.$post/posts/posts.ts. 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 integration/helpers/create-fixture.ts:423 — `req.path.endsWith(".data") || req.path === manifestPath` appears character-identically in 2 files — integration/helpers/create-fixture.ts, packages/react-router-serve/cli.ts. 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/react-router-dev/config/default-rsc-entries/entry.rsc.tsx:56 — `requestContext && !(requestContext instanceof RouterContextProvider)` appears character-identically in 2 files — packages/react-router-dev/config/default-rsc-entries/entry.rsc.tsx, playground/rsc-vite-framework/app/entry.rsc.tsx. 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/react-router/lib/dom/ssr/single-fetch.tsx:668 — `res.status >= 400 && !res.headers.has("X-Remix-Response")` appears character-identically in 2 files — packages/react-router/lib/dom/ssr/single-fetch.tsx, packages/react-router/lib/rsc/browser.tsx. 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/react-router/lib/router/matcher-route-pattern.ts:220 — `route.children && route.children.length > 0` appears character-identically in 2 files — packages/react-router/lib/router/matcher-route-pattern.ts, packages/react-router/lib/router/utils.ts. 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/react-router/lib/dom/ssr/fog-of-war.ts:125 — `state.navigation.location || state.location` appears character-identically in 4 files — packages/react-router/lib/dom/ssr/fog-of-war.ts, packages/react-router/lib/dom/ssr/route-discovery.ts, packages/react-router/lib/router/router.ts, packages/react-router/lib/rsc/browser.tsx. 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.
D7 · Architectural Integrity · Classify ADR enforcement · ×22
  • Classify ADR enforcement: useBlocker decisions/0001-use-blocker.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Use `npm` to manage NPM dependencies for Deno projects decisions/0001-use-npm-to-manage-npm-dependencies-for-deno-projects.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Do not clone request decisions/0002-do-not-clone-request.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Lazy Route Modules decisions/0002-lazy-route-modules.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Data Strategy decisions/0003-data-strategy.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Infer types for `useLoaderData` and `useActionData` from `loader` and `action` via generics decisions/0003-infer-types-for-useloaderdata-and-useactiondata-from-loader-and-action-via-generics.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Remix (and React Router) Streaming APIs decisions/0004-streaming-apis.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Remixing React Router decisions/0005-remixing-react-router.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Linear Workflow decisions/0006-linear-workflow.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Layering Remix on top of React Router 6.4 decisions/0007-remix-on-react-router-6-4-0.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Only support JS conversion for app code decisions/0008-only-support-js-conversion-for-app-code.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Do not rely on treeshaking for correctness decisions/0009-do-not-rely-on-treeshaking-for-correctness.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Splitting up client and server code in Vite decisions/0010-splitting-up-client-and-server-code-in-vite.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: routes.ts decisions/0011-routes-ts.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Type inference decisions/0012-type-inference.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: `react-router.config.ts` decisions/0013-react-router-config-ts.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Middleware + Context decisions/0014-context-middleware.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Title decisions/0015-observability.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Plan: Remove "Agnostic" Layer from RouteObject/RouteMatch Types decisions/0016-plan-remove-agnostic-types.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: API-only server builds decisions/0017-api-only-server-builds.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Custom Fetch and Router Request Metadata decisions/0018-custom-fetch.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Application-Controlled Route Discovery decisions/0019-application-controlled-route-discovery.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
IC1 · Incompleteness & stubs · Disabled test · ×20
  • Disabled test integration/browser-entry-test.ts: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 integration/cli-test.ts:283 — 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 integration/client-data-test.ts:130 — 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 integration/client-data-test.ts:135 — 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 integration/client-data-test.ts:1199 — 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 integration/client-data-test.ts:1480 — 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 integration/deduped-route-modules-test.ts:248 — 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 integration/link-test.ts:612 — 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 integration/manifest-reload-recovery-test.ts:172 — 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 integration/route-config-test.ts: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 integration/rsc/rsc-nojs-test.ts:176 — 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 integration/rsc/rsc-nojs-test.ts:201 — 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 integration/rsc/rsc-nojs-test.ts:236 — 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 integration/rsc/rsc-nojs-test.ts:270 — 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 integration/rsc/rsc-test.ts:1915 — 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 integration/rsc/rsc-test.ts:1953 — 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 integration/vite-basename-test.ts:527 — 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 integration/vite-hmr-hdr-test.ts:86 — 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 integration/vite-route-added-test.ts:42 — 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/react-router/__tests__/server-runtime/server-test.ts:616 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
D12 · Dependency Hygiene · Deprecated · ×13
  • Deprecated: @babel/plugin-proposal-class-properties REDACTED:1977 — @babel/plugin-proposal-class-properties 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:1990 — @babel/plugin-proposal-nullish-coalescing-operator 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:1997 — @babel/plugin-proposal-numeric-separator 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:2004 — @babel/plugin-proposal-optional-chaining 7.21.0 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-private-methods REDACTED:2011 — @babel/plugin-proposal-private-methods 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-private-property-in-object REDACTED:2024 — @babel/plugin-proposal-private-property-in-object 7.21.11 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @extra-number/significant-digits REDACTED:3440 — @extra-number/significant-digits 1.3.9 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:6707 — glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:6712 — glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: inflight REDACTED:6878 — inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: tsconfck REDACTED:8975 — tsconfck 3.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "unmaintained". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: uuid REDACTED:9230 — uuid 3.4.0 is resolved in REDACTED and is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: whatwg-encoding REDACTED:9492 — whatwg-encoding 3.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @exodus/bytes instead for a more spec-conformant and faster implementation". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
P2 · Observability · Console output used as the logging channel · ×12
  • Console output used as the logging channel packages/react-router-dev/invariant.ts:13 — `packages/react-router-dev/invariant.ts` reports through `console.*` at line 13 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/react-router-dev/vite/dev.ts:57 — `packages/react-router-dev/vite/dev.ts` 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 REDACTED:2149 — `REDACTED` reports through `console.*` at line 2149 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 REDACTED:3161 — `REDACTED` reports through `console.*` at line 3161 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/react-router-dev/vite/styles.ts:80 — `packages/react-router-dev/vite/styles.ts` reports through `console.*` at line 80 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/react-router-dev/vite/styles.ts:86 — `packages/react-router-dev/vite/styles.ts` reports through `console.*` at line 86 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/react-router-dev/vite/styles.ts:93 — `packages/react-router-dev/vite/styles.ts` reports through `console.*` at line 93 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/react-router-dev/vite/styles.ts:105 — `packages/react-router-dev/vite/styles.ts` reports through `console.*` at line 105 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/react-router-dev/config/config.ts:939 — `packages/react-router-dev/config/config.ts` reports through `console.*` at line 939 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/react-router-dev/config/config.ts:1111 — `packages/react-router-dev/config/config.ts` reports through `console.*` at line 1111 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/react-router-dev/config/defaults/entry.server.node.tsx:80 — `packages/react-router-dev/config/defaults/entry.server.node.tsx` reports through `console.*` at line 80 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/react-router-dev/config/defaults/entry.server.web.tsx:36 — `packages/react-router-dev/config/defaults/entry.server.web.tsx` 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.
D29 · Static Analysis (SAST) · REDACTED · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D20 · ADR Quality · ADR has no Consequences section · ×7
  • ADR has no Consequences section decisions/0001-use-blocker.md:1 — decisions/0001-use-blocker.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section decisions/0003-data-strategy.md:1 — decisions/0003-data-strategy.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section decisions/0005-remixing-react-router.md:1 — decisions/0005-remixing-react-router.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section decisions/0006-linear-workflow.md:1 — decisions/0006-linear-workflow.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section decisions/0011-routes-ts.md:1 — decisions/0011-routes-ts.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section decisions/0013-react-router-config-ts.md:1 — decisions/0013-react-router-config-ts.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section decisions/0014-context-middleware.md:1 — decisions/0014-context-middleware.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
X7 · Silent fallback defaults · Silent fallback default in catch · ×6
  • Silent fallback default in catch integration/vite-dev-test.ts:545 — `test.describe("Vite dev")` swallows every exception into `return ""` — 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.
  • Silent fallback default in catch integration/vite-dev-test.ts:633 — `readClientDeps` (in `test.describe("Vite dev")`) swallows every exception into `return ""` — 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.
  • Silent fallback default in catch packages/create-react-router/utils.ts:200 — `directoryExists` swallows every exception into `return false` — 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.
  • Silent fallback default in catch packages/create-react-router/utils.ts:209 — `fileExists` swallows every exception into `return false` — 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.
  • Silent fallback default in catch packages/react-router/lib/server-runtime/crypto.ts:31 — `unsign` swallows every exception into `return false` — 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.
  • Silent fallback default in catch packages/react-router/lib/server-runtime/cookies.ts:207 — `decodeData` swallows every exception into `return {}` — 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.
D34 · Knowledge Freshness · Orphaned file · ×5
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file integration/helpers/playwright-fixture.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/react-router/lib/rsc/errorBoundaries.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file integration/helpers/fixtures.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/react-router/lib/errors.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D10 · Test Quality · Mock-dominated test · ×4
  • Mock-dominated test: client-side redirects permit explicit external redirects to %s packages/react-router/__tests__/external-navigation-test.tsx:325 — This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: client-side redirects permit valid internal redirects to %s packages/react-router/__tests__/external-navigation-test.tsx:357 — This test sets up 5 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: delegates to the route if it should reload or not packages/react-router/__tests__/router/should-revalidate-test.ts:126 — This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 7 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: custom handlers override default recovery until removed packages/react-router/__tests__/dom/ssr/route-discovery-test.ts:514 — This test sets up 3 test doubles (for example `jest.spyOn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×4
  • No app-layer HTTPS enforcement detected integration/helpers/rsc-vite-framework/start.js:17 — `app.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 integration/helpers/rsc-vite/server.js:24 — `app.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/react-router-serve/cli.ts:265 — `app.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/react-router-serve/cli.ts:266 — `app.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.)
D30 · Dependency Vulnerabilities · Low CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D25 · ADR Conformance · ADR not followed · ×2
  • ADR not followed: Lazy Route Modules decisions/0002-lazy-route-modules.md:49 — decisions/0002-lazy-route-modules.md:49 rules out `lazy` in internal, route, but production code uses it: packages/react-router-dev/config/routes.ts:125, packages/react-router/lib/dom/ssr/routes.tsx:153, packages/react-router/lib/dom/ssr/routes.tsx:475, integration/helpers/rsc-vite/src/routes.ts:7, integration/helpers/rsc-vite/src/routes.ts:12. Remove the use, or supersede the record if the decision changed.
  • ADR not followed: Lazy Route Modules decisions/0002-lazy-route-modules.md:50 — decisions/0002-lazy-route-modules.md:50 rules out `errorElement`, but production code uses it: packages/react-router/lib/components.tsx:1172, packages/react-router/lib/components.tsx:1264, packages/react-router/lib/components.tsx:1611, packages/react-router/lib/components.tsx:1705, packages/react-router/lib/components.tsx:1732 (+33 more). Remove the use, or supersede the record if the decision changed.
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift docs/upgrading/component-routes.md:32 — docs/upgrading/component-routes.md names Vite 8, but the manifest declares `vite` ^7.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/upgrading/router-provider.md:30 — docs/upgrading/router-provider.md names Vite 8, but the manifest declares `vite` ^7.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add jest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 115 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: Router (19 required operations) packages/react-router/lib/router/router.ts:94 — `Router` declares 19 required operations: `match`, `initialize`, `subscribe`, `enableScrollRestoration`, `navigate`, `navigate`, `fetch`, `revalidate`, `createHref`, `encodeLocation`, `getFetcher`, `resetFetcher`, `deleteFetcher`, `dispose`, `getBlocker`, `deleteBlocker`, `patchRoutes`, `_internalSetRoutes`, `_internalSetStateDoNotUseOrYouWillBreakYourApp`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 19 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D12 · Dependency Hygiene · Outdated (npm) · ×1
  • Outdated (npm): @types/node integration/helpers/rsc-vite-framework/package.json:18 — @types/node is pinned at 22.19.19; registry.npmjs.org publishes 26.6.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.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 15 significant file(s) lose their only recent owner: scripts/changes/changes.ts, REDACTED, packages/react-router/lib/router/matcher-route-pattern.ts, scripts/release-comments.ts, scripts/changes/version.ts, scripts/changes/publish.ts, scripts/changes/pr.ts, scripts/changes/migrate-changesets.ts (+7 more). Pair on, review, or document these before any departure.
D20 · ADR Quality · ADR declares no status · ×1
  • ADR declares no status decisions/0016-plan-remove-agnostic-types.md:1 — `decisions/0016-plan-remove-agnostic-types.md` declares no status, while 21 of the 21 other records in `decisions` do, so a reader cannot tell whether this decision is in force. Add a `Status:` line.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 19 project(s) overshoot their size bounds, lowering Project Cohesion to 8.9/10. The most over is `packages/react-router` (32890 LoC, 236 module-visible types across 11 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.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Low vulnerability · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 5 of 96 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 96 of the 270 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: REDACTED, integration/helpers/playwright-fixture.ts, packages/react-router/lib/rsc/errorBoundaries.tsx, integration/helpers/fixtures.ts, packages/react-router/lib/errors.ts. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×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
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body packages/react-router/lib/dom/ssr/route-discovery.ts:431 — `serverLoad` has an empty body — confirm it's an intentional no-op and not an unfinished method.
M1 · Documentation (README) · Thin README · ×1
  • Thin README — The root README is 82 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 1/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `integration`, `integration/helpers/rsc-vite`, `integration/helpers/rsc-vite-framework`, `packages/create-react-router`, `packages/react-router-serve`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — 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 896938 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.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
R8 · Dependency Hygiene · Type-only dependency 'type-fest' in production deps · ×1
  • Type-only dependency 'type-fest' in production deps integration/helpers/create-fixture.ts:11 — 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 2/4 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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 · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~1.3 `!` null assertions per 1k TypeScript source lines — 79 assertion(s) across the 59709 source line(s) of the 217 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/react-router/lib/router/router.ts (15), packages/react-router/lib/dom-export/hydrated-router.tsx (6), REDACTED (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 67 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×67
  • Outdated (npm): @architect/functions — @architect/functions is pinned at 8.1.9; registry.npmjs.org publishes 8.1.10 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): @babel/core — @babel/core is pinned at 7.29.7; registry.npmjs.org publishes 8.0.9 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): @babel/generator — @babel/generator is pinned at 7.29.7; registry.npmjs.org publishes 8.0.6 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): @babel/parser — @babel/parser is pinned at 7.29.7; registry.npmjs.org publishes 8.0.8 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): @babel/preset-env — @babel/preset-env is pinned at 7.29.7; registry.npmjs.org publishes 8.0.7 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): @babel/preset-react — @babel/preset-react is pinned at 7.29.7; registry.npmjs.org publishes 8.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): @babel/preset-typescript — @babel/preset-typescript is pinned at 7.29.7; registry.npmjs.org publishes 8.0.7 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): @babel/traverse — @babel/traverse is pinned at 7.29.7; registry.npmjs.org publishes 8.0.7 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): @babel/types — @babel/types is pinned at 7.29.7; registry.npmjs.org publishes 8.0.8 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): @eslint/compat — @eslint/compat is pinned at 2.1.0; registry.npmjs.org publishes 2.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): @octokit/request — @octokit/request is pinned at 10.0.10; registry.npmjs.org publishes 10.0.16 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): @playwright/test — @playwright/test is pinned at 1.60.0; registry.npmjs.org publishes 1.64.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): @remix-run/node-fetch-server — @remix-run/node-fetch-server is pinned at 0.14.1; registry.npmjs.org publishes 1.0.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.
  • Outdated (npm): @remix-run/route-pattern — @remix-run/route-pattern is pinned at 0.22.1; registry.npmjs.org publishes 1.0.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.
  • Outdated (npm): @types/aws-lambda — @types/aws-lambda is pinned at 8.10.161; registry.npmjs.org publishes 8.10.164 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): @types/dedent — @types/dedent is pinned at 0.7.2; registry.npmjs.org publishes 1.7.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): @types/express — @types/express is pinned at 4.17.25; registry.npmjs.org publishes 5.0.6 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): @types/jsdom — @types/jsdom is pinned at 28.0.3; registry.npmjs.org publishes 30.0.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.
  • Outdated (npm): @types/react — @types/react is pinned at 19.2.17; registry.npmjs.org publishes 19.3.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.
  • Outdated (npm): @types/react-dom — @types/react-dom is pinned at 19.2.3; registry.npmjs.org publishes 19.3.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.
  • Outdated (npm): @types/react-test-renderer — @types/react-test-renderer is pinned at 19.1.0; registry.npmjs.org publishes 19.3.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.
  • Outdated (npm): @types/semver — @types/semver is pinned at 7.7.1; registry.npmjs.org publishes 7.8.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.
  • Outdated (npm): @typescript-eslint/eslint-plugin — @typescript-eslint/eslint-plugin is pinned at 8.60.0; registry.npmjs.org publishes 8.72.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.
  • Outdated (npm): @typescript-eslint/parser — @typescript-eslint/parser is pinned at 8.60.0; registry.npmjs.org publishes 8.72.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.
  • Outdated (npm): @vanilla-extract/css — @vanilla-extract/css is pinned at 1.20.1; registry.npmjs.org publishes 1.21.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.
  • + 42 more in this group — see findings.md.

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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0a29c916ce794605af87e8672967a4b6/history.json --exit-code 0 --source .2artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0a29c916ce794605af87e8672967a4b6/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/watchdog-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 --exclude docs/api --exclude playground/data --exclude playground/framework/app --exclude playground/framework-express/app --exclude playground/framework-spa/app --exclude playground/framework-vite-7/app --exclude playground/middleware/app --exclude playground/performance/app --exclude playground/performance/public/.well-known --exclude playground/performance/scripts --exclude playground/rsc-vite/src --exclude playground/rsc-vite-7-framework/app --exclude playground/rsc-vite-framework/app --exclude playground/split-route-modules/app --exclude playground/split-route-modules-spa/app --exclude playground/vite-plugin-cloudflare/app --exclude playground/vite-plugin-cloudflare/workers .90artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update54artifacts/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 52 file(s) — `integration/helpers/rsc-vite-framework/app/routes.ts`, `integration/helpers/rsc-vite/src/routes.ts`, `integration/helpers/vite-7-template/app/routes.ts`, `integration/helpers/vite-8-template/app/routes.ts`, `integration/helpers/vite-plugin-cloudflare-template/app/routes.ts`, … (+47 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.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/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a17883-2031-7dab-b6e7-5ca4b56d3c75 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 116 · Warnings: 729 · Recommendations: 154 · Info: 67 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 14:00 UTC.

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