Public report of TanStack/query, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 11:10 UTC · Survey ID cd_12b3407e2754443b85267edd01509ba4
TanStack/query
Measured 14 November 2026, 11:09 UTC, at code version 36dd792
CAI scoreAt riskUp 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 95,239 lines of product code in 45 projects, tests not counted · Estimated rebuild effort: about 1.3 person-years · Weakest lens: Security and Compliance, 27
Findings by how serious they are
33 critical1316 serious1163 minor
9 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 11:09 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
70of 70 dimensions measured by tools.
2435of 2512 findings point to an exact file and line, so you can open each one in the code. The other 77 concern the repository as a whole, such as missing documentation.
70dimensions across 7 lenses, read from 95,239 lines of product code in 45 projects.
TanStack/query is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no access checks on the code's endpoints or handlers and it has packages with a known security hole. It scores 43 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 27, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 13 points. Replacing the 15 packages under a banned licence comes next, worth about 6 points. Raising Security and Compliance to 70 would lift the score to about 55.
Twelve known security holes in the packages the code depends on can be used by attackers. Two automatic updates take new releases before a bad one can be spotted, and fifteen packages carry licence risk. Updating the vulnerable packages, setting a waiting period for automatic updates and replacing or clearing the banned-licence packages would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code, and the password or key in the code's history needs replacing, with the old one switched off. The page or frame without a title needs a descriptive title.
The product code is 95,239 lines, about €190,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe 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.
If Security and Compliance rose from 27 to 70, the lowest score rated Strong, the score would rise from 43 to about 55.
Code composition: what the lines of code are
Product code 43%Tests 57%
New since the last survey: 152 findings
These 152 critical or serious findings weren't in the previous survey, on 26 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Coupling · Off the main sequence: @tanstack/preact-query
Test Quality · No assertions: should keep initialData required when it is defined packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts
Test Quality · No assertions: should have defined data when passed to useInfiniteQuery with defined initialData packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts
Test Quality · No assertions: should keep data possibly undefined when initialData is a ternary that can be undefined packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts
Test Quality · No assertions: should accept annotated reactive options and preserve selected and cached types packages/vue-query/src/__tests__/queryClient.shared-execution-options.test-d.ts
Test Quality · No assertions: should accept annotated options in a root ref packages/vue-query/src/__tests__/queryClient.shared-execution-options.test-d.ts
Test Quality · No assertions: should preserve explicit generic arguments packages/vue-query/src/__tests__/queryClient.shared-execution-options.test-d.ts
Test Quality · No assertions: should retain mutable extracted skipToken options packages/vue-query/src/__tests__/queryClient.shared-execution-options.test-d.ts
Test Quality · No assertions: should preserve discriminated union narrowing in setQueryData updaterFn packages/vue-query/src/__tests__/queryOptions.test-d.ts
Test Quality · No assertions: should allow a getter that returns boolean or undefined packages/vue-query/src/__tests__/queryOptions.test-d.ts
Test Quality · No assertions: should type enabled with the query argument from query-core packages/vue-query/src/__tests__/queryOptions.test-d.ts
Test Quality · No assertions: should have defined data when initialData is provided as an object packages/vue-query/src/__tests__/useInfiniteQuery.test-d.tsx
Test Quality · No assertions: should have defined data when initialData is provided as a function which always returns the data packages/vue-query/src/__tests__/useInfiniteQuery.test-d.tsx
Test Quality · No assertions: should read data and isPending without unwrapping refs packages/vue-query/src/__tests__/useQuery.test-d.ts
Test Quality · No assertions: should narrow data to TData when status is success packages/vue-query/src/__tests__/useQuery.test-d.ts
Test Quality · No assertions: should narrow data to TData when isSuccess is true packages/vue-query/src/__tests__/useQuery.test-d.ts
Test Quality · No assertions: should narrow data to undefined when status is pending packages/vue-query/src/__tests__/useQuery.test-d.ts
Test Quality · No assertions: should narrow error when status is error and keep data possibly undefined packages/vue-query/src/__tests__/useQuery.test-d.ts
Test Quality · No assertions: should keep data defined on state when initialData is provided packages/vue-query/src/__tests__/useQuery.test-d.ts
Test Quality · No assertions: should keep a function returned by select as data packages/vue-query/src/__tests__/useQuery.test-d.ts
Test Quality · No assertions: should keep data possibly undefined when initialData is a ternary that can be undefined packages/solid-query/src/__tests__/infiniteQueryOptions.test-d.tsx
Test Quality · No assertions: should keep data possibly undefined and tag the queryKey with the result type of the QueryFn when initialData may be undefined packages/solid-query/src/__tests__/queryOptions.test-d.tsx
Test Quality · No assertions: should keep data possibly undefined when initialData is a ternary that can be undefined packages/react-query/src/__tests__/infiniteQueryOptions.test-d.tsx
Test Quality · No assertions: should keep data possibly undefined when initialData is a ternary that can be undefined packages/preact-query/src/__tests__/infiniteQueryOptions.test-d.tsx
Test Quality · No assertions: should keep data possibly undefined when initialData is a ternary that can be undefined packages/angular-query-experimental/src/__tests__/infinite-query-options.test-d.ts
Dependency Hygiene · One package at two majors across the workspace: nuxt
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 343 findings
These 343 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one. The first 100 are listed here.
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 · 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 · High CVE: [GHSA redacted] REDACTED
Rebuild cost: about €190,000 · Estimate
Cost to rebuild
€63,000 to €320,000, for 1,047 to 3,321 hours of work, about 1.3 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, 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 43. 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.
Size
Medium: 95,239 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
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 13 points · Medium effort · Access Controls
2
Resolve the 15 Banned license finding(s) in License Compliance — start with REDACTED (15).
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 €190,000 to build again, about 1.3 person-years of work. Its weakest lens is Security and Compliance, at 27 (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 13 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 7.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 285,586 lines over the last 90 days, which is about 1,158,210 lines a year. At that pace, the extra work comes to an estimated 57.9 to 386.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 our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · 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.
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.
167 modules, with 231 dependencies between them. One loop runs through 11 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 127 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.
query-core.src.hydration uses query-core.src.query, so a change to query-core.src.query can break query-core.src.hydration, while a change to query-core.src.hydration can't break query-core.src.query.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→30 query-core.src.hydration uses query-core.src.mutationpart of a loop✕
Connections
1 pair of types, where a type in query-core.src.hydration uses a type in query-core.src.mutation.
query-core.src.hydration uses query-core.src.mutation, so a change to query-core.src.mutation can break query-core.src.hydration, while a change to query-core.src.hydration can't break query-core.src.mutation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→7 query-core.src.retryer uses query-core.src.typespart of a loop✕
Connections
1 pair of types, where a type in query-core.src.retryer uses a type in query-core.src.types.
query-core.src.retryer uses query-core.src.types, so a change to query-core.src.types can break query-core.src.retryer, while a change to query-core.src.retryer can't break query-core.src.types.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
query-core.src.types uses query-core.src.hydration, so a change to query-core.src.hydration can break query-core.src.types, while a change to query-core.src.types can't break query-core.src.hydration.
Position
Below the diagonal: query-core.src.types uses a module listed above it, which is the healthy direction.
query-core.src.types uses query-core.src.retryer, so a change to query-core.src.retryer can break query-core.src.types, while a change to query-core.src.types can't break query-core.src.retryer.
Position
Below the diagonal: query-core.src.types uses a module listed above it, which is the healthy direction.
7→25 query-core.src.types uses query-core.src.queryCachepart of a loop✕
Connections
1 pair of types, where a type in query-core.src.types uses a type in query-core.src.queryCache.
query-core.src.types uses query-core.src.queryCache, so a change to query-core.src.queryCache can break query-core.src.types, while a change to query-core.src.types can't break query-core.src.queryCache.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→26 query-core.src.types uses query-core.src.querypart of a loop✕
Connections
1 pair of types, where a type in query-core.src.types uses a type in query-core.src.query.
query-core.src.types uses query-core.src.query, so a change to query-core.src.query can break query-core.src.types, while a change to query-core.src.types can't break query-core.src.query.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→32 query-core.src.types uses query-core.src.mutationCachepart of a loop✕
Connections
1 pair of types, where a type in query-core.src.types uses a type in query-core.src.mutationCache.
query-core.src.types uses query-core.src.mutationCache, so a change to query-core.src.mutationCache can break query-core.src.types, while a change to query-core.src.types can't break query-core.src.mutationCache.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
query-core.src.utils uses query-core.src.types, so a change to query-core.src.types can break query-core.src.utils, while a change to query-core.src.utils can't break query-core.src.types.
Position
Below the diagonal: query-core.src.utils uses a module listed above it, which is the healthy direction.
query-core.src.queryClient uses query-core.src.types, so a change to query-core.src.types can break query-core.src.queryClient, while a change to query-core.src.queryClient can't break query-core.src.types.
Position
Below the diagonal: query-core.src.queryClient uses a module listed above it, which is the healthy direction.
query-core.src.queryClient uses query-core.src.utils, so a change to query-core.src.utils can break query-core.src.queryClient, while a change to query-core.src.queryClient can't break query-core.src.utils.
Position
Below the diagonal: query-core.src.queryClient uses a module listed above it, which is the healthy direction.
9→25 query-core.src.queryClient uses query-core.src.queryCachepart of a loop✕
Connections
1 pair of types, where a type in query-core.src.queryClient uses a type in query-core.src.queryCache.
query-core.src.queryClient uses query-core.src.queryCache, so a change to query-core.src.queryCache can break query-core.src.queryClient, while a change to query-core.src.queryClient can't break query-core.src.queryCache.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→32 query-core.src.queryClient uses query-core.src.mutationCachepart of a loop✕
Connections
1 pair of types, where a type in query-core.src.queryClient uses a type in query-core.src.mutationCache.
query-core.src.queryClient uses query-core.src.mutationCache, so a change to query-core.src.mutationCache can break query-core.src.queryClient, while a change to query-core.src.queryClient can't break query-core.src.mutationCache.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
lit-query.src uses angular-query-experimental.src.types, so a change to angular-query-experimental.src.types can break lit-query.src, while a change to lit-query.src can't break angular-query-experimental.src.types.
Position
Below the diagonal: lit-query.src uses a module listed above it, which is the healthy direction.
lit-query.src uses lit-query.src.accessor, so a change to lit-query.src.accessor can break lit-query.src, while a change to lit-query.src can't break lit-query.src.accessor.
Position
Below the diagonal: lit-query.src uses a module listed above it, which is the healthy direction.
lit-query.src uses query-core.src.types, so a change to query-core.src.types can break lit-query.src, while a change to lit-query.src can't break query-core.src.types.
Position
Below the diagonal: lit-query.src uses a module listed above it, which is the healthy direction.
lit-query.src uses query-core.src.utils, so a change to query-core.src.utils can break lit-query.src, while a change to lit-query.src can't break query-core.src.utils.
Position
Below the diagonal: lit-query.src uses a module listed above it, which is the healthy direction.
lit-query.src uses query-core.src.queryClient, so a change to query-core.src.queryClient can break lit-query.src, while a change to lit-query.src can't break query-core.src.queryClient.
Position
Below the diagonal: lit-query.src uses a module listed above it, which is the healthy direction.
lit-query.src.controllers.BaseController uses query-core.src.queryClient, so a change to query-core.src.queryClient can break lit-query.src.controllers.BaseController, while a change to lit-query.src.controllers.BaseController can't break query-core.src.queryClient.
Position
Below the diagonal: lit-query.src.controllers.BaseController uses a module listed above it, which is the healthy direction.
preact-query.src.HydrationBoundary uses query-core.src.queryClient, so a change to query-core.src.queryClient can break preact-query.src.HydrationBoundary, while a change to preact-query.src.HydrationBoundary can't break query-core.src.queryClient.
Position
Below the diagonal: preact-query.src.HydrationBoundary uses a module listed above it, which is the healthy direction.
query-core.src.queryObserver uses query-core.src.subscribable, so a change to query-core.src.subscribable can break query-core.src.queryObserver, while a change to query-core.src.queryObserver can't break query-core.src.subscribable.
Position
Below the diagonal: query-core.src.queryObserver uses a module listed above it, which is the healthy direction.
query-core.src.queryObserver uses query-core.src.types, so a change to query-core.src.types can break query-core.src.queryObserver, while a change to query-core.src.queryObserver can't break query-core.src.types.
Position
Below the diagonal: query-core.src.queryObserver uses a module listed above it, which is the healthy direction.
query-core.src.queryObserver uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-core.src.queryObserver, while a change to query-core.src.queryObserver can't break query-core.src.queryClient.
Position
Below the diagonal: query-core.src.queryObserver uses a module listed above it, which is the healthy direction.
13→26 query-core.src.queryObserver uses query-core.src.querypart of a loop✕
Connections
2 pairs of types, where a type in query-core.src.queryObserver uses a type in query-core.src.query.
query-core.src.queryObserver uses query-core.src.query, so a change to query-core.src.query can break query-core.src.queryObserver, while a change to query-core.src.queryObserver can't break query-core.src.query.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
query-devtools.src.contexts.types uses lit-query.src.accessor, so a change to lit-query.src.accessor can break query-devtools.src.contexts.types, while a change to query-devtools.src.contexts.types can't break lit-query.src.accessor.
Position
Below the diagonal: query-devtools.src.contexts.types uses a module listed above it, which is the healthy direction.
query-devtools.src.contexts.types uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-devtools.src.contexts.types, while a change to query-devtools.src.contexts.types can't break query-core.src.queryClient.
Position
Below the diagonal: query-devtools.src.contexts.types uses a module listed above it, which is the healthy direction.
query-persist-client-core.src.persist uses query-core.src.hydration, so a change to query-core.src.hydration can break query-persist-client-core.src.persist, while a change to query-persist-client-core.src.persist can't break query-core.src.hydration.
Position
Below the diagonal: query-persist-client-core.src.persist uses a module listed above it, which is the healthy direction.
query-persist-client-core.src.persist uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-persist-client-core.src.persist, while a change to query-persist-client-core.src.persist can't break query-core.src.queryClient.
Position
Below the diagonal: query-persist-client-core.src.persist uses a module listed above it, which is the healthy direction.
angular-query-experimental.src.devtools-panel.types uses query-core.src.queryClient, so a change to query-core.src.queryClient can break angular-query-experimental.src.devtools-panel.types, while a change to angular-query-experimental.src.devtools-panel.types can't break query-core.src.queryClient.
Position
Below the diagonal: angular-query-experimental.src.devtools-panel.types uses a module listed above it, which is the healthy direction.
angular-query-experimental.src.devtools-panel.types uses query-devtools.src.contexts.types, so a change to query-devtools.src.contexts.types can break angular-query-experimental.src.devtools-panel.types, while a change to angular-query-experimental.src.devtools-panel.types can't break query-devtools.src.contexts.types.
Position
Below the diagonal: angular-query-experimental.src.devtools-panel.types uses a module listed above it, which is the healthy direction.
angular-query-experimental.src.devtools.types uses query-core.src.queryClient, so a change to query-core.src.queryClient can break angular-query-experimental.src.devtools.types, while a change to angular-query-experimental.src.devtools.types can't break query-core.src.queryClient.
Position
Below the diagonal: angular-query-experimental.src.devtools.types uses a module listed above it, which is the healthy direction.
angular-query-experimental.src.devtools.types uses query-devtools.src.contexts.types, so a change to query-devtools.src.contexts.types can break angular-query-experimental.src.devtools.types, while a change to angular-query-experimental.src.devtools.types can't break query-devtools.src.contexts.types.
Position
Below the diagonal: angular-query-experimental.src.devtools.types uses a module listed above it, which is the healthy direction.
lit-query.src.createInfiniteQueryController uses angular-query-experimental.src.types, so a change to angular-query-experimental.src.types can break lit-query.src.createInfiniteQueryController, while a change to lit-query.src.createInfiniteQueryController can't break angular-query-experimental.src.types.
Position
Below the diagonal: lit-query.src.createInfiniteQueryController uses a module listed above it, which is the healthy direction.
lit-query.src.createInfiniteQueryController uses lit-query.src.accessor, so a change to lit-query.src.accessor can break lit-query.src.createInfiniteQueryController, while a change to lit-query.src.createInfiniteQueryController can't break lit-query.src.accessor.
Position
Below the diagonal: lit-query.src.createInfiniteQueryController uses a module listed above it, which is the healthy direction.
lit-query.src.createInfiniteQueryController uses query-core.src.types, so a change to query-core.src.types can break lit-query.src.createInfiniteQueryController, while a change to lit-query.src.createInfiniteQueryController can't break query-core.src.types.
Position
Below the diagonal: lit-query.src.createInfiniteQueryController uses a module listed above it, which is the healthy direction.
lit-query.src.createInfiniteQueryController uses query-core.src.queryClient, so a change to query-core.src.queryClient can break lit-query.src.createInfiniteQueryController, while a change to lit-query.src.createInfiniteQueryController can't break query-core.src.queryClient.
Position
Below the diagonal: lit-query.src.createInfiniteQueryController uses a module listed above it, which is the healthy direction.
lit-query.src.createInfiniteQueryController uses lit-query.src.controllers.BaseController, so a change to lit-query.src.controllers.BaseController can break lit-query.src.createInfiniteQueryController, while a change to lit-query.src.createInfiniteQueryController can't break lit-query.src.controllers.BaseController.
Position
Below the diagonal: lit-query.src.createInfiniteQueryController uses a module listed above it, which is the healthy direction.
lit-query.src.createMutationController uses angular-query-experimental.src.types, so a change to angular-query-experimental.src.types can break lit-query.src.createMutationController, while a change to lit-query.src.createMutationController can't break angular-query-experimental.src.types.
Position
Below the diagonal: lit-query.src.createMutationController uses a module listed above it, which is the healthy direction.
lit-query.src.createMutationController uses lit-query.src.accessor, so a change to lit-query.src.accessor can break lit-query.src.createMutationController, while a change to lit-query.src.createMutationController can't break lit-query.src.accessor.
Position
Below the diagonal: lit-query.src.createMutationController uses a module listed above it, which is the healthy direction.
lit-query.src.createMutationController uses query-core.src.types, so a change to query-core.src.types can break lit-query.src.createMutationController, while a change to lit-query.src.createMutationController can't break query-core.src.types.
Position
Below the diagonal: lit-query.src.createMutationController uses a module listed above it, which is the healthy direction.
lit-query.src.createMutationController uses query-core.src.queryClient, so a change to query-core.src.queryClient can break lit-query.src.createMutationController, while a change to lit-query.src.createMutationController can't break query-core.src.queryClient.
Position
Below the diagonal: lit-query.src.createMutationController uses a module listed above it, which is the healthy direction.
lit-query.src.createMutationController uses lit-query.src.controllers.BaseController, so a change to lit-query.src.controllers.BaseController can break lit-query.src.createMutationController, while a change to lit-query.src.createMutationController can't break lit-query.src.controllers.BaseController.
Position
Below the diagonal: lit-query.src.createMutationController uses a module listed above it, which is the healthy direction.
lit-query.src.createQueriesController uses lit-query.src.accessor, so a change to lit-query.src.accessor can break lit-query.src.createQueriesController, while a change to lit-query.src.createQueriesController can't break lit-query.src.accessor.
Position
Below the diagonal: lit-query.src.createQueriesController uses a module listed above it, which is the healthy direction.
lit-query.src.createQueriesController uses query-core.src.types, so a change to query-core.src.types can break lit-query.src.createQueriesController, while a change to lit-query.src.createQueriesController can't break query-core.src.types.
Position
Below the diagonal: lit-query.src.createQueriesController uses a module listed above it, which is the healthy direction.
lit-query.src.createQueriesController uses query-core.src.queryClient, so a change to query-core.src.queryClient can break lit-query.src.createQueriesController, while a change to lit-query.src.createQueriesController can't break query-core.src.queryClient.
Position
Below the diagonal: lit-query.src.createQueriesController uses a module listed above it, which is the healthy direction.
lit-query.src.createQueriesController uses lit-query.src.controllers.BaseController, so a change to lit-query.src.controllers.BaseController can break lit-query.src.createQueriesController, while a change to lit-query.src.createQueriesController can't break lit-query.src.controllers.BaseController.
Position
Below the diagonal: lit-query.src.createQueriesController uses a module listed above it, which is the healthy direction.
lit-query.src.createQueryController uses angular-query-experimental.src.types, so a change to angular-query-experimental.src.types can break lit-query.src.createQueryController, while a change to lit-query.src.createQueryController can't break angular-query-experimental.src.types.
Position
Below the diagonal: lit-query.src.createQueryController uses a module listed above it, which is the healthy direction.
lit-query.src.createQueryController uses lit-query.src.accessor, so a change to lit-query.src.accessor can break lit-query.src.createQueryController, while a change to lit-query.src.createQueryController can't break lit-query.src.accessor.
Position
Below the diagonal: lit-query.src.createQueryController uses a module listed above it, which is the healthy direction.
lit-query.src.createQueryController uses query-core.src.types, so a change to query-core.src.types can break lit-query.src.createQueryController, while a change to lit-query.src.createQueryController can't break query-core.src.types.
Position
Below the diagonal: lit-query.src.createQueryController uses a module listed above it, which is the healthy direction.
lit-query.src.createQueryController uses query-core.src.queryClient, so a change to query-core.src.queryClient can break lit-query.src.createQueryController, while a change to lit-query.src.createQueryController can't break query-core.src.queryClient.
Position
Below the diagonal: lit-query.src.createQueryController uses a module listed above it, which is the healthy direction.
lit-query.src.createQueryController uses lit-query.src.controllers.BaseController, so a change to lit-query.src.controllers.BaseController can break lit-query.src.createQueryController, while a change to lit-query.src.createQueryController can't break lit-query.src.controllers.BaseController.
Position
Below the diagonal: lit-query.src.createQueryController uses a module listed above it, which is the healthy direction.
lit-query.src.useIsFetching uses lit-query.src.accessor, so a change to lit-query.src.accessor can break lit-query.src.useIsFetching, while a change to lit-query.src.useIsFetching can't break lit-query.src.accessor.
Position
Below the diagonal: lit-query.src.useIsFetching uses a module listed above it, which is the healthy direction.
lit-query.src.useIsFetching uses query-core.src.utils, so a change to query-core.src.utils can break lit-query.src.useIsFetching, while a change to lit-query.src.useIsFetching can't break query-core.src.utils.
Position
Below the diagonal: lit-query.src.useIsFetching uses a module listed above it, which is the healthy direction.
lit-query.src.useIsFetching uses query-core.src.queryClient, so a change to query-core.src.queryClient can break lit-query.src.useIsFetching, while a change to lit-query.src.useIsFetching can't break query-core.src.queryClient.
Position
Below the diagonal: lit-query.src.useIsFetching uses a module listed above it, which is the healthy direction.
lit-query.src.useIsFetching uses lit-query.src.controllers.BaseController, so a change to lit-query.src.controllers.BaseController can break lit-query.src.useIsFetching, while a change to lit-query.src.useIsFetching can't break lit-query.src.controllers.BaseController.
Position
Below the diagonal: lit-query.src.useIsFetching uses a module listed above it, which is the healthy direction.
lit-query.src.useIsMutating uses lit-query.src.accessor, so a change to lit-query.src.accessor can break lit-query.src.useIsMutating, while a change to lit-query.src.useIsMutating can't break lit-query.src.accessor.
Position
Below the diagonal: lit-query.src.useIsMutating uses a module listed above it, which is the healthy direction.
lit-query.src.useIsMutating uses query-core.src.utils, so a change to query-core.src.utils can break lit-query.src.useIsMutating, while a change to lit-query.src.useIsMutating can't break query-core.src.utils.
Position
Below the diagonal: lit-query.src.useIsMutating uses a module listed above it, which is the healthy direction.
lit-query.src.useIsMutating uses query-core.src.queryClient, so a change to query-core.src.queryClient can break lit-query.src.useIsMutating, while a change to lit-query.src.useIsMutating can't break query-core.src.queryClient.
Position
Below the diagonal: lit-query.src.useIsMutating uses a module listed above it, which is the healthy direction.
lit-query.src.useIsMutating uses lit-query.src.controllers.BaseController, so a change to lit-query.src.controllers.BaseController can break lit-query.src.useIsMutating, while a change to lit-query.src.useIsMutating can't break lit-query.src.controllers.BaseController.
Position
Below the diagonal: lit-query.src.useIsMutating uses a module listed above it, which is the healthy direction.
query-core.src.queriesObserver uses query-core.src.subscribable, so a change to query-core.src.subscribable can break query-core.src.queriesObserver, while a change to query-core.src.queriesObserver can't break query-core.src.subscribable.
Position
Below the diagonal: query-core.src.queriesObserver uses a module listed above it, which is the healthy direction.
query-core.src.queriesObserver uses query-core.src.types, so a change to query-core.src.types can break query-core.src.queriesObserver, while a change to query-core.src.queriesObserver can't break query-core.src.types.
Position
Below the diagonal: query-core.src.queriesObserver uses a module listed above it, which is the healthy direction.
query-core.src.queriesObserver uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-core.src.queriesObserver, while a change to query-core.src.queriesObserver can't break query-core.src.queryClient.
Position
Below the diagonal: query-core.src.queriesObserver uses a module listed above it, which is the healthy direction.
query-core.src.queriesObserver uses query-core.src.queryObserver, so a change to query-core.src.queryObserver can break query-core.src.queriesObserver, while a change to query-core.src.queriesObserver can't break query-core.src.queryObserver.
Position
Below the diagonal: query-core.src.queriesObserver uses a module listed above it, which is the healthy direction.
query-core.src.queryCache uses query-core.src.subscribable, so a change to query-core.src.subscribable can break query-core.src.queryCache, while a change to query-core.src.queryCache can't break query-core.src.subscribable.
Position
Below the diagonal: query-core.src.queryCache uses a module listed above it, which is the healthy direction.
query-core.src.queryCache uses query-core.src.types, so a change to query-core.src.types can break query-core.src.queryCache, while a change to query-core.src.queryCache can't break query-core.src.types.
Position
Below the diagonal: query-core.src.queryCache uses a module listed above it, which is the healthy direction.
query-core.src.queryCache uses query-core.src.utils, so a change to query-core.src.utils can break query-core.src.queryCache, while a change to query-core.src.queryCache can't break query-core.src.utils.
Position
Below the diagonal: query-core.src.queryCache uses a module listed above it, which is the healthy direction.
query-core.src.queryCache uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-core.src.queryCache, while a change to query-core.src.queryCache can't break query-core.src.queryClient.
Position
Below the diagonal: query-core.src.queryCache uses a module listed above it, which is the healthy direction.
query-core.src.queryCache uses query-core.src.queryObserver, so a change to query-core.src.queryObserver can break query-core.src.queryCache, while a change to query-core.src.queryCache can't break query-core.src.queryObserver.
Position
Below the diagonal: query-core.src.queryCache uses a module listed above it, which is the healthy direction.
25→26 query-core.src.queryCache uses query-core.src.querypart of a loop✕
Connections
10 pairs of types, where a type in query-core.src.queryCache uses a type in query-core.src.query.
query-core.src.queryCache uses query-core.src.query, so a change to query-core.src.query can break query-core.src.queryCache, while a change to query-core.src.queryCache can't break query-core.src.query.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
query-core.src.query uses query-core.src.retryer, so a change to query-core.src.retryer can break query-core.src.query, while a change to query-core.src.query can't break query-core.src.retryer.
Position
Below the diagonal: query-core.src.query uses a module listed above it, which is the healthy direction.
query-core.src.query uses query-core.src.types, so a change to query-core.src.types can break query-core.src.query, while a change to query-core.src.query can't break query-core.src.types.
Position
Below the diagonal: query-core.src.query uses a module listed above it, which is the healthy direction.
query-core.src.query uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-core.src.query, while a change to query-core.src.query can't break query-core.src.queryClient.
Position
Below the diagonal: query-core.src.query uses a module listed above it, which is the healthy direction.
query-core.src.query uses query-core.src.queryObserver, so a change to query-core.src.queryObserver can break query-core.src.query, while a change to query-core.src.query can't break query-core.src.queryObserver.
Position
Below the diagonal: query-core.src.query uses a module listed above it, which is the healthy direction.
query-core.src.query uses query-core.src.queryCache, so a change to query-core.src.queryCache can break query-core.src.query, while a change to query-core.src.query can't break query-core.src.queryCache.
Position
Below the diagonal: query-core.src.query uses a module listed above it, which is the healthy direction.
query-core.src.infiniteQueryObserver uses query-core.src.types, so a change to query-core.src.types can break query-core.src.infiniteQueryObserver, while a change to query-core.src.infiniteQueryObserver can't break query-core.src.types.
Position
Below the diagonal: query-core.src.infiniteQueryObserver uses a module listed above it, which is the healthy direction.
query-core.src.infiniteQueryObserver uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-core.src.infiniteQueryObserver, while a change to query-core.src.infiniteQueryObserver can't break query-core.src.queryClient.
Position
Below the diagonal: query-core.src.infiniteQueryObserver uses a module listed above it, which is the healthy direction.
query-core.src.infiniteQueryObserver uses query-core.src.queryObserver, so a change to query-core.src.queryObserver can break query-core.src.infiniteQueryObserver, while a change to query-core.src.infiniteQueryObserver can't break query-core.src.queryObserver.
Position
Below the diagonal: query-core.src.infiniteQueryObserver uses a module listed above it, which is the healthy direction.
query-core.src.infiniteQueryObserver uses query-core.src.query, so a change to query-core.src.query can break query-core.src.infiniteQueryObserver, while a change to query-core.src.infiniteQueryObserver can't break query-core.src.query.
Position
Below the diagonal: query-core.src.infiniteQueryObserver uses a module listed above it, which is the healthy direction.
query-core.src.mutationObserver uses query-core.src.subscribable, so a change to query-core.src.subscribable can break query-core.src.mutationObserver, while a change to query-core.src.mutationObserver can't break query-core.src.subscribable.
Position
Below the diagonal: query-core.src.mutationObserver uses a module listed above it, which is the healthy direction.
query-core.src.mutationObserver uses query-core.src.types, so a change to query-core.src.types can break query-core.src.mutationObserver, while a change to query-core.src.mutationObserver can't break query-core.src.types.
Position
Below the diagonal: query-core.src.mutationObserver uses a module listed above it, which is the healthy direction.
query-core.src.mutationObserver uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-core.src.mutationObserver, while a change to query-core.src.mutationObserver can't break query-core.src.queryClient.
Position
Below the diagonal: query-core.src.mutationObserver uses a module listed above it, which is the healthy direction.
query-core.src.mutationObserver uses query-core.src.query, so a change to query-core.src.query can break query-core.src.mutationObserver, while a change to query-core.src.mutationObserver can't break query-core.src.query.
Position
Below the diagonal: query-core.src.mutationObserver uses a module listed above it, which is the healthy direction.
28→30 query-core.src.mutationObserver uses query-core.src.mutationpart of a loop✕
Connections
1 pair of types, where a type in query-core.src.mutationObserver uses a type in query-core.src.mutation.
query-core.src.mutationObserver uses query-core.src.mutation, so a change to query-core.src.mutation can break query-core.src.mutationObserver, while a change to query-core.src.mutationObserver can't break query-core.src.mutation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
query-persist-client-core.src uses query-core.src.types, so a change to query-core.src.types can break query-persist-client-core.src, while a change to query-persist-client-core.src can't break query-core.src.types.
Position
Below the diagonal: query-persist-client-core.src uses a module listed above it, which is the healthy direction.
query-persist-client-core.src uses query-core.src.utils, so a change to query-core.src.utils can break query-persist-client-core.src, while a change to query-persist-client-core.src can't break query-core.src.utils.
Position
Below the diagonal: query-persist-client-core.src uses a module listed above it, which is the healthy direction.
query-persist-client-core.src uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-persist-client-core.src, while a change to query-persist-client-core.src can't break query-core.src.queryClient.
Position
Below the diagonal: query-persist-client-core.src uses a module listed above it, which is the healthy direction.
query-persist-client-core.src uses query-persist-client-core.src.persist, so a change to query-persist-client-core.src.persist can break query-persist-client-core.src, while a change to query-persist-client-core.src can't break query-persist-client-core.src.persist.
Position
Below the diagonal: query-persist-client-core.src uses a module listed above it, which is the healthy direction.
query-persist-client-core.src uses query-core.src.query, so a change to query-core.src.query can break query-persist-client-core.src, while a change to query-persist-client-core.src can't break query-core.src.query.
Position
Below the diagonal: query-persist-client-core.src uses a module listed above it, which is the healthy direction.
query-core.src.mutation uses query-core.src.retryer, so a change to query-core.src.retryer can break query-core.src.mutation, while a change to query-core.src.mutation can't break query-core.src.retryer.
Position
Below the diagonal: query-core.src.mutation uses a module listed above it, which is the healthy direction.
query-core.src.mutation uses query-core.src.types, so a change to query-core.src.types can break query-core.src.mutation, while a change to query-core.src.mutation can't break query-core.src.types.
Position
Below the diagonal: query-core.src.mutation uses a module listed above it, which is the healthy direction.
query-core.src.mutation uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-core.src.mutation, while a change to query-core.src.mutation can't break query-core.src.queryClient.
Position
Below the diagonal: query-core.src.mutation uses a module listed above it, which is the healthy direction.
query-core.src.mutation uses query-core.src.query, so a change to query-core.src.query can break query-core.src.mutation, while a change to query-core.src.mutation can't break query-core.src.query.
Position
Below the diagonal: query-core.src.mutation uses a module listed above it, which is the healthy direction.
query-core.src.mutation uses query-core.src.mutationObserver, so a change to query-core.src.mutationObserver can break query-core.src.mutation, while a change to query-core.src.mutation can't break query-core.src.mutationObserver.
Position
Below the diagonal: query-core.src.mutation uses a module listed above it, which is the healthy direction.
30→32 query-core.src.mutation uses query-core.src.mutationCachepart of a loop✕
Connections
2 pairs of types, where a type in query-core.src.mutation uses a type in query-core.src.mutationCache.
query-core.src.mutation uses query-core.src.mutationCache, so a change to query-core.src.mutationCache can break query-core.src.mutation, while a change to query-core.src.mutation can't break query-core.src.mutationCache.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
query-core.src uses query-core.src.hydration, so a change to query-core.src.hydration can break query-core.src, while a change to query-core.src can't break query-core.src.hydration.
Position
Below the diagonal: query-core.src uses a module listed above it, which is the healthy direction.
query-core.src uses query-core.src.retryer, so a change to query-core.src.retryer can break query-core.src, while a change to query-core.src can't break query-core.src.retryer.
Position
Below the diagonal: query-core.src uses a module listed above it, which is the healthy direction.
query-core.src uses query-core.src.types, so a change to query-core.src.types can break query-core.src, while a change to query-core.src can't break query-core.src.types.
Position
Below the diagonal: query-core.src uses a module listed above it, which is the healthy direction.
query-core.src uses query-core.src.utils, so a change to query-core.src.utils can break query-core.src, while a change to query-core.src can't break query-core.src.utils.
Position
Below the diagonal: query-core.src uses a module listed above it, which is the healthy direction.
query-core.src uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-core.src, while a change to query-core.src can't break query-core.src.queryClient.
Position
Below the diagonal: query-core.src uses a module listed above it, which is the healthy direction.
query-core.src uses query-core.src.query, so a change to query-core.src.query can break query-core.src, while a change to query-core.src can't break query-core.src.query.
Position
Below the diagonal: query-core.src uses a module listed above it, which is the healthy direction.
query-core.src uses query-core.src.mutation, so a change to query-core.src.mutation can break query-core.src, while a change to query-core.src can't break query-core.src.mutation.
Position
Below the diagonal: query-core.src uses a module listed above it, which is the healthy direction.
query-core.src.mutationCache uses query-core.src.subscribable, so a change to query-core.src.subscribable can break query-core.src.mutationCache, while a change to query-core.src.mutationCache can't break query-core.src.subscribable.
Position
Below the diagonal: query-core.src.mutationCache uses a module listed above it, which is the healthy direction.
query-core.src.mutationCache uses query-core.src.types, so a change to query-core.src.types can break query-core.src.mutationCache, while a change to query-core.src.mutationCache can't break query-core.src.types.
Position
Below the diagonal: query-core.src.mutationCache uses a module listed above it, which is the healthy direction.
query-core.src.mutationCache uses query-core.src.utils, so a change to query-core.src.utils can break query-core.src.mutationCache, while a change to query-core.src.mutationCache can't break query-core.src.utils.
Position
Below the diagonal: query-core.src.mutationCache uses a module listed above it, which is the healthy direction.
query-core.src.mutationCache uses query-core.src.queryClient, so a change to query-core.src.queryClient can break query-core.src.mutationCache, while a change to query-core.src.mutationCache can't break query-core.src.queryClient.
Position
Below the diagonal: query-core.src.mutationCache uses a module listed above it, which is the healthy direction.
query-core.src.mutationCache uses query-core.src.query, so a change to query-core.src.query can break query-core.src.mutationCache, while a change to query-core.src.mutationCache can't break query-core.src.query.
Position
Below the diagonal: query-core.src.mutationCache uses a module listed above it, which is the healthy direction.
query-core.src.mutationCache uses query-core.src.mutationObserver, so a change to query-core.src.mutationObserver can break query-core.src.mutationCache, while a change to query-core.src.mutationCache can't break query-core.src.mutationObserver.
Position
Below the diagonal: query-core.src.mutationCache uses a module listed above it, which is the healthy direction.
query-core.src.mutationCache uses query-core.src.mutation, so a change to query-core.src.mutation can break query-core.src.mutationCache, while a change to query-core.src.mutationCache can't break query-core.src.mutation.
Position
Below the diagonal: query-core.src.mutationCache uses a module listed above it, which is the healthy direction.
query-devtools.src uses lit-query.src.accessor, so a change to lit-query.src.accessor can break query-devtools.src, while a change to query-devtools.src can't break lit-query.src.accessor.
Position
Below the diagonal: query-devtools.src uses a module listed above it, which is the healthy direction.
query-devtools.src uses query-devtools.src.contexts.types, so a change to query-devtools.src.contexts.types can break query-devtools.src, while a change to query-devtools.src can't break query-devtools.src.contexts.types.
Position
Below the diagonal: query-devtools.src uses a module listed above it, which is the healthy direction.
query-devtools.src uses query-core.src.query, so a change to query-core.src.query can break query-devtools.src, while a change to query-devtools.src can't break query-core.src.query.
Position
Below the diagonal: query-devtools.src uses a module listed above it, which is the healthy direction.
query-devtools.src uses query-core.src.mutation, so a change to query-core.src.mutation can break query-devtools.src, while a change to query-devtools.src can't break query-core.src.mutation.
Position
Below the diagonal: query-devtools.src uses a module listed above it, which is the healthy direction.
angular-query-experimental.src uses angular-query-experimental.src.types, so a change to angular-query-experimental.src.types can break angular-query-experimental.src, while a change to angular-query-experimental.src can't break angular-query-experimental.src.types.
Position
Below the diagonal: angular-query-experimental.src uses a module listed above it, which is the healthy direction.
angular-query-experimental.src uses query-core.src.utils, so a change to query-core.src.utils can break angular-query-experimental.src, while a change to angular-query-experimental.src can't break query-core.src.utils.
Position
Below the diagonal: angular-query-experimental.src uses a module listed above it, which is the healthy direction.
angular-query-experimental.src uses query-core.src.queryClient, so a change to query-core.src.queryClient can break angular-query-experimental.src, while a change to angular-query-experimental.src can't break query-core.src.queryClient.
Position
Below the diagonal: angular-query-experimental.src uses a module listed above it, which is the healthy direction.
angular-query-experimental.src uses query-core.src.mutationCache, so a change to query-core.src.mutationCache can break angular-query-experimental.src, while a change to angular-query-experimental.src can't break query-core.src.mutationCache.
Position
Below the diagonal: angular-query-experimental.src uses a module listed above it, which is the healthy direction.
preact-query.src uses preact-query.src.types, so a change to preact-query.src.types can break preact-query.src, while a change to preact-query.src can't break preact-query.src.types.
Position
Below the diagonal: preact-query.src uses a module listed above it, which is the healthy direction.
preact-query.src uses query-core.src.types, so a change to query-core.src.types can break preact-query.src, while a change to preact-query.src can't break query-core.src.types.
Position
Below the diagonal: preact-query.src uses a module listed above it, which is the healthy direction.
preact-query.src uses query-core.src.utils, so a change to query-core.src.utils can break preact-query.src, while a change to preact-query.src can't break query-core.src.utils.
Position
Below the diagonal: preact-query.src uses a module listed above it, which is the healthy direction.
preact-query.src uses query-core.src.queryClient, so a change to query-core.src.queryClient can break preact-query.src, while a change to preact-query.src can't break query-core.src.queryClient.
Position
Below the diagonal: preact-query.src uses a module listed above it, which is the healthy direction.
preact-query.src uses preact-query.src.HydrationBoundary, so a change to preact-query.src.HydrationBoundary can break preact-query.src, while a change to preact-query.src can't break preact-query.src.HydrationBoundary.
Position
Below the diagonal: preact-query.src uses a module listed above it, which is the healthy direction.
preact-query.src uses query-core.src.queryObserver, so a change to query-core.src.queryObserver can break preact-query.src, while a change to preact-query.src can't break query-core.src.queryObserver.
Position
Below the diagonal: preact-query.src uses a module listed above it, which is the healthy direction.
preact-query.src uses query-core.src.query, so a change to query-core.src.query can break preact-query.src, while a change to preact-query.src can't break query-core.src.query.
Position
Below the diagonal: preact-query.src uses a module listed above it, which is the healthy direction.
preact-query.src uses query-core.src.mutationCache, so a change to query-core.src.mutationCache can break preact-query.src, while a change to preact-query.src can't break query-core.src.mutationCache.
Position
Below the diagonal: preact-query.src uses a module listed above it, which is the healthy direction.
react-query.src uses preact-query.src.types, so a change to preact-query.src.types can break react-query.src, while a change to react-query.src can't break preact-query.src.types.
Position
Below the diagonal: react-query.src uses a module listed above it, which is the healthy direction.
react-query.src uses query-core.src.types, so a change to query-core.src.types can break react-query.src, while a change to react-query.src can't break query-core.src.types.
Position
Below the diagonal: react-query.src uses a module listed above it, which is the healthy direction.
react-query.src uses query-core.src.utils, so a change to query-core.src.utils can break react-query.src, while a change to react-query.src can't break query-core.src.utils.
Position
Below the diagonal: react-query.src uses a module listed above it, which is the healthy direction.
react-query.src uses query-core.src.queryClient, so a change to query-core.src.queryClient can break react-query.src, while a change to react-query.src can't break query-core.src.queryClient.
Position
Below the diagonal: react-query.src uses a module listed above it, which is the healthy direction.
react-query.src uses preact-query.src.HydrationBoundary, so a change to preact-query.src.HydrationBoundary can break react-query.src, while a change to react-query.src can't break preact-query.src.HydrationBoundary.
Position
Below the diagonal: react-query.src uses a module listed above it, which is the healthy direction.
react-query.src uses query-core.src.queryObserver, so a change to query-core.src.queryObserver can break react-query.src, while a change to react-query.src can't break query-core.src.queryObserver.
Position
Below the diagonal: react-query.src uses a module listed above it, which is the healthy direction.
react-query.src uses query-core.src.query, so a change to query-core.src.query can break react-query.src, while a change to react-query.src can't break query-core.src.query.
Position
Below the diagonal: react-query.src uses a module listed above it, which is the healthy direction.
react-query.src uses query-core.src.mutationCache, so a change to query-core.src.mutationCache can break react-query.src, while a change to react-query.src can't break query-core.src.mutationCache.
Position
Below the diagonal: react-query.src uses a module listed above it, which is the healthy direction.
solid-query.src uses lit-query.src.accessor, so a change to lit-query.src.accessor can break solid-query.src, while a change to solid-query.src can't break lit-query.src.accessor.
Position
Below the diagonal: solid-query.src uses a module listed above it, which is the healthy direction.
solid-query.src uses preact-query.src.types, so a change to preact-query.src.types can break solid-query.src, while a change to solid-query.src can't break preact-query.src.types.
Position
Below the diagonal: solid-query.src uses a module listed above it, which is the healthy direction.
solid-query.src uses query-core.src.types, so a change to query-core.src.types can break solid-query.src, while a change to solid-query.src can't break query-core.src.types.
Position
Below the diagonal: solid-query.src uses a module listed above it, which is the healthy direction.
solid-query.src uses query-core.src.utils, so a change to query-core.src.utils can break solid-query.src, while a change to solid-query.src can't break query-core.src.utils.
Position
Below the diagonal: solid-query.src uses a module listed above it, which is the healthy direction.
solid-query.src uses query-core.src.queryClient, so a change to query-core.src.queryClient can break solid-query.src, while a change to solid-query.src can't break query-core.src.queryClient.
Position
Below the diagonal: solid-query.src uses a module listed above it, which is the healthy direction.
solid-query.src uses query-core.src.query, so a change to query-core.src.query can break solid-query.src, while a change to solid-query.src can't break query-core.src.query.
Position
Below the diagonal: solid-query.src uses a module listed above it, which is the healthy direction.
solid-query.src uses query-core.src.mutationCache, so a change to query-core.src.mutationCache can break solid-query.src, while a change to solid-query.src can't break query-core.src.mutationCache.
Position
Below the diagonal: solid-query.src uses a module listed above it, which is the healthy direction.
svelte-query.src uses angular-query-experimental.src.types, so a change to angular-query-experimental.src.types can break svelte-query.src, while a change to svelte-query.src can't break angular-query-experimental.src.types.
Position
Below the diagonal: svelte-query.src uses a module listed above it, which is the healthy direction.
svelte-query.src uses lit-query.src.accessor, so a change to lit-query.src.accessor can break svelte-query.src, while a change to svelte-query.src can't break lit-query.src.accessor.
Position
Below the diagonal: svelte-query.src uses a module listed above it, which is the healthy direction.
svelte-query.src uses query-core.src.hydration, so a change to query-core.src.hydration can break svelte-query.src, while a change to svelte-query.src can't break query-core.src.hydration.
Position
Below the diagonal: svelte-query.src uses a module listed above it, which is the healthy direction.
svelte-query.src uses query-core.src.utils, so a change to query-core.src.utils can break svelte-query.src, while a change to svelte-query.src can't break query-core.src.utils.
Position
Below the diagonal: svelte-query.src uses a module listed above it, which is the healthy direction.
svelte-query.src uses query-core.src.queryClient, so a change to query-core.src.queryClient can break svelte-query.src, while a change to svelte-query.src can't break query-core.src.queryClient.
Position
Below the diagonal: svelte-query.src uses a module listed above it, which is the healthy direction.
svelte-query.src uses query-core.src.mutationCache, so a change to query-core.src.mutationCache can break svelte-query.src, while a change to svelte-query.src can't break query-core.src.mutationCache.
Position
Below the diagonal: svelte-query.src uses a module listed above it, which is the healthy direction.
vue-query.src.types uses query-core.src.hydration, so a change to query-core.src.hydration can break vue-query.src.types, while a change to vue-query.src.types can't break query-core.src.hydration.
Position
Below the diagonal: vue-query.src.types uses a module listed above it, which is the healthy direction.
vue-query.src.types uses query-core.src.types, so a change to query-core.src.types can break vue-query.src.types, while a change to vue-query.src.types can't break query-core.src.types.
Position
Below the diagonal: vue-query.src.types uses a module listed above it, which is the healthy direction.
vue-query.src.types uses query-core.src.queryCache, so a change to query-core.src.queryCache can break vue-query.src.types, while a change to vue-query.src.types can't break query-core.src.queryCache.
Position
Below the diagonal: vue-query.src.types uses a module listed above it, which is the healthy direction.
vue-query.src.types uses query-core.src.mutationCache, so a change to query-core.src.mutationCache can break vue-query.src.types, while a change to vue-query.src.types can't break query-core.src.mutationCache.
Position
Below the diagonal: vue-query.src.types uses a module listed above it, which is the healthy direction.
vue-query.src uses preact-query.src.types, so a change to preact-query.src.types can break vue-query.src, while a change to vue-query.src can't break preact-query.src.types.
Position
Below the diagonal: vue-query.src uses a module listed above it, which is the healthy direction.
vue-query.src uses query-core.src.queryClient, so a change to query-core.src.queryClient can break vue-query.src, while a change to vue-query.src can't break query-core.src.queryClient.
Position
Below the diagonal: vue-query.src uses a module listed above it, which is the healthy direction.
vue-query.src uses query-core.src.mutationCache, so a change to query-core.src.mutationCache can break vue-query.src, while a change to vue-query.src can't break query-core.src.mutationCache.
Position
Below the diagonal: vue-query.src uses a module listed above it, which is the healthy direction.
vue-query.src uses vue-query.src.types, so a change to vue-query.src.types can break vue-query.src, while a change to vue-query.src can't break vue-query.src.types.
Position
Below the diagonal: vue-query.src uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 54% · Adequate · gated by R10 ·
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 category
Findings
Severity
A03:2025 — Software Supply Chain Failures
39
High / Critical
A05:2025 — Injection
10
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Top priorities: 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; Resolve the 15 Banned license finding(s) in License Compliance — start with REDACTED (15); Resolve the 16 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (16).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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.
Test Quality: No assertions: should not allow excess properties
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 — 33
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 — 1316
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 — 1163
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 70 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 70 dimensions across the health lenses
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
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, 2435 of 2512 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.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `integrations/react/next-15/app/make-query-client.ts`, `integrations/react/next-16/app/make-query-client.ts`, `knip.ts`, `packages/eslint-plugin-query/src/index.ts`, `packages/query-core/src/mutation.ts`, … (+3 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.
AC6 Visual & motion safety — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> dev / > pnpm run watch / sh: 1: pnpm: not found" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> dev / > pnpm run watch / sh: 1: pnpm: not found" No runtime evidence was gathered.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, 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. The .NET and Node.js version checks are a different kind and still publish.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 85 further occurrence(s) are not listed individually; the score already reflects all 125.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 22 further occurrence(s) are not listed individually; the score already reflects all 62.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 357 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 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.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
+ 18 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with Explorer.Explorer (cyclomatic 79), Devtools.ContentView (cyclomatic 75), Devtools.DraggablePanel (cyclomatic 51). — 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 4 together lifts Cyclomatic Complexity from 6.3 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 29 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 30 down to 30 or less in Cognitive Complexity — start with Devtools.DraggablePanel (cognitive 73), Explorer.Explorer (cognitive 72), Devtools.ContentView (cognitive 70). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 5.7 to about 7.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.9 / 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.
Resolve the 22 FunctionTooLong finding(s) in God Classes — start with Devtools.tsx (6), Explorer.tsx (2), default-import.output.tsx (2). — One of this dimension's main actionable groups (22 warning-level).
Resolve the 8 FileTooLong finding(s) in God Classes — start with queryClient.ts (2), Devtools.tsx, index.tsx. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 MethodTooLong finding(s) in God Classes — start with query.ts, queryObserver.ts, mutation.ts. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.2 / 10Stronggated by 4 serious findings✓ 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.
42 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 39 of the 42 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @tanstack/react-query · ×4
What to do
Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
19 skipped (19 with a documented reason), 1929 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4984 tests (1 harness-style project(s) excluded from the assertion penalty).
No assertions: should re-export core query filters · ×941packages/vue-query/src/__tests__/filterTypes.test-d.ts:9
No direct assertions: should omit a string key and reject one the object does not have · ×988packages/query-core/src/__tests__/OmitKeyof.test-d.ts:5
Mock-dominated test: should catch and log errors in `persistClient` · ×9packages/query-persist-client-core/src/__tests__/persist.test.ts:46
Resolve the 988 No direct assertions finding(s) in Test Quality — start with queryClient.test-d.tsx (131), queryObserver.test-d.tsx (130), infiniteQueryObserver.test-d.tsx (90). — One of this dimension's main actionable groups (988 recommendation-level).
Resolve the 941 No assertions finding(s) in Test Quality — start with queryOptions.test-d.ts (85), queryOptions.test-d.tsx (77), useQuery.test-d.tsx (72). — One of this dimension's main actionable groups (941 warning-level).
Resolve the 9 Mock-dominated test finding(s) in Test Quality — start with queryClient.test.tsx (4), queryObserver.test.tsx (2), persist.test.ts. — One of this dimension's main actionable groups (9 recommendation-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
52 outdated direct production npm dependency(ies) of 97 graded, 4 pinning defect(s), across 199 REDACTED (47 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 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.
Deprecated: eslint · ×4REDACTED:64
One package at two majors across the workspace: next · ×4
Resolve the 16 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (16). — One of this dimension's main actionable groups (16 recommendation-level).
Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
15 of 1671 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1671 package(s) this repository's committed lockfile installs for a consumer — its 97 production, optional and peer dependency(ies), across 47 product REDACTED manifest(s), and everything those install in turn. Its 1251 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.
Resolve the 15 Banned license finding(s) in License Compliance — start with REDACTED (15). — One of this dimension's main actionable groups (15 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with useBaseQuery.ts (2), Devtools.tsx, queryObserver.ts. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with index.tsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.2 / 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.
36 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 198 of the 535 production source files in this repository: 335 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
What to do
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.
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.
19 deducted task-comment markers across 85375 LoC (0.0/KLoC) → score 10.0. 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.
Resolve the 18 TodoComment finding(s) in Explicit Debt — start with useInfiniteQuery.test-d.tsx (9), createInfiniteQuery.test-d.ts (4), createInfiniteQueryController.test-d.ts (2). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with vueQueryPlugin.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 322 document(s) read across 47 unit(s).
Documentation: no build, run or usage example · ×4packages/preact-query/README.md:1
What to do
Resolve the 4 Documentation finding(s) in Documentation Quality — start with README.md (4). — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
1 naming inconsistencies among 93 declarations measured against a convention their peers follow.
`usePokemonID` spells `ID` where 92 names in the project spell it `Id`examples/solid/ssr-astro/src/components/SolidApp.tsx:26
What to do
Resolve the 1 `usePokemonID` spells `ID` where 92 names in the project spell it `Id` finding(s) in Naming Consistency — start with SolidApp.tsx. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
52 domain type(s) cross context boundaries across 105 contexts; they are measured and withheld (not published, not scored). Contexts: algolia, angular-query-experimental, angular-query-persist-client, auto-refetching, auto-refetching-nextjs-pages-router, auto-refetching-nuxt4, auto-refetching-solid-start2, auto-refetching-sveltekit, basic, basic-angular-router, basic-graphql-request, basic-persister and 93 more.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×9packages/angular-query-experimental/src/devtools-panel/types.ts:6
What to do
Resolve the 17 redundant comment finding(s) in Comment Value — start with useInfiniteQuery.test.tsx (3), useQueries.test-d.tsx (3), key-transformation.cjs (3). — One of this dimension's main actionable groups (17 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
27 % of calls cross a namespace and 0 % go through an interface, but 63 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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.
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).
11 finding(s): 0 critical, 4 high, 7 medium, 0 low. semgrep hit a parse error in 23 file(s) — `examples/svelte/contacts-sveltekit/src/routes/(app)/contacts/[contactId]/+page.server.ts` (lines 5–16), `examples/svelte/contacts-sveltekit/src/routes/(app)/contacts/[contactId]/edit/+page.server.ts` (lines 5–17), `examples/svelte/contacts-sveltekit/src/routes/(app)/contacts/new/+page.server.ts` (lines 5–17), `integrations/react/next-15/app/make-query-client.ts` (lines 6–13), `integrations/react/next-16/app/make-query-client.ts` (lines 6–13), … (+18 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.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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.
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.
7 of 200 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs. Counted over 200 of the 535 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
Resolve the 1 Change coupling finding(s) in Change Coupling — start with devtools.tsx. — 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.
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.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 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.
Do you agree with this assessment?
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.
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>. — integrations/lit/vite/index.html:2
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — integrations/svelte/sveltekit-2/src/app.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
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.
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.
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.
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.
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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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 — server actions ("use server") in integrations/react/next-16/app/_action.ts (integrations/react/next-16/app/_action.ts:1) — 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. — integrations/react/next-16/app/_action.ts:1
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.
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.
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
docs/framework/react/guides/mutations.md names React 16, but the manifest declares `react` ^19.3.1. 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/framework/react/guides/mutations.md:66
What to do
Reconcile the README with reality: docs/framework/react/guides/mutations.md names React 16, but the manifest declares `react` ^19.3.1.
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.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 378 JavaScript/TypeScript production file(s) this check read across 46 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/autofix.yml:4
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
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.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
integrations/react/next-15/ and integrations/react/next-16/ are near-verbatim copies of each other: 9 files are byte-identical under the same relative paths (~277 lines; the trees hold 12 and 12 files). That is one structural fact, not 9 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — integrations/react/next-15/app/make-query-client.ts:1
111 duplicated blocks under packages/ have copies in at least two of the sibling directories angular-query-experimental, angular-query-persist-client, eslint-plugin-query, lit-query, preact-query, preact-query-devtools (+19 more sibling(s) not listed) — 38 of them are reported below, and 73 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 111 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 111 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 111 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/preact-query/src/useQueries.ts:6
7 duplicated blocks under integrations/react/ have copies in at least two of the sibling directories next-14, next-15, next-16, vite, webpack-4, webpack-5 — 6 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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. — integrations/react/next-15/app/make-query-client.ts:21
packages/lit-query/src/createInfiniteQueryController.ts:29 · packages/lit-query/src/createQueryController.ts:29 — the two spans are one implementation copied and then locally edited — 1111 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/lit-query/src/createInfiniteQueryController.ts:29
packages/preact-query/src/useQueries.ts:6 · packages/react-query/src/useQueries.ts:9 — these 2 files are line-for-line copies of one another — 181 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/preact-query/src/useQueries.ts:6
packages/preact-query/src/types.ts:2 · packages/react-query/src/types.ts:3 — these 2 files are line-for-line copies of one another — 143 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/preact-query/src/types.ts:2
packages/preact-query/src/useSuspenseQueries.ts:1 · packages/react-query/src/useSuspenseQueries.ts:2 — these 2 files are line-for-line copies of one another — 129 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/preact-query/src/useSuspenseQueries.ts:1
packages/angular-query-experimental/src/inject-queries.ts:39 · packages/svelte-query/src/createQueries.svelte.ts:24 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/angular-query-experimental/src/inject-queries.ts:39
packages/query-devtools/src/TanstackQueryDevtools.tsx:1 · packages/query-devtools/src/TanstackQueryDevtoolsPanel.tsx:1 — these 2 files are line-for-line copies of one another — 96 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/query-devtools/src/TanstackQueryDevtools.tsx:1
packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs:14 · packages/query-codemods/src/v5/remove-overloads/transformers/query-fn-aware-usage-transformer.cjs:12 — the two spans are one implementation copied and then locally edited — 430 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/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs:14
packages/query-core/src/types.ts:1078 · packages/query-core/src/types.ts:1444 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/query-core/src/types.ts:1078
packages/angular-query-experimental/src/infinite-query-options.ts:24 · packages/preact-query/src/infiniteQueryOptions.ts:25 · packages/react-query/src/infiniteQueryOptions.ts:24 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/angular-query-experimental/src/infinite-query-options.ts:24
packages/query-core/src/queryClient.ts:286 · packages/vue-query/src/queryClient.ts:168 — the two spans are one implementation copied and then locally edited — 354 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/query-core/src/queryClient.ts:286
packages/preact-query/src/errorBoundaryUtils.ts:21 · packages/react-query/src/errorBoundaryUtils.ts:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/preact-query/src/errorBoundaryUtils.ts:21
packages/preact-query/src/useMutationState.ts:3 · packages/react-query/src/useMutationState.ts:4 — these 2 files are line-for-line copies of one another — 63 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/preact-query/src/useMutationState.ts:3
packages/preact-query/src/infiniteQueryOptions.ts:1 · packages/react-query/src/infiniteQueryOptions.ts:1 — these 2 files are line-for-line copies of one another — 59 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/preact-query/src/infiniteQueryOptions.ts:1
packages/preact-query/src/HydrationBoundary.tsx:17 · packages/react-query/src/HydrationBoundary.tsx:16 — the two spans are one implementation copied and then locally edited — 306 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/preact-query/src/HydrationBoundary.tsx:17
packages/preact-query/src/queryOptions.ts:1 · packages/react-query/src/queryOptions.ts:1 — these 2 files are line-for-line copies of one another — 57 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/preact-query/src/queryOptions.ts:1
packages/preact-query/src/suspense.ts:19 · packages/react-query/src/suspense.ts:18 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/preact-query/src/suspense.ts:19
packages/angular-query-experimental/src/query-options.ts:22 · packages/preact-query/src/queryOptions.ts:23 · packages/react-query/src/queryOptions.ts:22 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/angular-query-experimental/src/query-options.ts:22
packages/preact-query/src/useBaseQuery.ts:1 · packages/react-query/src/useBaseQuery.ts:4 — these 2 files are line-for-line copies of one another — 53 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/preact-query/src/useBaseQuery.ts:1
packages/lit-query/src/useIsFetching.ts:1 · packages/lit-query/src/useIsMutating.ts:1 — these 2 files are line-for-line copies of one another — 51 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/lit-query/src/useIsFetching.ts:1
packages/vue-query/src/usePrefetchInfiniteQuery.ts:38 · packages/vue-query/src/usePrefetchQuery.ts:39 — the two spans are one implementation copied and then locally edited — 199 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/vue-query/src/usePrefetchInfiniteQuery.ts:38
packages/preact-query/src/useMutation.ts:188 · packages/react-query/src/useMutation.ts:187 — the two spans are one implementation copied and then locally edited — 249 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/preact-query/src/useMutation.ts:188
packages/angular-query-experimental/src/create-base-query.ts:90 · packages/angular-query-experimental/src/inject-mutation.ts:241 — the two spans are one implementation copied and then locally edited — 184 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/angular-query-experimental/src/create-base-query.ts:90
packages/angular-query-experimental/src/types.ts:212 · packages/preact-query/src/types.ts:385 · packages/react-query/src/types.ts:386 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/angular-query-experimental/src/types.ts:212
packages/lit-query/src/createQueriesController.ts:120 · packages/solid-query/src/useQueries.ts:118 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/lit-query/src/createQueriesController.ts:120
packages/react-query-devtools/src/ReactQueryDevtools.tsx:54 · packages/react-query-devtools/src/ReactQueryDevtoolsPanel.tsx:45 — the two spans are one implementation copied and then locally edited — 192 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-query-devtools/src/ReactQueryDevtools.tsx:54
packages/solid-query-persist-client/tsdown.config.ts:5 · packages/solid-query/tsdown.config.ts:5 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/solid-query-persist-client/tsdown.config.ts:5
packages/lit-query/src/useIsFetching.ts:60 · packages/lit-query/src/useIsMutating.ts:60 · packages/lit-query/src/useMutationState.ts:79 — the 3 copies are spread across 3 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/lit-query/src/useIsFetching.ts:60
packages/query-devtools/src/Devtools.tsx:2628 · packages/query-devtools/src/Devtools.tsx:2668 — all 2 copies are in the same file, and the CITED SPAN is a DECLARATION HEADER — the name, parameter list with its constraints and defaults, and base-type clause of a declaration — rather than statements inside a body. A header cannot be lifted into a helper: there is no expression position for a call to stand in, and the copies are frequently required to match, because one declaration passes its parameters straight through to the other. So the move is not extraction. Give the repeated pieces names — factor a long constraint or base-type expression into one named type both declarations refer to — and where the headers must stay identical, derive one from the other (a shared base declaration, or a single alias that spells the parameter set once) so that changing it once changes both. Where the language offers neither, treat the two as a pair that must be edited together: they drift apart the first time only one of them is changed, which is why this is reported. — packages/query-devtools/src/Devtools.tsx:2628
packages/svelte-query-devtools/vite.config.ts:7 · packages/svelte-query-persist-client/vite.config.ts:7 · packages/svelte-query/vite.config.ts:7 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/svelte-query-devtools/vite.config.ts:7
integrations/react/next-15/app/make-query-client.ts:21 · integrations/react/next-16/app/make-query-client.ts:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — integrations/react/next-15/app/make-query-client.ts:21
packages/preact-query/src/useSuspenseInfiniteQuery.ts:122 · packages/react-query/src/useSuspenseInfiniteQuery.ts:102 — 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/preact-query/src/useSuspenseInfiniteQuery.ts:122
oxlint.config.ts:230 · packages/angular-query-experimental/root.oxlint.config.ts:230 · packages/angular-query-persist-client/root.oxlint.config.ts:230 · packages/eslint-plugin-query/root.oxlint.config.ts:230 · +23 more site(s) not listed — the 27 copies are spread across 27 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — oxlint.config.ts:230
packages/preact-query-persist-client/src/PersistQueryClientProvider.tsx:44 · packages/react-query-persist-client/src/PersistQueryClientProvider.tsx:38 — the two spans are one implementation copied and then locally edited — 245 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/preact-query-persist-client/src/PersistQueryClientProvider.tsx:44
integrations/react/next-15/app/page.tsx:9 · integrations/react/next-16/app/page.tsx:9 — 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. — integrations/react/next-15/app/page.tsx:9
packages/solid-query/src/useMutationState.ts:24 · packages/vue-query/src/useMutationState.ts:98 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/solid-query/src/useMutationState.ts:24
packages/lit-query/src/createInfiniteQueryController.ts:69 · packages/lit-query/src/createQueriesController.ts:224 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/lit-query/src/createInfiniteQueryController.ts:69
packages/query-devtools/src/Devtools.tsx:1318 · packages/query-devtools/src/Devtools.tsx:1400 · packages/query-devtools/src/Devtools.tsx:1470 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — packages/query-devtools/src/Devtools.tsx:1318
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.
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.
knip.ts:1 reaches into another package with a relative path (./packages/angular-query-experimental/package.json) — import the package by name instead. — knip.ts:1
knip.ts:2 reaches into another package with a relative path (./packages/react-query/package.json) — import the package by name instead. — knip.ts:2
knip.ts:3 reaches into another package with a relative path (./packages/react-query-devtools/package.json) — import the package by name instead. — knip.ts:3
knip.ts:4 reaches into another package with a relative path (./packages/react-query-next-experimental/package.json) — import the package by name instead. — knip.ts:4
knip.ts:5 reaches into another package with a relative path (./packages/react-query-persist-client/package.json) — import the package by name instead. — knip.ts:5
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.
ContentView has cyclomatic complexity 30 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/query-devtools/src/Devtools.tsx:772
addReferenceDetails has cyclomatic complexity 28 and cognitive complexity 89; 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:712
Explorer has cyclomatic complexity 23 and cognitive complexity 17; 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/query-devtools/src/Explorer.tsx:468
replaceEqualDeep has cyclomatic complexity 22 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — packages/query-core/src/utils.ts:388, packages/query-core/src/utils.ts:389
(anonymous) has cyclomatic complexity 22 and cognitive complexity 20; 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/query-core/src/hydration.ts:330
getNativeObjectType has cyclomatic complexity 20 and cognitive complexity 19; 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/query-devtools/src/nativeObjectType.ts:32
CallExpression has cyclomatic complexity 18 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/eslint-plugin-query/src/rules/prefer-query-options/prefer-query-options.rule.ts:105
DraggablePanel has cyclomatic complexity 18 and cognitive complexity 17; 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/query-devtools/src/Devtools.tsx:498
visit has cyclomatic complexity 17 and cognitive complexity 13; 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/eslint-plugin-query/src/rules/exhaustive-deps/exhaustive-deps.utils.ts:208
replacer has cyclomatic complexity 16 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/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs:68
matchQuery has cyclomatic complexity 16 and cognitive complexity 20; 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/query-core/src/utils.ts:205
(anonymous) has cyclomatic complexity 15 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/query-devtools/src/Devtools.tsx:706
fetch has cyclomatic complexity 15 and cognitive complexity 17; 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/query-core/src/query.ts:709
declaredTypeLabel has cyclomatic complexity 15 and cognitive complexity 16; 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:393
partialMatchKey has cyclomatic complexity 14 and cognitive complexity 23; 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. (×2) — packages/query-core/src/utils.ts:343, packages/query-core/src/utils.ts:344
(anonymous) has cyclomatic complexity 14 and cognitive complexity 18; 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/query-devtools/src/utils.tsx:248
CallExpression has cyclomatic complexity 14 and cognitive complexity 17; 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/eslint-plugin-query/src/rules/no-rest-destructuring/no-rest-destructuring.rule.ts:40
isRelevantReference has cyclomatic complexity 14 and cognitive complexity 16; 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/eslint-plugin-query/src/rules/exhaustive-deps/exhaustive-deps.utils.ts:6
(anonymous) has cyclomatic complexity 13 and cognitive complexity 20; 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. (×2) — packages/preact-query/src/HydrationBoundary.tsx:114, packages/react-query/src/HydrationBoundary.tsx:114
execute has cyclomatic complexity 13 and cognitive complexity 19; 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/query-core/src/mutation.ts:301
(anonymous) has cyclomatic complexity 13 and cognitive complexity 14; 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/query-devtools/src/Explorer.tsx:547
(anonymous) has cyclomatic complexity 13 and cognitive complexity 12; 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/query-devtools/src/Explorer.tsx:499
visit has cyclomatic complexity 13 and cognitive complexity 12; 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/query-devtools/src/explorerSearch.ts:163
restoreQueries has cyclomatic complexity 12 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/query-persist-client-core/src/createPersister.ts:394
(anonymous) has cyclomatic complexity 12 and cognitive complexity 14; 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/query-core/src/streamedQuery.ts:87
useBaseQuery has cyclomatic complexity 12 and cognitive complexity 13; 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. (×2) — packages/preact-query/src/useBaseQuery.ts:39, packages/react-query/src/useBaseQuery.ts:39
(anonymous) has cyclomatic complexity 12 and cognitive complexity 11; 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/query-core/src/retryer.ts:244
searchEntries has cyclomatic complexity 12 and cognitive complexity 10; 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/query-devtools/src/explorerSearch.ts:58
removeQueries has cyclomatic complexity 11 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/query-persist-client-core/src/createPersister.ts:453
fetchFn has cyclomatic complexity 11 and cognitive complexity 20; 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/query-core/src/infiniteQueryBehavior.ts:38
(anonymous) has cyclomatic complexity 11 and cognitive complexity 20; 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/query-core/src/query.ts:877
install has cyclomatic complexity 11 and cognitive complexity 18; 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/vue-query/src/vueQueryPlugin.ts:76
(anonymous) has cyclomatic complexity 11 and cognitive complexity 17; 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/query-devtools/src/utils.tsx:326
(anonymous) has cyclomatic complexity 11 and cognitive complexity 11; 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/query-core/src/queryObserver.ts:787
Do you agree with this assessment?
R3 · Large Files7.1 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
packages/query-devtools/src/Devtools.tsx has 3700 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/query-devtools/src/Devtools.tsx:1
packages/query-core/src/types.ts has 2344 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/query-core/src/types.ts:1
packages/query-devtools/src/icons/index.tsx has 1413 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/query-devtools/src/icons/index.tsx:1
packages/query-core/src/queryClient.ts has 1099 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/query-core/src/queryClient.ts:1
REDACTED has 1041 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/query-core/src/query.ts has 1026 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/query-core/src/query.ts:1
packages/query-devtools/src/Explorer.tsx has 978 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/query-devtools/src/Explorer.tsx:1
packages/query-core/src/queryObserver.ts has 875 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/query-core/src/queryObserver.ts:1
packages/vue-query/src/queryClient.ts has 715 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/vue-query/src/queryClient.ts:1
packages/query-core/src/utils.ts has 679 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/query-core/src/utils.ts:1
packages/lit-query/src/createQueriesController.ts has 654 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/lit-query/src/createQueriesController.ts:1
packages/preact-query/src/useSuspenseQueries.ts 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/preact-query/src/useSuspenseQueries.ts:1
packages/query-core/src/mutation.ts has 515 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/query-core/src/mutation.ts:1
packages/react-query/src/useSuspenseQueries.ts has 514 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-query/src/useSuspenseQueries.ts:1
packages/query-persist-client-core/src/createPersister.ts has 471 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/query-persist-client-core/src/createPersister.ts:1
packages/react-query/src/useQueries.ts has 469 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-query/src/useQueries.ts:1
packages/preact-query/src/types.ts has 466 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/preact-query/src/types.ts:1
packages/react-query/src/types.ts has 466 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-query/src/types.ts:1
packages/angular-query-experimental/src/inject-queries.ts has 459 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/angular-query-experimental/src/inject-queries.ts:1
packages/vue-query/src/useQueries.ts has 453 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/vue-query/src/useQueries.ts:1
packages/eslint-plugin-query/src/rules/exhaustive-deps/exhaustive-deps.utils.ts has 431 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/eslint-plugin-query/src/rules/exhaustive-deps/exhaustive-deps.utils.ts:1
packages/angular-query-experimental/src/types.ts has 417 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/angular-query-experimental/src/types.ts:1
packages/vue-query/src/queryOptions.ts has 417 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/vue-query/src/queryOptions.ts:1
packages/preact-query/src/useQueries.ts has 416 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/preact-query/src/useQueries.ts:1
packages/solid-query/src/useQueries.ts has 406 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/solid-query/src/useQueries.ts:1
packages/query-core/src/hydration.ts has 404 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/query-core/src/hydration.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage8.0 / 10Strong✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
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) — packages/react-query-next-experimental/src/HydrationStreamProvider.tsx:1, packages/query-async-storage-persister/src/index.ts:1, packages/angular-query-experimental/scripts/prepack.js:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
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.
Do you agree with this assessment?
R7 · Dead Code8.9 / 10Strong✓ 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.
2 file(s) (~20 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — integrations/react/nodenext
2 file(s) (~42 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — integrations/solid/astro-7
2 file(s) (~23 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — integrations/vue/declaration-emit
Unreachable from the 348 application, 168 tooling and 368 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 (348 application, 168 tooling, 368 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 (×29) — packages/query-codemods/src/v5/remove-overloads/__testfixtures__/default-import.output.tsx, packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.output.tsx, packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.input.tsx, …
no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/query-codemods/src/v5/remove-overloads/remove-overloads.cjs) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs, packages/query-codemods/src/v5/remove-overloads/transformers/query-fn-aware-usage-transformer.cjs
no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/query-codemods/src/v4/key-transformation.cjs, packages/query-codemods/src/v5/is-loading/is-loading.cjs, packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/query-codemods/src/utils/index.cjs
no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/query-codemods/src/v4/key-transformation.cjs) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/query-codemods/src/v4/utils/replacers/key-replacer.cjs
no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/query-codemods/src/v4/key-transformation.cjs, packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/query-codemods/src/utils/transformers/query-cache-transformer.cjs
no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs, packages/query-codemods/src/v5/remove-overloads/transformers/query-fn-aware-usage-transformer.cjs) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/query-codemods/src/v5/remove-overloads/utils/index.cjs
no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (packages/query-codemods/src/v4/key-transformation.cjs, packages/query-codemods/src/v5/is-loading/is-loading.cjs, packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/query-codemods/src/utils/transformers/query-client-transformer.cjs
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in the root REDACTED 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. (×2)
Declared in integrations/angular/cli-22/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 packages/angular-query-experimental/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 packages/angular-query-persist-client/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.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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.
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.
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.
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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`cloneDeep` is exported, takes a document from its caller (line 92) and hands it to `_cloneDeep`, which calls itself at line 68 (`_cloneDeep`) with a piece of `value` (and at line 74) — and nowhere in `_cloneDeep` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `_cloneDeep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/vue-query/src/utils.ts:68
`updateNestedDataByPath` is exported and takes `oldData: unknown` from its caller, and it calls itself at line 265 (`updateNestedDataByPath`) with a piece of `oldData` (and at line 290, line 305) — and nowhere in `updateNestedDataByPath` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `updateNestedDataByPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/query-devtools/src/utils.tsx:265
`deleteNestedDataByPath` is exported and takes `oldData: unknown` from its caller, and it calls itself at line 339 (`deleteNestedDataByPath`) with a piece of `oldData` (and at line 361, line 377) — and nowhere in `deleteNestedDataByPath` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deleteNestedDataByPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/query-devtools/src/utils.tsx:339
`partialMatchKey` is exported and takes `a: any` from its caller, and it calls itself at line 357 (`partialMatchKey`) with a piece of `a` (and at line 366) — and nowhere in `partialMatchKey` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `partialMatchKey` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/query-core/src/utils.ts:357
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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 0/8 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`. (×4) — packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.input.tsx:11, packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.output.tsx:11, packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.input.tsx:16, …
`queryFn` 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 })`. (×4) — integrations/react/next-16/app/client-component.tsx:10, integrations/react/next-16/app/page.tsx:15, integrations/react/next-15/app/client-component.tsx:10, …
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
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.
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.
Do you agree with this assessment?
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.
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.
`.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. (×3) — packages/vue-query/src/useMutation.ts:273, packages/query-devtools/src/Devtools.tsx:2048, packages/lit-query/src/createMutationController.ts:190
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. (×2) — packages/svelte-query/src/createBaseQuery.svelte.ts:108, packages/query-async-storage-persister/src/asyncThrottle.ts:48
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
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.
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.
193/200 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~1.4 `!` null assertions per 1k TypeScript source lines — 82 assertion(s) across the 57626 source line(s) of the 339 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/query-devtools/src/Devtools.tsx (27), packages/query-devtools/src/Explorer.tsx (10), packages/solid-query/src/useQueries.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
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 `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 8 of 55 WCAG 2.2 Level A/AA success criteria (15%; ≈16% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 47 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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.
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.
SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 22 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 — 56 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.
AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
AX1 Captive dependencies — Not applicable: Angular's root injector cannot see a component-level provider, so a root service asking for one fails with NullInjectorError instead of capturing it.
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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> dev / > pnpm run watch / sh: 1: pnpm: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
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 — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — Not assessed: 357 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — 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.
Banned license: @img/sharp-libvips-darwin-arm64 REDACTED:9490— `@img/sharp-libvips-darwin-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-darwin-x64 REDACTED:9495— `@img/sharp-libvips-darwin-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm REDACTED:9506— `@img/sharp-libvips-linux-arm` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm64 REDACTED:9500— `@img/sharp-libvips-linux-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-ppc64 REDACTED:9512— `@img/sharp-libvips-linux-ppc64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-riscv64 REDACTED:9518— `@img/sharp-libvips-linux-riscv64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-s390x REDACTED:9524— `@img/sharp-libvips-linux-s390x` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-x64 REDACTED:9530— `@img/sharp-libvips-linux-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-arm64 REDACTED:9536— `@img/sharp-libvips-linuxmusl-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-x64 REDACTED:9542— `@img/sharp-libvips-linuxmusl-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-wasm32 REDACTED:9604— `@img/sharp-wasm32` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later AND MIT`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-arm64 REDACTED:9613— `@img/sharp-win32-arm64` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-ia32 REDACTED:9619— `@img/sharp-win32-ia32` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-x64 REDACTED:9625— `@img/sharp-win32-x64` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: ua-parser-js REDACTED:21553— `ua-parser-js` 1.0.41 is published on registry.npmjs.org under `AGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> integrations/svelte/sveltekit-2/src/app.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
No assertions: should re-export core query filters packages/vue-query/src/__tests__/filterTypes.test-d.ts:9— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should re-export core mutation filters packages/vue-query/src/__tests__/filterTypes.test-d.ts:16— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should not allow excess properties packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:20— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should infer types for callbacks packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when passed to useInfiniteQuery packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:48— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should keep initialData required when it is defined packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:64— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should have defined data when passed to useInfiniteQuery with defined initialData packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:76— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should keep data possibly undefined when initialData is a ternary that can be undefined packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when passed to infiniteQuery packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:111— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when passed to infiniteQuery with select packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:128— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should tag the queryKey with the result type of the QueryFn packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:146— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should tag the queryKey even if no promise is returned packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:158— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should tag the queryKey with the result type of the QueryFn if select is used packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:170— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should return the proper type when passed to getQueryData packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:183— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should properly type when passed to setQueryData packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:200— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should not allow excess properties packages/vue-query/src/__tests__/mutationOptions.test-d.ts:16— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should infer types for callbacks packages/vue-query/src/__tests__/mutationOptions.test-d.ts:28— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should infer types for onError callback packages/vue-query/src/__tests__/mutationOptions.test-d.ts:38— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should infer types for variables packages/vue-query/src/__tests__/mutationOptions.test-d.ts:50— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should infer result type correctly packages/vue-query/src/__tests__/mutationOptions.test-d.ts:60— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should infer context type correctly packages/vue-query/src/__tests__/mutationOptions.test-d.ts:73— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should error if mutationFn return type mismatches TData packages/vue-query/src/__tests__/mutationOptions.test-d.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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should allow mutationKey to be omitted packages/vue-query/src/__tests__/mutationOptions.test-d.ts:104— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should infer all types when not explicitly provided packages/vue-query/src/__tests__/mutationOptions.test-d.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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when used with useMutation packages/vue-query/src/__tests__/mutationOptions.test-d.ts:143— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 916 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file packages/react-query-next-experimental/src/HydrationStreamProvider.tsx: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/query-async-storage-persister/src/index.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/angular-query-experimental/scripts/prepack.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react-query-next-experimental/src/ReactQueryStreamedHydration.tsx: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/eslint-plugin-query/src/index.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 knip.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 integrations/lit/vite/src/main.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 integrations/react/next-15/app/make-query-client.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 integrations/react/next-16/app/make-query-client.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 integrations/react/next-15/app/page.tsx: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 integrations/react/next-16/app/page.tsx: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 integrations/react/next-15/app/providers.tsx: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 integrations/react/next-16/app/providers.tsx: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 integrations/react/next-15/app/client-component.tsx: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 integrations/react/next-16/app/client-component.tsx: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 integrations/solid/astro-7/src/components/App.tsx: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 integrations/solid/solid-start-2/src/app.tsx: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 integrations/vue/nuxt-3/plugins/vue-query.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 integrations/vue/nuxt-4/app/plugins/vue-query.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-query-next-experimental/src/htmlescape.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 integrations/angular/cli-22/src/app/app.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 integrations/react/next-14/app/client-component.tsx: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 integrations/react/webpack-4/src/App.tsx: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 integrations/react/webpack-5/src/App.tsx: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 integrations/preact/vite/src/App.tsx: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.
FunctionTooLong: Devtools.stylesFactory packages/query-devtools/src/Devtools.tsx:2839— FunctionTooLong — stylesFactory runs 929 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 829 over it, 9.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.TanstackLogo packages/query-devtools/src/icons/index.tsx:623— FunctionTooLong — TanstackLogo runs 814 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 714 over it, 8.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: Devtools.ContentView packages/query-devtools/src/Devtools.tsx:772— FunctionTooLong — ContentView runs 679 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 579 over it, 6.79× 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: Devtools.QueryDetails packages/query-devtools/src/Devtools.tsx:1979— FunctionTooLong — QueryDetails runs 443 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 343 over it, 4.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Explorer.Explorer packages/query-devtools/src/Explorer.tsx:468— FunctionTooLong — Explorer runs 326 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 226 over it, 3.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: createPersister.experimental_createQueryPersister packages/query-persist-client-core/src/createPersister.ts:137— FunctionTooLong — experimental_createQueryPersister runs 203 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 103 over it, 2.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: Devtools.DraggablePanel packages/query-devtools/src/Devtools.tsx:498— FunctionTooLong — DraggablePanel runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× 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: default-import.output.WithKnownParameters packages/query-codemods/src/v5/remove-overloads/__testfixtures__/default-import.output.tsx:10— FunctionTooLong — WithKnownParameters runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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: default-import.output.WithIdentifiers packages/query-codemods/src/v5/remove-overloads/__testfixtures__/default-import.output.tsx:253— FunctionTooLong — WithIdentifiers runs 185 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× 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: Devtools.MutationDetails packages/query-devtools/src/Devtools.tsx:2513— FunctionTooLong — MutationDetails 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: useBaseQuery.useBaseQuery packages/solid-query/src/useBaseQuery.ts:124— FunctionTooLong — useBaseQuery runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: devtools.setupDevtools packages/vue-query/src/devtools/devtools.ts:23— FunctionTooLong — setupDevtools runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.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: Explorer.stylesFactory packages/query-devtools/src/Explorer.tsx:856— FunctionTooLong — stylesFactory runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: filter-aware-usage-transformer.transformFilterAwareUsages packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs:14— FunctionTooLong — transformFilterAwareUsages runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.default packages/query-codemods/src/utils/index.cjs:1— FunctionTooLong — default 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: useBaseQuery.useBaseQuery packages/vue-query/src/useBaseQuery.ts:112— FunctionTooLong — useBaseQuery runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: Devtools.Devtools packages/query-devtools/src/Devtools.tsx:198— FunctionTooLong — Devtools runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: keep-previous-data.transformUsages packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs:13— FunctionTooLong — transformUsages runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× 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: useQueries.useQueries packages/solid-query/src/useQueries.ts:272— FunctionTooLong — useQueries runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× 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: is-loading.transformUsages packages/query-codemods/src/v5/is-loading/is-loading.cjs:15— FunctionTooLong — transformUsages runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: retryer.createRetryer packages/query-core/src/retryer.ts:149— FunctionTooLong — createRetryer runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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: query-fn-aware-usage-transformer.transformQueryFnAwareUsages packages/query-codemods/src/v5/remove-overloads/transformers/query-fn-aware-usage-transformer.cjs:12— FunctionTooLong — transformQueryFnAwareUsages 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.
TodoComment packages/vue-query/src/__tests__/useInfiniteQuery.test-d.tsx:20— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/vue-query/src/__tests__/useInfiniteQuery.test-d.tsx:68— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/svelte-query/tests/createInfiniteQuery/createInfiniteQuery.test-d.ts:68— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/svelte-query/tests/createInfiniteQuery/createInfiniteQuery.test-d.ts:119— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/svelte-query/tests/createInfiniteQuery/createInfiniteQuery.test-d.ts:177— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/svelte-query/tests/createInfiniteQuery/createInfiniteQuery.test-d.ts:220— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/solid-query/src/__tests__/useInfiniteQuery.test-d.tsx:100— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/solid-query/src/__tests__/useInfiniteQuery.test-d.tsx:158— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/solid-query/src/__tests__/useInfiniteQuery.test-d.tsx:201— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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-query/src/__tests__/useInfiniteQuery.test-d.tsx:79— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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-query/src/__tests__/useInfiniteQuery.test-d.tsx:132— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/preact-query/src/__tests__/useInfiniteQuery.test-d.tsx:80— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/preact-query/src/__tests__/useInfiniteQuery.test-d.tsx:133— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/lit-query/src/__tests__/createInfiniteQueryController.test-d.ts:62— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/lit-query/src/__tests__/createInfiniteQueryController.test-d.ts:128— // TODO: Order of generics prevents pageParams to be typed correctly. Using `unknown` for now — 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/query-core/src/__tests__/queryClient.test-d.tsx:301— // TODO: types here are wrong and coming up undefined — 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/query-core/src/__tests__/queryClient.test-d.tsx:314— // TODO: types here are wrong and coming up undefined — 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/eslint-plugin-query/src/utils/detect-react-query-imports.ts:92— // TODO: canReportErrors() — 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×17
Hotspot: packages/query-devtools/src/Devtools.tsx packages/query-devtools/src/Devtools.tsx:772— packages/query-devtools/src/Devtools.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 75 in Devtools.ContentView at line 772. 4 of those changes were fix/bug commits, 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- packages/query-devtools/src/Devtools.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/query-core/src/queryObserver.ts packages/query-core/src/queryObserver.ts:589— packages/query-core/src/queryObserver.ts changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in QueryObserver.createResult at line 589. 6 of those changes were fix/bug commits, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- packages/query-core/src/queryObserver.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/query-core/src/query.ts packages/query-core/src/query.ts:709— packages/query-core/src/query.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in Query.fetch at line 709. 5 of those changes were fix/bug commits, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- packages/query-core/src/query.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/solid-query/src/useBaseQuery.ts packages/solid-query/src/useBaseQuery.ts:124— packages/solid-query/src/useBaseQuery.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in useBaseQuery.useBaseQuery at line 124. 3 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- packages/solid-query/src/useBaseQuery.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/vue-query/src/useBaseQuery.ts packages/vue-query/src/useBaseQuery.ts:112— packages/vue-query/src/useBaseQuery.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in useBaseQuery.useBaseQuery at line 112. 2 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- packages/vue-query/src/useBaseQuery.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/query-core/src/hydration.ts packages/query-core/src/hydration.ts:306— packages/query-core/src/hydration.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in hydration.hydrate at line 306. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- packages/query-core/src/hydration.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/query-core/src/retryer.ts packages/query-core/src/retryer.ts:223— packages/query-core/src/retryer.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in retryer.createRetryer.run at line 223. 2 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- packages/query-core/src/retryer.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/svelte-query/src/containers.svelte.ts packages/svelte-query/src/containers.svelte.ts:47— packages/svelte-query/src/containers.svelte.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in containers.svelte.createRawRef at line 47. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- packages/svelte-query/src/containers.svelte.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/query-broadcast-client-experimental/src/index.ts packages/query-broadcast-client-experimental/src/index.ts:66— packages/query-broadcast-client-experimental/src/index.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in index.broadcastQueryClient at line 66. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- packages/query-broadcast-client-experimental/src/index.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/query-core/src/infiniteQueryBehavior.ts packages/query-core/src/infiniteQueryBehavior.ts:30— packages/query-core/src/infiniteQueryBehavior.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in infiniteQueryBehavior.infiniteQueryBehavior.onFetch at line 30. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- packages/query-core/src/infiniteQueryBehavior.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.
FileTooLong: src/Devtools.tsx packages/query-devtools/src/Devtools.tsx— FileTooLong — 3164 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2664 over it, 6.33× 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: icons/index.tsx packages/query-devtools/src/icons/index.tsx— FileTooLong — 1259 significant lines (blank, comment-only and punctuation-only lines excluded), about 65% of them inside a single declaration: TanstackLogo (623-1487). The bar is 500 significant lines; this is 759 over it, 2.52× 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: src/types.ts packages/query-core/src/types.ts— FileTooLong — 926 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 426 over it, 1.85× 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: src/Explorer.tsx packages/query-devtools/src/Explorer.tsx— FileTooLong — 822 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 322 over it, 1.64× 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: src/queryClient.ts packages/vue-query/src/queryClient.ts— FileTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: QueryClient (67-746). The bar is 500 significant lines; this is 75 over it, 1.15× 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: src/queryClient.ts packages/query-core/src/queryClient.ts— FileTooLong — 529 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: QueryClient (78-1176). The bar is 500 significant lines; this is 29 over it, 1.06× 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: src/queryObserver.ts packages/query-core/src/queryObserver.ts— FileTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: QueryObserver (56-872). The bar is 500 significant lines; this is 24 over it, 1.05× 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: src/query.ts packages/query-core/src/query.ts— FileTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: Query (284-1035). The bar is 500 significant lines; this is 23 over it, 1.05× 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×8
Async function without AbortSignal: queryFn packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.input.tsx:11— `queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
Async function without AbortSignal: queryFn packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.output.tsx:11— `queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
Async function without AbortSignal: queryFn packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.input.tsx:16— `queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
Async function without AbortSignal: queryFn packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.output.tsx:17— `queryFn` awaits `axios.get(…)` 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: `axios.get(url, { signal })`.
Async function without AbortSignal: queryFn integrations/react/next-16/app/client-component.tsx:10— `queryFn` 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: queryFn integrations/react/next-16/app/page.tsx:15— `queryFn` 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: queryFn integrations/react/next-15/app/client-component.tsx:10— `queryFn` 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: queryFn integrations/react/next-15/app/page.tsx:15— `queryFn` 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 })`.
Dead file (~81 LoC) packages/query-codemods/src/v5/is-loading/__testfixtures__/default-import.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~81 LoC) packages/query-codemods/src/v5/is-loading/__testfixtures__/default-import.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~81 LoC) packages/query-codemods/src/v5/is-loading/__testfixtures__/named-import.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~81 LoC) packages/query-codemods/src/v5/is-loading/__testfixtures__/named-import.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~81 LoC) packages/query-codemods/src/v5/rename-properties/__testfixtures__/rename-cache-time.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~81 LoC) packages/query-codemods/src/v5/rename-properties/__testfixtures__/rename-cache-time.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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
Boundary violation [package:relative-cross-package] knip.ts:1— knip.ts:1 reaches into another package with a relative path (./packages/angular-query-experimental/package.json) — import the package by name instead.
Boundary violation [package:relative-cross-package] knip.ts:2— knip.ts:2 reaches into another package with a relative path (./packages/react-query/package.json) — import the package by name instead.
Boundary violation [package:relative-cross-package] knip.ts:3— knip.ts:3 reaches into another package with a relative path (./packages/react-query-devtools/package.json) — import the package by name instead.
Boundary violation [package:relative-cross-package] knip.ts:4— knip.ts:4 reaches into another package with a relative path (./packages/react-query-next-experimental/package.json) — import the package by name instead.
Boundary violation [package:relative-cross-package] knip.ts:5— knip.ts:5 reaches into another package with a relative path (./packages/react-query-persist-client/package.json) — import the package by name instead.
Swallowed exception (empty catch) packages/vue-query/src/useMutation.ts:273— `.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/svelte-query/src/createBaseQuery.svelte.ts:108— 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/query-devtools/src/Devtools.tsx:2048— `.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/query-async-storage-persister/src/asyncThrottle.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/lit-query/src/createMutationController.ts:190— `.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.
Deprecated: eslint REDACTED:64— eslint 9.39.5, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/eslint-plugin-query/package.json:65— eslint 9.39.5, declared in packages/eslint-plugin-query/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: vue packages/vue-query/package.json:82— vue 2.6.14 (declared as `vue2`), declared in packages/vue-query/package.json, is marked deprecated by its publisher: "Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: vue packages/vue-query/package.json:83— vue 2.7.16 (declared as `vue2.7`), declared in packages/vue-query/package.json, is marked deprecated by its publisher: "Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.". Replace it with the package or version that message names, or record why this one must stay.
D12 · Dependency Hygiene· One package at two majors across the workspace · ×4
One package at two majors across the workspace: next — `next` is maintained at 3 different major versions inside this one repository — major 14 in integrations/react/next-14/package.json; major 15 in integrations/react/next-15/package.json; major 16 in integrations/react/next-16/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.
One package at two majors across the workspace: nuxt — `nuxt` is maintained at 2 different major versions inside this one repository — major 3 in integrations/vue/nuxt-3/package.json; major 4 in integrations/vue/nuxt-4/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.
One package at two majors across the workspace: react — `react` is maintained at 2 different major versions inside this one repository — major 18 in integrations/react/next-14/package.json; major 19 in integrations/react/next-15/package.json, integrations/react/next-16/package.json, integrations/react/vite/package.json (+2 more). 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.
One package at two majors across the workspace: react-dom — `react-dom` is maintained at 2 different major versions inside this one repository — major 18 in integrations/react/next-14/package.json; major 19 in integrations/react/next-15/package.json, integrations/react/next-16/package.json, integrations/react/vite/package.json (+2 more). 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.
Off the main sequence: @tanstack/react-query — @tanstack/react-query: abstractness 0.00, instability 0.09, distance 0.91 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
Off the main sequence: @tanstack/solid-query — @tanstack/solid-query: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: @tanstack/vue-query — @tanstack/vue-query: abstractness 0.05, instability 0.17, distance 0.79 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: @tanstack/preact-query — @tanstack/preact-query: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×4
Recursive walk over a caller-supplied document has no depth cap packages/vue-query/src/utils.ts:68— `cloneDeep` is exported, takes a document from its caller (line 92) and hands it to `_cloneDeep`, which calls itself at line 68 (`_cloneDeep`) with a piece of `value` (and at line 74) — and nowhere in `_cloneDeep` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `_cloneDeep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/query-devtools/src/utils.tsx:265— `updateNestedDataByPath` is exported and takes `oldData: unknown` from its caller, and it calls itself at line 265 (`updateNestedDataByPath`) with a piece of `oldData` (and at line 290, line 305) — and nowhere in `updateNestedDataByPath` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `updateNestedDataByPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/query-devtools/src/utils.tsx:339— `deleteNestedDataByPath` is exported and takes `oldData: unknown` from its caller, and it calls itself at line 339 (`deleteNestedDataByPath`) with a piece of `oldData` (and at line 361, line 377) — and nowhere in `deleteNestedDataByPath` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deleteNestedDataByPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/query-core/src/utils.ts:357— `partialMatchKey` is exported and takes `a: any` from its caller, and it calls itself at line 357 (`partialMatchKey`) with a piece of `a` (and at line 366) — and nowhere in `partialMatchKey` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `partialMatchKey` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
MethodTooLong: Query.fetch packages/query-core/src/query.ts:709— MethodTooLong — fetch runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× 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.
MethodTooLong: QueryObserver.createResult packages/query-core/src/queryObserver.ts:589— MethodTooLong — createResult runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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.
MethodTooLong: Mutation.execute packages/query-core/src/mutation.ts:301— MethodTooLong — execute runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× 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.
ClassTooLong: QueryClient packages/vue-query/src/queryClient.ts:67— ClassTooLong — 525 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 125 over it, 1.31× 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.
ClassTooLong: QueryClient packages/query-core/src/queryClient.ts:78— ClassTooLong — 478 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 78 over it, 1.20× 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.
ClassTooLong: QueryObserver packages/query-core/src/queryObserver.ts:56— ClassTooLong — 444 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 44 over it, 1.11× 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.
HydrationBoundary.HydrationBoundary (cognitive 21) packages/preact-query/src/HydrationBoundary.tsx:86— HydrationBoundary.HydrationBoundary has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 9). None of this is in the body itself: all 21 points belong to 2 function literals inside it that branch (lines 114, 161). 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.
HydrationBoundary.HydrationBoundary (cognitive 21) packages/react-query/src/HydrationBoundary.tsx:85— HydrationBoundary.HydrationBoundary has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 9). None of this is in the body itself: all 21 points belong to 2 function literals inside it that branch (lines 114, 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.
TooManyMethods: QueryClient packages/vue-query/src/queryClient.ts:67— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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.
TooManyMethods: QueryClient packages/query-core/src/queryClient.ts:78— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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.
Duplicated block (33 lines × 2 locations) integrations/react/next-15/app/make-query-client.ts:21— integrations/react/next-15/app/make-query-client.ts:21 · integrations/react/next-16/app/make-query-client.ts:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (33 lines × 2 locations) packages/preact-query/src/useSuspenseInfiniteQuery.ts:122— packages/preact-query/src/useSuspenseInfiniteQuery.ts:122 · packages/react-query/src/useSuspenseInfiniteQuery.ts:102 — 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 (31 lines × 2 locations) integrations/react/next-15/app/page.tsx:9— integrations/react/next-15/app/page.tsx:9 · integrations/react/next-16/app/page.tsx:9 — 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 (31 lines × 2 locations) packages/solid-query/src/useMutationState.ts:24— packages/solid-query/src/useMutationState.ts:24 · packages/vue-query/src/useMutationState.ts:98 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Complex function replaceEqualDeep (cyclomatic 22, cognitive 29) packages/query-core/src/utils.ts:388— replaceEqualDeep has cyclomatic complexity 22 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function replaceEqualDeep (cyclomatic 22, cognitive 29) packages/query-core/src/utils.ts:389— replaceEqualDeep has cyclomatic complexity 22 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function partialMatchKey (cyclomatic 14, cognitive 23) packages/query-core/src/utils.ts:343— partialMatchKey has cyclomatic complexity 14 and cognitive complexity 23; 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.
Complex function partialMatchKey (cyclomatic 14, cognitive 23) packages/query-core/src/utils.ts:344— partialMatchKey has cyclomatic complexity 14 and cognitive complexity 23; 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.
Complex function (anonymous) (cyclomatic 13, cognitive 20) packages/preact-query/src/HydrationBoundary.tsx:114— (anonymous) has cyclomatic complexity 13 and cognitive complexity 20; 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.
Complex function (anonymous) (cyclomatic 13, cognitive 20) packages/react-query/src/HydrationBoundary.tsx:114— (anonymous) has cyclomatic complexity 13 and cognitive complexity 20; 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.
Complex function useBaseQuery (cyclomatic 12, cognitive 13) packages/preact-query/src/useBaseQuery.ts:39— useBaseQuery has cyclomatic complexity 12 and cognitive complexity 13; 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.
Complex function useBaseQuery (cyclomatic 12, cognitive 13) packages/react-query/src/useBaseQuery.ts:39— useBaseQuery has cyclomatic complexity 12 and cognitive complexity 13; 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.
Dead file (~284 LoC) packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~284 LoC) packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~271 LoC) packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs— no import path from any entry point (348 application, 168 tooling, 368 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 (~271 LoC) packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs— no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/query-codemods/src/v5/remove-overloads/remove-overloads.cjs) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~96 LoC) packages/query-codemods/src/v4/__testfixtures__/default-import.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~96 LoC) packages/query-codemods/src/v4/__testfixtures__/named-import.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~58 LoC) knip.ts— no import path from any entry point (348 application, 168 tooling, 368 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 (~58 LoC) packages/query-codemods/src/v5/remove-overloads/remove-overloads.cjs— no import path from any entry point (348 application, 168 tooling, 368 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 (~55 LoC) packages/query-codemods/src/v5/remove-overloads/__testfixtures__/bug-reports.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~55 LoC) packages/query-codemods/src/v5/rename-hydrate/rename-hydrate.cjs— no import path from any entry point (348 application, 168 tooling, 368 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
Unused dependency '@oxc-project/runtime' — Declared in packages/angular-query-experimental/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 '@oxc-project/runtime' — Declared in packages/angular-query-persist-client/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.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×2
JavaScript dependencies are not locked REDACTED:12— REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked REDACTED:13— REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark integrations/lit/vite/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
No authorization integrations/react/next-16/app/_action.ts:1— This repository serves requests — server actions ("use server") in integrations/react/next-16/app/_action.ts (integrations/react/next-16/app/_action.ts:1) — 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.
Explorer.Explorer (cyclomatic 79) packages/query-devtools/src/Explorer.tsx:468— Explorer.Explorer has cyclomatic complexity 79 (threshold 15). Of this number, 22 points are the body's own statements and 57 belong to 18 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.
Devtools.ContentView (cyclomatic 75) packages/query-devtools/src/Devtools.tsx:772— Devtools.ContentView has cyclomatic complexity 75 (threshold 15). Of this number, 30 points are the body's own statements and 45 belong to 17 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.
Devtools.DraggablePanel (cyclomatic 51) packages/query-devtools/src/Devtools.tsx:498— Devtools.DraggablePanel has cyclomatic complexity 51 (threshold 15). Of this number, 18 points are the body's own statements and 33 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useBaseQuery.useBaseQuery (cyclomatic 34) packages/solid-query/src/useBaseQuery.ts:124— useBaseQuery.useBaseQuery has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 270, a function literal at line 376, a function literal at line 148, …). 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.
QueryObserver.createResult (cyclomatic 30) packages/query-core/src/queryObserver.ts:589— QueryObserver.createResult has cyclomatic complexity 30 (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.
Query.fetch (cyclomatic 28) packages/query-core/src/query.ts:709— Query.fetch has cyclomatic complexity 28 (threshold 15). Of this number, 16 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Devtools.QueryDetails (cyclomatic 24) packages/query-devtools/src/Devtools.tsx:1979— Devtools.QueryDetails has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 12 function items inside it that branch (restoreQueryAfterLoadingOrError, a function literal at line 2289, a function literal at line 1986, …). 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.
utils.replaceEqualDeep (cyclomatic 22) packages/query-core/src/utils.ts:389— utils.replaceEqualDeep has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
query-fn-aware-usage-transformer.transformQueryFnAwareUsages (cyclomatic 21) packages/query-codemods/src/v5/remove-overloads/transformers/query-fn-aware-usage-transformer.cjs:12— query-fn-aware-usage-transformer.transformQueryFnAwareUsages has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 6 function items inside it that branch (replacer, transformArgumentToQueryFunction, canSkipReplacement, …). 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.
hydration.hydrate (cyclomatic 21) packages/query-core/src/hydration.ts:306— hydration.hydrate has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 330). 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.
Devtools.Devtools (cyclomatic 21) packages/query-devtools/src/Devtools.tsx:198— Devtools.Devtools has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 229, 212, 220, …). 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.
useBaseQuery.useBaseQuery (cyclomatic 21) packages/vue-query/src/useBaseQuery.ts:112— useBaseQuery.useBaseQuery has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 143, 231, 277, …). 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.
exports (cyclomatic 21) packages/query-codemods/src/utils/index.cjs:1— exports has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 22 function items inside it that branch (isClassInstantiationOf, isFunctionCallOf, locateImports, …). 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.
nativeObjectType.getNativeObjectType (cyclomatic 20) packages/query-devtools/src/nativeObjectType.ts:32— nativeObjectType.getNativeObjectType 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.
PiPContext.PiPProvider (cyclomatic 20) packages/query-devtools/src/contexts/PiPContext.tsx:43— PiPContext.PiPProvider has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 96, a function literal at line 145, requestPipWindow, …). 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.
index.broadcastQueryClient (cyclomatic 19) packages/query-broadcast-client-experimental/src/index.ts:66— index.broadcastQueryClient has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 170, 129, 95, …). 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.
exports (cyclomatic 19) packages/query-codemods/src/v4/utils/replacers/key-replacer.cjs:8— exports has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 13 function items inside it that branch (a function literal at line 93, createKeyValue, isStringLiteral, …). 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.
containers.svelte.createRawRef (cyclomatic 18) packages/svelte-query/src/containers.svelte.ts:47— containers.svelte.createRawRef has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 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.
infiniteQueryBehavior.infiniteQueryBehavior.onFetch (cyclomatic 17) packages/query-core/src/infiniteQueryBehavior.ts:30— infiniteQueryBehavior.infiniteQueryBehavior.onFetch has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (fetchFn, fetchFn::fetchPage, fetchFn::fetchPage::createQueryFnContext). 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.
QueryObserver.setOptions (cyclomatic 17) packages/query-core/src/queryObserver.ts:189— QueryObserver.setOptions has cyclomatic complexity 17 (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.
filter-aware-usage-transformer.transformFilterAwareUsages::replacer (cyclomatic 16) packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs:68— filter-aware-usage-transformer.transformFilterAwareUsages::replacer 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.
retryer.createRetryer.run (cyclomatic 16) packages/query-core/src/retryer.ts:223— retryer.createRetryer.run has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 244, 276, 281). 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.
utils.matchQuery (cyclomatic 16) packages/query-core/src/utils.ts:205— utils.matchQuery 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.
Repeated repair: examples/react/chat/src/index.tsx examples/react/chat/src/index.tsx:25— examples/react/chat/src/index.tsx changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is index.ChatMessage at line 25), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(examples/react/chat): submit through a 'form' so 'Enter' cannot send an empty question (#12049)”; “fix(examples/react/chat): give each question an 'id' so repeated questions get their own React key and query (#12047)”; “fix(examples/react/chat): use camelCase 'strokeWidth', 'strokeLinecap' and 'strokeLinejoin' on the send icon (#12048)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 02:55:47 +09:00' --until='2026-11-14 02:55:47 +09:00' --full-history --no-merges -- examples/react/chat/src/index.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.
HackComment packages/vue-query/src/vueQueryPlugin.ts:135— // HACK: taken from provide(): https://github.com/vuejs/composition-api/blob/master/src/apis/inject.ts#L30 — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
Devtools.DraggablePanel (cognitive 73) packages/query-devtools/src/Devtools.tsx:498— Devtools.DraggablePanel has cognitive complexity 73 (threshold 15). Drivers by points: ternaries 16 (34 pts), boolean chains 20, if/else 14 (19 pts) (nesting depth added 23). Of this number, 17 points are the body's own statements and 56 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. This file is where this pass's cognitive complexity CONCENTRATES: packages/query-devtools/src/Devtools.tsx holds 4 of the 35 methods over the threshold — including the worst — and 131 of the 415 points over it (32%), 2.3× the next-largest file (packages/query-devtools/src/Explorer.tsx at 57). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Explorer.Explorer (cognitive 72) packages/query-devtools/src/Explorer.tsx:468— Explorer.Explorer has cognitive complexity 72 (threshold 15). Drivers by points: boolean chains 27, ternaries 19 (27 pts), if/else 15 (17 pts), match/switch 1 (nesting depth added 10). Of this number, 16 points are the body's own statements and 56 belong to 18 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.
Devtools.ContentView (cognitive 70) packages/query-devtools/src/Devtools.tsx:772— Devtools.ContentView has cognitive complexity 70 (threshold 15). Drivers by points: boolean chains 31, ternaries 22 (24 pts), if/else 13 (14 pts), loops 1 (nesting depth added 3). Of this number, 23 points are the body's own statements and 47 belong to 17 function literals 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. This file is where this pass's cognitive complexity CONCENTRATES: packages/query-devtools/src/Devtools.tsx holds 4 of the 35 methods over the threshold — including the worst — and 131 of the 415 points over it (32%), 2.3× the next-largest file (packages/query-devtools/src/Explorer.tsx at 57). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Query.fetch (cognitive 39) packages/query-core/src/query.ts:709— Query.fetch has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (31 pts), boolean chains 6, error handling 1, ternaries 1 (nesting depth added 13). Of this number, 18 points are the body's own statements and 21 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createPersister.experimental_createQueryPersister.restoreQueries (cognitive 35) packages/query-persist-client-core/src/createPersister.ts:394— createPersister.experimental_createQueryPersister.restoreQueries has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (29 pts), error handling 1 (4 pts), loops 1 (2 pts) (nesting depth added 24). 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.
QueryObserver.createResult (cognitive 33) packages/query-core/src/queryObserver.ts:589— QueryObserver.createResult has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 12, error handling 1 (3 pts), 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.
filter-aware-usage-transformer.transformFilterAwareUsages::replacer (cognitive 32) packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs:68— filter-aware-usage-transformer.transformFilterAwareUsages::replacer has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (27 pts), ternaries 2 (4 pts), error handling 1 (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.
useBaseQuery.useBaseQuery (cognitive 32) packages/solid-query/src/useBaseQuery.ts:124— useBaseQuery.useBaseQuery has cognitive complexity 32 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 9, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 9 of the 32 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 270, a function literal at line 376, a function literal at line 177, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
createPersister.experimental_createQueryPersister.removeQueries (cognitive 29) packages/query-persist-client-core/src/createPersister.ts:453— createPersister.experimental_createQueryPersister.removeQueries has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (23 pts), error handling 1 (4 pts), loops 1 (2 pts) (nesting depth added 19). 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.
transformUsages (cognitive 28) packages/query-codemods/src/v5/is-loading/is-loading.cjs:15— transformUsages has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 3 (9 pts), other 2, error handling 1 (nesting depth added 14). None of this is in the body itself: all 28 points belong to 14 function items inside it that branch (replacer, a function literal at line 133, getNodeLocation, …). 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.
Devtools.QueryDetails (cognitive 26) packages/query-devtools/src/Devtools.tsx:1979— Devtools.QueryDetails has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 8, boolean chains 4, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 2289, restoreQueryAfterLoadingOrError, a function literal at line 2339, …). 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. This file is where this pass's cognitive complexity CONCENTRATES: packages/query-devtools/src/Devtools.tsx holds 4 of the 35 methods over the threshold — including the worst — and 131 of the 415 points over it (32%), 2.3× the next-largest file (packages/query-devtools/src/Explorer.tsx at 57). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
useBaseQuery.useBaseQuery (cognitive 25) packages/vue-query/src/useBaseQuery.ts:112— useBaseQuery.useBaseQuery has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 3, ternaries 2, loops 1 (nesting depth added 6). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 231, 143, 248, …). 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.
utils.replaceEqualDeep (cognitive 24) packages/query-core/src/utils.ts:389— utils.replaceEqualDeep has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 5 (6 pts), boolean chains 5, 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.
PiPContext.PiPProvider (cognitive 24) packages/query-devtools/src/contexts/PiPContext.tsx:43— PiPContext.PiPProvider has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 7, error handling 2 (3 pts) (nesting depth added 5). None of this is in the body itself: all 24 points belong to 6 function items inside it that branch (a function literal at line 145, a function literal at line 96, requestPipWindow, …). 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.
exports (cognitive 24) packages/query-codemods/src/v4/utils/replacers/key-replacer.cjs:8— exports has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 2, error handling 1, other 1, ternaries 1 (nesting depth added 6). None of this is in the body itself: all 24 points belong to 13 function items inside it that branch (a function literal at line 93, createKeyValue, isStringLiteral, …). 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.
utils.partialMatchKey (cognitive 22) packages/query-core/src/utils.ts:344— utils.partialMatchKey has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (5 pts), boolean chains 2 (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.
Devtools.Devtools (cognitive 22) packages/query-devtools/src/Devtools.tsx:198— Devtools.Devtools has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (14 pts), boolean chains 8 (nesting depth added 4). Of this number, 11 points are the body's own statements and 11 belong to 5 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. This file is where this pass's cognitive complexity CONCENTRATES: packages/query-devtools/src/Devtools.tsx holds 4 of the 35 methods over the threshold — including the worst — and 131 of the 415 points over it (32%), 2.3× the next-largest file (packages/query-devtools/src/Explorer.tsx at 57). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
createPersister.experimental_createQueryPersister.retrieveQuery (cognitive 22) packages/query-persist-client-core/src/createPersister.ts:206— createPersister.experimental_createQueryPersister.retrieveQuery has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), error handling 2 (5 pts) (nesting depth added 13). 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.
utils.matchQuery (cognitive 20) packages/query-core/src/utils.ts:205— utils.matchQuery has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5 (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.
nativeObjectType.getNativeObjectType (cognitive 19) packages/query-devtools/src/nativeObjectType.ts:32— nativeObjectType.getNativeObjectType has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, error handling 1, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createPersister.experimental_createQueryPersister.persisterGc (cognitive 19) packages/query-persist-client-core/src/createPersister.ts:358— createPersister.experimental_createQueryPersister.persisterGc has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (13 pts), error handling 1 (4 pts), loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
exports (cognitive 19) packages/query-codemods/src/utils/index.cjs:1— exports has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 6, if/else 6, ternaries 4, loops 2 (3 pts) (nesting depth added 1). None of this is in the body itself: all 19 points belong to 22 function items inside it that branch (locateImports, isClassInstantiationOf, isFunctionCallOf, …). 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.
infiniteQueryBehavior.infiniteQueryBehavior.onFetch::fetchFn (cognitive 18) packages/query-core/src/infiniteQueryBehavior.ts:38— infiniteQueryBehavior.infiniteQueryBehavior.onFetch::fetchFn has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 3 (5 pts), boolean chains 2, loops 1 (2 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.
Mutation.execute (cognitive 18) packages/query-core/src/mutation.ts:301— Mutation.execute has cognitive complexity 18 (threshold 15). Drivers by points: error handling 5 (9 pts), if/else 6 (8 pts), boolean chains 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.
streamedQuery.streamedQuery.<returned closure> (cognitive 18) packages/query-core/src/streamedQuery.ts:87— streamedQuery.streamedQuery.<returned closure> has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 5, ternaries 2 (4 pts), loops 1 (nesting depth added 4). Of this number, 14 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.
transformUsages (cognitive 18) packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs:13— transformUsages has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (4 pts), other 2, boolean chains 1, error handling 1 (nesting depth added 6). None of this is in the body itself: all 18 points belong to 21 function items inside it that branch (replacer, getNodeLocation, (anonymous)::resolveTargetArgument, …). 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.
MutationObserver.#notify (cognitive 17) packages/query-core/src/mutationObserver.ts:250— MutationObserver.#notify has cognitive complexity 17 (threshold 15). Drivers by points: error handling 4 (12 pts), if/else 3 (4 pts), boolean chains 1 (nesting depth added 9). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 251). 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.
hydration.hydrate (cognitive 17) packages/query-core/src/hydration.ts:306— hydration.hydrate has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (5 pts), ternaries 4 (5 pts) (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 330). 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.
utils.updateNestedDataByPath (cognitive 17) packages/query-devtools/src/utils.tsx:244— utils.updateNestedDataByPath has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, ternaries 1 (2 pts) (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.
utils.deleteNestedDataByPath (cognitive 17) packages/query-devtools/src/utils.tsx:323— utils.deleteNestedDataByPath has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 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.
containers.svelte.createRawRef (cognitive 17) packages/svelte-query/src/containers.svelte.ts:47— containers.svelte.createRawRef has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 4, loops 2, ternaries 2 (nesting depth added 1). Of this number, 9 points are the body's own statements and 8 belong to 3 function items inside it that branch. 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.
query-fn-aware-usage-transformer.transformQueryFnAwareUsages::replacer (cognitive 16) packages/query-codemods/src/v5/remove-overloads/transformers/query-fn-aware-usage-transformer.cjs:95— query-fn-aware-usage-transformer.transformQueryFnAwareUsages::replacer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (2 pts), 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.
MutationCache.remove (cognitive 16) packages/query-core/src/mutationCache.ts:186— MutationCache.remove has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (16 pts) (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.
Change coupling: devtools.tsx ↔ devtoolsPanel.tsx packages/solid-query-devtools/src/devtools.tsx:1— `packages/solid-query-devtools/src/devtools.tsx` and `packages/solid-query-devtools/src/devtoolsPanel.tsx` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `a5d5e004` docs(*-devtools): describe how the 'theme' prop interacts with the th…; `f232b75e` fix(solid-query-devtools): stop defaulting the 'theme' prop to 'syste…; `688f6e07` docs(*): describe 'shadowDOMTarget' as the shadow DOM the devtools st… — run `git show` on any of them.
No structured logging — No logging call was found in the 378 JavaScript/TypeScript production file(s) this check read across 46 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Forked directory tree (9 identical files, ~277 lines × 2 trees) integrations/react/next-15/app/make-query-client.ts:1— integrations/react/next-15/ and integrations/react/next-16/ are near-verbatim copies of each other: 9 files are byte-identical under the same relative paths (~277 lines; the trees hold 12 and 12 files). That is one structural fact, not 9 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Duplication concentrated across 25 sibling directories (111 clone groups) packages/preact-query/src/useQueries.ts:6— 111 duplicated blocks under packages/ have copies in at least two of the sibling directories angular-query-experimental, angular-query-persist-client, eslint-plugin-query, lit-query, preact-query, preact-query-devtools (+19 more sibling(s) not listed) — 38 of them are reported below, and 73 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 111 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 111 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 111 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.
Duplication concentrated across 6 sibling directories (7 clone groups) integrations/react/next-15/app/make-query-client.ts:21— 7 duplicated blocks under integrations/react/ have copies in at least two of the sibling directories next-14, next-15, next-16, vite, webpack-4, webpack-5 — 6 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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 (213 matched lines × 2 locations) · ×1
Duplicated block with local edits (213 matched lines × 2 locations) packages/lit-query/src/createInfiniteQueryController.ts:29— packages/lit-query/src/createInfiniteQueryController.ts:29 · packages/lit-query/src/createQueryController.ts:29 — the two spans are one implementation copied and then locally edited — 1111 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.
Wholesale file copy (181 identical lines × 2 files) packages/preact-query/src/useQueries.ts:6— packages/preact-query/src/useQueries.ts:6 · packages/react-query/src/useQueries.ts:9 — these 2 files are line-for-line copies of one another — 181 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (143 identical lines × 2 files) packages/preact-query/src/types.ts:2— packages/preact-query/src/types.ts:2 · packages/react-query/src/types.ts:3 — these 2 files are line-for-line copies of one another — 143 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (129 identical lines × 2 files) packages/preact-query/src/useSuspenseQueries.ts:1— packages/preact-query/src/useSuspenseQueries.ts:1 · packages/react-query/src/useSuspenseQueries.ts:2 — these 2 files are line-for-line copies of one another — 129 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (98 lines × 2 locations) packages/angular-query-experimental/src/inject-queries.ts:39— packages/angular-query-experimental/src/inject-queries.ts:39 · packages/svelte-query/src/createQueries.svelte.ts:24 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Wholesale file copy (96 identical lines × 2 files) packages/query-devtools/src/TanstackQueryDevtools.tsx:1— packages/query-devtools/src/TanstackQueryDevtools.tsx:1 · packages/query-devtools/src/TanstackQueryDevtoolsPanel.tsx:1 — these 2 files are line-for-line copies of one another — 96 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (93 matched lines × 2 locations) · ×1
Duplicated block with local edits (93 matched lines × 2 locations) packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs:14— packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs:14 · packages/query-codemods/src/v5/remove-overloads/transformers/query-fn-aware-usage-transformer.cjs:12 — the two spans are one implementation copied and then locally edited — 430 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (91 lines × 2 locations) packages/query-core/src/types.ts:1078— packages/query-core/src/types.ts:1078 · packages/query-core/src/types.ts:1444 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (74 lines × 3 locations) packages/angular-query-experimental/src/infinite-query-options.ts:24— packages/angular-query-experimental/src/infinite-query-options.ts:24 · packages/preact-query/src/infiniteQueryOptions.ts:25 · packages/react-query/src/infiniteQueryOptions.ts:24 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication· Duplicated block with local edits (70 matched lines × 2 locations) · ×1
Duplicated block with local edits (70 matched lines × 2 locations) packages/query-core/src/queryClient.ts:286— packages/query-core/src/queryClient.ts:286 · packages/vue-query/src/queryClient.ts:168 — the two spans are one implementation copied and then locally edited — 354 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (66 lines × 2 locations) packages/preact-query/src/errorBoundaryUtils.ts:21— packages/preact-query/src/errorBoundaryUtils.ts:21 · packages/react-query/src/errorBoundaryUtils.ts:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Wholesale file copy (63 identical lines × 2 files) packages/preact-query/src/useMutationState.ts:3— packages/preact-query/src/useMutationState.ts:3 · packages/react-query/src/useMutationState.ts:4 — these 2 files are line-for-line copies of one another — 63 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (59 identical lines × 2 files) packages/preact-query/src/infiniteQueryOptions.ts:1— packages/preact-query/src/infiniteQueryOptions.ts:1 · packages/react-query/src/infiniteQueryOptions.ts:1 — these 2 files are line-for-line copies of one another — 59 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (58 matched lines × 2 locations) · ×1
Duplicated block with local edits (58 matched lines × 2 locations) packages/preact-query/src/HydrationBoundary.tsx:17— packages/preact-query/src/HydrationBoundary.tsx:17 · packages/react-query/src/HydrationBoundary.tsx:16 — the two spans are one implementation copied and then locally edited — 306 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.
Wholesale file copy (57 identical lines × 2 files) packages/preact-query/src/queryOptions.ts:1— packages/preact-query/src/queryOptions.ts:1 · packages/react-query/src/queryOptions.ts:1 — these 2 files are line-for-line copies of one another — 57 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (57 lines × 2 locations) packages/preact-query/src/suspense.ts:19— packages/preact-query/src/suspense.ts:19 · packages/react-query/src/suspense.ts:18 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (53 lines × 3 locations) packages/angular-query-experimental/src/query-options.ts:22— packages/angular-query-experimental/src/query-options.ts:22 · packages/preact-query/src/queryOptions.ts:23 · packages/react-query/src/queryOptions.ts:22 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Wholesale file copy (53 identical lines × 2 files) packages/preact-query/src/useBaseQuery.ts:1— packages/preact-query/src/useBaseQuery.ts:1 · packages/react-query/src/useBaseQuery.ts:4 — these 2 files are line-for-line copies of one another — 53 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (51 identical lines × 2 files) packages/lit-query/src/useIsFetching.ts:1— packages/lit-query/src/useIsFetching.ts:1 · packages/lit-query/src/useIsMutating.ts:1 — these 2 files are line-for-line copies of one another — 51 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (51 matched lines × 2 locations) · ×1
Duplicated block with local edits (51 matched lines × 2 locations) packages/vue-query/src/usePrefetchInfiniteQuery.ts:38— packages/vue-query/src/usePrefetchInfiniteQuery.ts:38 · packages/vue-query/src/usePrefetchQuery.ts:39 — the two spans are one implementation copied and then locally edited — 199 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 (47 matched lines × 2 locations) · ×1
Duplicated block with local edits (47 matched lines × 2 locations) packages/preact-query/src/useMutation.ts:188— packages/preact-query/src/useMutation.ts:188 · packages/react-query/src/useMutation.ts:187 — the two spans are one implementation copied and then locally edited — 249 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 (44 matched lines × 2 locations) · ×1
Duplicated block with local edits (44 matched lines × 2 locations) packages/angular-query-experimental/src/create-base-query.ts:90— packages/angular-query-experimental/src/create-base-query.ts:90 · packages/angular-query-experimental/src/inject-mutation.ts:241 — the two spans are one implementation copied and then locally edited — 184 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (42 lines × 3 locations) packages/angular-query-experimental/src/types.ts:212— packages/angular-query-experimental/src/types.ts:212 · packages/preact-query/src/types.ts:385 · packages/react-query/src/types.ts:386 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (39 lines × 2 locations) packages/lit-query/src/createQueriesController.ts:120— packages/lit-query/src/createQueriesController.ts:120 · packages/solid-query/src/useQueries.ts:118 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (39 matched lines × 2 locations) · ×1
Duplicated block with local edits (39 matched lines × 2 locations) packages/react-query-devtools/src/ReactQueryDevtools.tsx:54— packages/react-query-devtools/src/ReactQueryDevtools.tsx:54 · packages/react-query-devtools/src/ReactQueryDevtoolsPanel.tsx:45 — the two spans are one implementation copied and then locally edited — 192 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (37 lines × 2 locations) packages/solid-query-persist-client/tsdown.config.ts:5— packages/solid-query-persist-client/tsdown.config.ts:5 · packages/solid-query/tsdown.config.ts:5 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (36 lines × 3 locations) packages/lit-query/src/useIsFetching.ts:60— packages/lit-query/src/useIsFetching.ts:60 · packages/lit-query/src/useIsMutating.ts:60 · packages/lit-query/src/useMutationState.ts:79 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (35 lines × 2 locations) packages/query-devtools/src/Devtools.tsx:2628— packages/query-devtools/src/Devtools.tsx:2628 · packages/query-devtools/src/Devtools.tsx:2668 — all 2 copies are in the same file, and the CITED SPAN is a DECLARATION HEADER — the name, parameter list with its constraints and defaults, and base-type clause of a declaration — rather than statements inside a body. A header cannot be lifted into a helper: there is no expression position for a call to stand in, and the copies are frequently required to match, because one declaration passes its parameters straight through to the other. So the move is not extraction. Give the repeated pieces names — factor a long constraint or base-type expression into one named type both declarations refer to — and where the headers must stay identical, derive one from the other (a shared base declaration, or a single alias that spells the parameter set once) so that changing it once changes both. Where the language offers neither, treat the two as a pair that must be edited together: they drift apart the first time only one of them is changed, which is why this is reported.
Duplicated block (35 lines × 3 locations) packages/svelte-query-devtools/vite.config.ts:7— packages/svelte-query-devtools/vite.config.ts:7 · packages/svelte-query-persist-client/vite.config.ts:7 · packages/svelte-query/vite.config.ts:7 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (32 lines × 27 locations) oxlint.config.ts:230— oxlint.config.ts:230 · packages/angular-query-experimental/root.oxlint.config.ts:230 · packages/angular-query-persist-client/root.oxlint.config.ts:230 · packages/eslint-plugin-query/root.oxlint.config.ts:230 · +23 more site(s) not listed — the 27 copies are spread across 27 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
R10 · Code Duplication· Duplicated block with local edits (32 matched lines × 2 locations) · ×1
Duplicated block with local edits (32 matched lines × 2 locations) packages/preact-query-persist-client/src/PersistQueryClientProvider.tsx:44— packages/preact-query-persist-client/src/PersistQueryClientProvider.tsx:44 · packages/react-query-persist-client/src/PersistQueryClientProvider.tsx:38 — the two spans are one implementation copied and then locally edited — 245 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (30 lines × 2 locations) packages/lit-query/src/createInfiniteQueryController.ts:69— packages/lit-query/src/createInfiniteQueryController.ts:69 · packages/lit-query/src/createQueriesController.ts:224 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (29 lines × 3 locations) packages/query-devtools/src/Devtools.tsx:1318— packages/query-devtools/src/Devtools.tsx:1318 · packages/query-devtools/src/Devtools.tsx:1400 · packages/query-devtools/src/Devtools.tsx:1470 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Complex function ContentView (cyclomatic 30, cognitive 29) packages/query-devtools/src/Devtools.tsx:772— ContentView has cyclomatic complexity 30 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
Complex function addReferenceDetails (cyclomatic 28, cognitive 89) REDACTED:712— addReferenceDetails has cyclomatic complexity 28 and cognitive complexity 89; 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 Explorer (cyclomatic 23, cognitive 17) · ×1
Complex function Explorer (cyclomatic 23, cognitive 17) packages/query-devtools/src/Explorer.tsx:468— Explorer has cyclomatic complexity 23 and cognitive complexity 17; 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.
Complex function (anonymous) (cyclomatic 22, cognitive 20) packages/query-core/src/hydration.ts:330— (anonymous) has cyclomatic complexity 22 and cognitive complexity 20; 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.
Complex function getNativeObjectType (cyclomatic 20, cognitive 19) packages/query-devtools/src/nativeObjectType.ts:32— getNativeObjectType has cyclomatic complexity 20 and cognitive complexity 19; 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.
Complex function CallExpression (cyclomatic 18, cognitive 24) packages/eslint-plugin-query/src/rules/prefer-query-options/prefer-query-options.rule.ts:105— CallExpression has cyclomatic complexity 18 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function DraggablePanel (cyclomatic 18, cognitive 17) packages/query-devtools/src/Devtools.tsx:498— DraggablePanel has cyclomatic complexity 18 and cognitive complexity 17; 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.
Complex function visit (cyclomatic 17, cognitive 13) packages/eslint-plugin-query/src/rules/exhaustive-deps/exhaustive-deps.utils.ts:208— visit has cyclomatic complexity 17 and cognitive complexity 13; 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.
Complex function replacer (cyclomatic 16, cognitive 32) packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs:68— replacer has cyclomatic complexity 16 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.
Complex function matchQuery (cyclomatic 16, cognitive 20) packages/query-core/src/utils.ts:205— matchQuery has cyclomatic complexity 16 and cognitive complexity 20; 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.
Complex function (anonymous) (cyclomatic 15, cognitive 29) packages/query-devtools/src/Devtools.tsx:706— (anonymous) has cyclomatic complexity 15 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fetch (cyclomatic 15, cognitive 17) packages/query-core/src/query.ts:709— fetch has cyclomatic complexity 15 and cognitive complexity 17; 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.
Complex function declaredTypeLabel (cyclomatic 15, cognitive 16) REDACTED:393— declaredTypeLabel has cyclomatic complexity 15 and cognitive complexity 16; 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.
Complex function (anonymous) (cyclomatic 14, cognitive 18) packages/query-devtools/src/utils.tsx:248— (anonymous) has cyclomatic complexity 14 and cognitive complexity 18; 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.
Complex function CallExpression (cyclomatic 14, cognitive 17) packages/eslint-plugin-query/src/rules/no-rest-destructuring/no-rest-destructuring.rule.ts:40— CallExpression has cyclomatic complexity 14 and cognitive complexity 17; 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.
Complex function isRelevantReference (cyclomatic 14, cognitive 16) packages/eslint-plugin-query/src/rules/exhaustive-deps/exhaustive-deps.utils.ts:6— isRelevantReference has cyclomatic complexity 14 and cognitive complexity 16; 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.
Complex function execute (cyclomatic 13, cognitive 19) packages/query-core/src/mutation.ts:301— execute has cyclomatic complexity 13 and cognitive complexity 19; 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.
Complex function (anonymous) (cyclomatic 13, cognitive 14) packages/query-devtools/src/Explorer.tsx:547— (anonymous) has cyclomatic complexity 13 and cognitive complexity 14; 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.
Complex function (anonymous) (cyclomatic 13, cognitive 12) packages/query-devtools/src/Explorer.tsx:499— (anonymous) has cyclomatic complexity 13 and cognitive complexity 12; 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.
Complex function visit (cyclomatic 13, cognitive 12) packages/query-devtools/src/explorerSearch.ts:163— visit has cyclomatic complexity 13 and cognitive complexity 12; 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.
Complex function restoreQueries (cyclomatic 12, cognitive 35) packages/query-persist-client-core/src/createPersister.ts:394— restoreQueries has cyclomatic complexity 12 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 14) packages/query-core/src/streamedQuery.ts:87— (anonymous) has cyclomatic complexity 12 and cognitive complexity 14; 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.
Complex function (anonymous) (cyclomatic 12, cognitive 11) packages/query-core/src/retryer.ts:244— (anonymous) has cyclomatic complexity 12 and cognitive complexity 11; 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.
Complex function searchEntries (cyclomatic 12, cognitive 10) packages/query-devtools/src/explorerSearch.ts:58— searchEntries has cyclomatic complexity 12 and cognitive complexity 10; 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.
Complex function removeQueries (cyclomatic 11, cognitive 29) packages/query-persist-client-core/src/createPersister.ts:453— removeQueries has cyclomatic complexity 11 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fetchFn (cyclomatic 11, cognitive 20) packages/query-core/src/infiniteQueryBehavior.ts:38— fetchFn has cyclomatic complexity 11 and cognitive complexity 20; 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.
Complex function (anonymous) (cyclomatic 11, cognitive 20) packages/query-core/src/query.ts:877— (anonymous) has cyclomatic complexity 11 and cognitive complexity 20; 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.
Complex function install (cyclomatic 11, cognitive 18) packages/vue-query/src/vueQueryPlugin.ts:76— install has cyclomatic complexity 11 and cognitive complexity 18; 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.
Complex function (anonymous) (cyclomatic 11, cognitive 17) packages/query-devtools/src/utils.tsx:326— (anonymous) has cyclomatic complexity 11 and cognitive complexity 17; 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.
Complex function (anonymous) (cyclomatic 11, cognitive 11) packages/query-core/src/queryObserver.ts:787— (anonymous) has cyclomatic complexity 11 and cognitive complexity 11; 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/query-devtools/src/Devtools.tsx · ×1
packages/query-devtools/src/Devtools.tsx: 3700 lines of code packages/query-devtools/src/Devtools.tsx:1— packages/query-devtools/src/Devtools.tsx has 3700 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/query-core/src/types.ts · ×1
packages/query-core/src/types.ts: 2344 lines of code packages/query-core/src/types.ts:1— packages/query-core/src/types.ts has 2344 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/query-devtools/src/icons/index.tsx · ×1
packages/query-devtools/src/icons/index.tsx: 1413 lines of code packages/query-devtools/src/icons/index.tsx:1— packages/query-devtools/src/icons/index.tsx has 1413 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/query-core/src/queryClient.ts · ×1
packages/query-core/src/queryClient.ts: 1099 lines of code packages/query-core/src/queryClient.ts:1— packages/query-core/src/queryClient.ts has 1099 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: 1041 lines of code REDACTED:1— REDACTED has 1041 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/query-core/src/query.ts · ×1
packages/query-core/src/query.ts: 1026 lines of code packages/query-core/src/query.ts:1— packages/query-core/src/query.ts has 1026 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/query-devtools/src/Explorer.tsx · ×1
packages/query-devtools/src/Explorer.tsx: 978 lines of code packages/query-devtools/src/Explorer.tsx:1— packages/query-devtools/src/Explorer.tsx has 978 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/query-core/src/queryObserver.ts · ×1
packages/query-core/src/queryObserver.ts: 875 lines of code packages/query-core/src/queryObserver.ts:1— packages/query-core/src/queryObserver.ts has 875 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/vue-query/src/queryClient.ts · ×1
packages/vue-query/src/queryClient.ts: 715 lines of code packages/vue-query/src/queryClient.ts:1— packages/vue-query/src/queryClient.ts has 715 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/query-core/src/utils.ts · ×1
packages/query-core/src/utils.ts: 679 lines of code packages/query-core/src/utils.ts:1— packages/query-core/src/utils.ts has 679 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/lit-query/src/createQueriesController.ts · ×1
packages/lit-query/src/createQueriesController.ts: 654 lines of code packages/lit-query/src/createQueriesController.ts:1— packages/lit-query/src/createQueriesController.ts has 654 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/preact-query/src/useSuspenseQueries.ts · ×1
packages/preact-query/src/useSuspenseQueries.ts: 613 lines of code packages/preact-query/src/useSuspenseQueries.ts:1— packages/preact-query/src/useSuspenseQueries.ts 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· packages/query-core/src/mutation.ts · ×1
packages/query-core/src/mutation.ts: 515 lines of code packages/query-core/src/mutation.ts:1— packages/query-core/src/mutation.ts has 515 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-query/src/useSuspenseQueries.ts · ×1
packages/react-query/src/useSuspenseQueries.ts: 514 lines of code packages/react-query/src/useSuspenseQueries.ts:1— packages/react-query/src/useSuspenseQueries.ts has 514 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/query-persist-client-core/src/createPersister.ts · ×1
packages/query-persist-client-core/src/createPersister.ts: 471 lines of code packages/query-persist-client-core/src/createPersister.ts:1— packages/query-persist-client-core/src/createPersister.ts has 471 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-query/src/useQueries.ts · ×1
packages/react-query/src/useQueries.ts: 469 lines of code packages/react-query/src/useQueries.ts:1— packages/react-query/src/useQueries.ts has 469 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/preact-query/src/types.ts · ×1
packages/preact-query/src/types.ts: 466 lines of code packages/preact-query/src/types.ts:1— packages/preact-query/src/types.ts has 466 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-query/src/types.ts · ×1
packages/react-query/src/types.ts: 466 lines of code packages/react-query/src/types.ts:1— packages/react-query/src/types.ts has 466 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/angular-query-experimental/src/inject-queries.ts · ×1
packages/angular-query-experimental/src/inject-queries.ts: 459 lines of code packages/angular-query-experimental/src/inject-queries.ts:1— packages/angular-query-experimental/src/inject-queries.ts has 459 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/vue-query/src/useQueries.ts · ×1
packages/vue-query/src/useQueries.ts: 453 lines of code packages/vue-query/src/useQueries.ts:1— packages/vue-query/src/useQueries.ts has 453 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/eslint-plugin-query/src/rules/exhaustive-deps/exhaustive-deps.utils.ts · ×1
packages/eslint-plugin-query/src/rules/exhaustive-deps/exhaustive-deps.utils.ts: 431 lines of code packages/eslint-plugin-query/src/rules/exhaustive-deps/exhaustive-deps.utils.ts:1— packages/eslint-plugin-query/src/rules/exhaustive-deps/exhaustive-deps.utils.ts has 431 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/angular-query-experimental/src/types.ts · ×1
packages/angular-query-experimental/src/types.ts: 417 lines of code packages/angular-query-experimental/src/types.ts:1— packages/angular-query-experimental/src/types.ts has 417 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/vue-query/src/queryOptions.ts · ×1
packages/vue-query/src/queryOptions.ts: 417 lines of code packages/vue-query/src/queryOptions.ts:1— packages/vue-query/src/queryOptions.ts has 417 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/preact-query/src/useQueries.ts · ×1
packages/preact-query/src/useQueries.ts: 416 lines of code packages/preact-query/src/useQueries.ts:1— packages/preact-query/src/useQueries.ts has 416 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/solid-query/src/useQueries.ts · ×1
packages/solid-query/src/useQueries.ts: 406 lines of code packages/solid-query/src/useQueries.ts:1— packages/solid-query/src/useQueries.ts has 406 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/query-core/src/hydration.ts · ×1
packages/query-core/src/hydration.ts: 404 lines of code packages/query-core/src/hydration.ts:1— packages/query-core/src/hydration.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~501 LoC) packages/query-codemods/src/v5/remove-overloads/__testfixtures__/default-import.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~290 LoC) packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~289 LoC) packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~244 LoC) packages/query-codemods/src/v5/is-loading/is-loading.cjs— no import path from any entry point (348 application, 168 tooling, 368 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 (~210 LoC) packages/query-codemods/src/v5/remove-overloads/__testfixtures__/default-import.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~208 LoC) packages/query-codemods/src/utils/index.cjs— no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/query-codemods/src/v4/key-transformation.cjs, packages/query-codemods/src/v5/is-loading/is-loading.cjs, packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~185 LoC) packages/query-codemods/src/v5/remove-overloads/transformers/query-fn-aware-usage-transformer.cjs— no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/query-codemods/src/v5/remove-overloads/remove-overloads.cjs) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~181 LoC) packages/query-codemods/src/v4/key-transformation.cjs— no import path from any entry point (348 application, 168 tooling, 368 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 (~175 LoC) packages/query-codemods/src/v4/__testfixtures__/parameter-is-object-expression.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~164 LoC) packages/query-codemods/src/v4/utils/replacers/key-replacer.cjs— no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/query-codemods/src/v4/key-transformation.cjs) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~127 LoC) packages/query-codemods/src/v4/__testfixtures__/parameter-is-object-expression.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~124 LoC) packages/query-codemods/src/utils/transformers/query-cache-transformer.cjs— no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/query-codemods/src/v4/key-transformation.cjs, packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~123 LoC) packages/query-codemods/src/v5/remove-overloads/utils/index.cjs— no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs, packages/query-codemods/src/v5/remove-overloads/transformers/query-fn-aware-usage-transformer.cjs) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~103 LoC) scripts/generate-labeler-config.ts— no import path from any entry point (348 application, 168 tooling, 368 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 (~98 LoC) packages/query-codemods/src/v4/__testfixtures__/named-import.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~94 LoC) packages/query-codemods/src/v4/__testfixtures__/default-import.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~88 LoC) packages/query-codemods/src/v4/__testfixtures__/namespaced-import.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~86 LoC) packages/query-codemods/src/v4/__testfixtures__/namespaced-import.input.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~62 LoC) packages/query-codemods/src/v5/remove-overloads/__testfixtures__/bug-reports.output.tsx— no import path from any entry point (348 application, 168 tooling, 368 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 (~53 LoC) packages/query-codemods/src/utils/transformers/query-client-transformer.cjs— no import path from any entry point (348 application, 168 tooling, 368 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (packages/query-codemods/src/v4/key-transformation.cjs, packages/query-codemods/src/v5/is-loading/is-loading.cjs, packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Unused dependency '@arethetypeswrong/cli' — Declared in the root REDACTED 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 '@size-limit/preset-small-lib' — Declared in the root REDACTED 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 '@angular/cli' — Declared in integrations/angular/cli-22/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.
No direct assertions: should omit a string key and reject one the object does not have packages/query-core/src/__tests__/OmitKeyof.test-d.ts:5— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should omit a number key and reject one the object does not have packages/query-core/src/__tests__/OmitKeyof.test-d.ts:60— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should omit a symbol key and reject one the object does not have packages/query-core/src/__tests__/OmitKeyof.test-d.ts:115— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should default TStrictly to strictly packages/query-core/src/__tests__/OmitKeyof.test-d.ts:176— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should constrain TStrictly to strictly or safely packages/query-core/src/__tests__/OmitKeyof.test-d.ts:197— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should accept an arbitrary key only with safely, never with strictly packages/query-core/src/__tests__/OmitKeyof.test-d.ts:215— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should preserve optional and readonly modifiers packages/query-core/src/__tests__/OmitKeyof.test-d.ts:236— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should collapse a union instead of distributing over it packages/query-core/src/__tests__/OmitKeyof.test-d.ts:254— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should accept every key of an index signature packages/query-core/src/__tests__/OmitKeyof.test-d.ts:274— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should omit every key when TKey is keyof TObject packages/query-core/src/__tests__/OmitKeyof.test-d.ts:286— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should distribute over a union instead of collapsing it, unlike OmitKeyof packages/query-core/src/__tests__/OmitKeyof.test-d.ts:298— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should constrain TKey to the keys shared by every union member packages/query-core/src/__tests__/OmitKeyof.test-d.ts:313— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should behave like Omit on a non-union object packages/query-core/src/__tests__/OmitKeyof.test-d.ts:333— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should take no arguments and return a boolean packages/query-core/src/__tests__/environmentManager.test-d.ts:8— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should reject an override that returns a non-boolean packages/query-core/src/__tests__/environmentManager.test-d.ts:12— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should reject an override that requires an argument packages/query-core/src/__tests__/environmentManager.test-d.ts:19— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should be a function returning a boolean, not a boolean constant packages/query-core/src/__tests__/environmentManager.test-d.ts:28— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should take no parameters packages/query-core/src/__tests__/environmentManager.test-d.ts:35— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should expose exactly isServer and setIsServer packages/query-core/src/__tests__/environmentManager.test-d.ts:41— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should expose isServer as the standalone check packages/query-core/src/__tests__/environmentManager.test-d.ts:47— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should only accept an IsServerValue and return void packages/query-core/src/__tests__/environmentManager.test-d.ts:52— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should type the singleton as a FocusManager packages/query-core/src/__tests__/focusManager.test-d.tsx:7— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should only expose its documented members packages/query-core/src/__tests__/focusManager.test-d.tsx:11— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should take a listener of the focus state and return an unsubscribe function packages/query-core/src/__tests__/focusManager.test-d.tsx:24— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should reject a listener that takes a non-boolean focus state packages/query-core/src/__tests__/focusManager.test-d.tsx:31— No conventional assertion call was detected, and 988 of 1630 tests in `packages/query-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Duplicated predicate packages/lit-query/src/createInfiniteQueryController.ts:199— `!this.syncClient() || !this.connectedState` appears character-identically in 3 files — packages/lit-query/src/createInfiniteQueryController.ts, packages/lit-query/src/createMutationController.ts, packages/lit-query/src/createQueriesController.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/lit-query/src/createInfiniteQueryController.ts:293— `!this.syncClient() || !this.observer || !this.queryClient` appears character-identically in 3 files — packages/lit-query/src/createInfiniteQueryController.ts, packages/lit-query/src/createMutationController.ts, packages/lit-query/src/createQueryController.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/query-core/src/queryClient.ts:90— `config.mutationCache || new MutationCache()` appears character-identically in 2 files — packages/query-core/src/queryClient.ts, packages/vue-query/src/queryClient.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 integrations/react/next-15/app/make-query-client.ts:42— `defaultShouldDehydrateQuery(query) || query.state.status === 'pending'` appears character-identically in 2 files — integrations/react/next-15/app/make-query-client.ts, integrations/react/next-16/app/make-query-client.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/preact-query/src/suspense.ts:74— `defaultedOptions?.suspense && result.isPending` appears character-identically in 2 files — packages/preact-query/src/suspense.ts, packages/react-query/src/suspense.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/preact-query/src/HydrationBoundary.tsx:136— `dehydratedQuery.state.dataUpdatedAt > existingQuery.state.dataUpdatedAt || (dehydratedQuery.promise && existingQuery.state.status !== 'pendi…` appears character-identically in 2 files — packages/preact-query/src/HydrationBoundary.tsx, packages/react-query/src/HydrationBoundary.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/query-codemods/src/v5/is-loading/__testfixtures__/default-import.input.tsx:23— `isError || isLoadingRenamed || isSuccess` appears character-identically in 4 files — packages/query-codemods/src/v5/is-loading/__testfixtures__/default-import.input.tsx, packages/query-codemods/src/v5/is-loading/__testfixtures__/default-import.output.tsx, packages/query-codemods/src/v5/is-loading/__testfixtures__/named-import.input.tsx, packages/query-codemods/src/v5/is-loading/__testfixtures__/named-import.output.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/query-codemods/src/v5/is-loading/__testfixtures__/default-import.input.tsx:36— `isError || rest.isLoading || rest.isSuccess` appears character-identically in 2 files — packages/query-codemods/src/v5/is-loading/__testfixtures__/default-import.input.tsx, packages/query-codemods/src/v5/is-loading/__testfixtures__/named-import.input.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/query-codemods/src/v5/is-loading/__testfixtures__/default-import.output.tsx:36— `isError || rest.isPending || rest.isSuccess` appears character-identically in 2 files — packages/query-codemods/src/v5/is-loading/__testfixtures__/default-import.output.tsx, packages/query-codemods/src/v5/is-loading/__testfixtures__/named-import.output.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/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs:63— `isSpreadElement || (isObjectProperty && property.key.name !== config.keyName)` appears character-identically in 2 files — packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs, packages/query-codemods/src/v5/remove-overloads/transformers/query-fn-aware-usage-transformer.cjs. 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/query-devtools/src/DevtoolsComponent.tsx:22— `props.theme || localStore.theme_preference || THEME_PREFERENCE` appears character-identically in 2 files — packages/query-devtools/src/DevtoolsComponent.tsx, packages/query-devtools/src/DevtoolsPanelComponent.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/preact-query/src/errorBoundaryUtils.ts:39— `query?.state.status === 'error' && typeof options.throwOnError === 'function'` appears character-identically in 2 files — packages/preact-query/src/errorBoundaryUtils.ts, packages/react-query/src/errorBoundaryUtils.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/query-codemods/src/v5/is-loading/__testfixtures__/default-import.input.tsx:49— `queryResult.isError || queryResult.isLoading || queryResult.isSuccess` appears character-identically in 2 files — packages/query-codemods/src/v5/is-loading/__testfixtures__/default-import.input.tsx, packages/query-codemods/src/v5/is-loading/__testfixtures__/named-import.input.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/query-codemods/src/v5/is-loading/__testfixtures__/default-import.output.tsx:49— `queryResult.isError || queryResult.isPending || queryResult.isSuccess` appears character-identically in 2 files — packages/query-codemods/src/v5/is-loading/__testfixtures__/default-import.output.tsx, packages/query-codemods/src/v5/is-loading/__testfixtures__/named-import.output.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/preact-query/src/useMutation.ts:234— `result.error && shouldThrowError(observer.options.throwOnError, [result.error])` appears character-identically in 2 files — packages/preact-query/src/useMutation.ts, packages/react-query/src/useMutation.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/preact-query/src/errorBoundaryUtils.ts:96— `result.isError && !errorResetBoundary.isReset() && !result.isFetching && query && ((suspense && result.data === undefined) || shouldThrowErr…` appears character-identically in 2 files — packages/preact-query/src/errorBoundaryUtils.ts, packages/react-query/src/errorBoundaryUtils.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/angular-query-experimental/src/inject-mutation.ts:280— `state.isError && shouldThrowError(observer.options.throwOnError, [state.error])` appears character-identically in 2 files — packages/angular-query-experimental/src/inject-mutation.ts, packages/solid-query/src/useMutation.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/vue-query/src/useBaseQuery.ts:153— `typeof clonedOptions.enabled === 'function' && clonedOptions.enabled.length === 0` appears character-identically in 2 files — packages/vue-query/src/useBaseQuery.ts, packages/vue-query/src/useQueries.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/preact-query/src/useBaseQuery.ts:57— `typeof options !== 'object' || Array.isArray(options)` appears character-identically in 2 files — packages/preact-query/src/useBaseQuery.ts, packages/react-query/src/useBaseQuery.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/angular-query-experimental/scripts/prepack.js:57— `typeof value === 'object' && value !== null` appears character-identically in 2 files — packages/angular-query-experimental/scripts/prepack.js, packages/query-devtools/src/Devtools.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/query-core/src/focusManager.ts:25— `typeof window !== 'undefined' && window.addEventListener` appears character-identically in 2 files — packages/query-core/src/focusManager.ts, packages/query-core/src/onlineManager.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/query-devtools/src/nativeObjectType.ts:35— `value === null || typeof value !== 'object'` appears character-identically in 2 files — packages/query-devtools/src/nativeObjectType.ts, packages/query-devtools/src/utils.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.
redundant comment packages/angular-query-experimental/src/__tests__/inject-mutation.test.ts:977— "Set initial data" repeats the code it sits on: 3 of its 3 words (set, initial, data) are already in `queryClient.setQueryData(testQueryKey, 'initial')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/preact-query/src/__tests__/useInfiniteQuery.test.tsx:550— 5 comments in this file only repeat the code they sit on (lines 550, 557, 564, 572, 752), for example "Fetch next page". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/preact-query/src/__tests__/useQueries.test-d.tsx:676— "handles when queryFn returns a Promise" repeats the code it sits on: 4 of its 5 words (query, fn, returns, promise) are already in `const result5 = useQueries({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/query-codemods/src/v4/key-transformation.cjs:162— "This function transforms usages of `useQueries`." repeats the code it sits on: 4 of its 5 words (transforms, usages, use, queries) are already in `transformUseQueriesUsages({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/query-codemods/src/v4/key-transformation.cjs:169— "This function transforms usages of `QueryClient`." repeats the code it sits on: 4 of its 5 words (transforms, usages, query, client) are already in `transformQueryClientUsages({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/query-codemods/src/v4/key-transformation.cjs:177— "This function transforms usages of `QueryCache`." repeats the code it sits on: 4 of its 5 words (transforms, usages, query, cache) are already in `transformQueryCacheUsages({ jscodeshift, utils, root, filePath, packageName })`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs:120— "Removing the `keepPreviousData` property from the object." repeats the code it sits on: 5 of its 6 words (keep, previous, data, property, object) are already in `const mutableObjectExpressionProperties =`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/query-core/src/__tests__/mutationObserver.test.tsx:607— "Call setOptions with the same options" repeats the code it sits on: 3 of its 3 words (call, set, options) are already in `mutationObserver.setOptions({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/query-core/src/__tests__/query.test.tsx:1530— "Now create an observer with initialData" repeats the code it sits on: 4 of its 5 words (create, observer, initial, data) are already in `const observer = new QueryObserver(queryClient, {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/query-core/src/query.ts:775— "Create query function context" repeats the code it sits on: 4 of its 4 words (create, query, function, context) are already in `const createQueryFnContext = (): QueryFunctionContext<TQueryKey> =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/query-devtools/src/contexts/PiPContext.tsx:80— "Clear Delegated Events" repeats the code it sits on: 3 of its 3 words (clear, delegated, events) are already in `clearDelegatedEvents(pip.document)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/react-query/src/__tests__/useInfiniteQuery.test.tsx:548— 5 comments in this file only repeat the code they sit on (lines 548, 555, 562, 570, 750), for example "Fetch next page". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/react-query/src/__tests__/useQueries.test-d.tsx:675— "handles when queryFn returns a Promise" repeats the code it sits on: 4 of its 5 words (query, fn, returns, promise) are already in `const result5 = useQueries({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/solid-query/src/__tests__/useInfiniteQuery.test.tsx:586— 5 comments in this file only repeat the code they sit on (lines 586, 593, 600, 608, 815), for example "Fetch next page". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/solid-query/src/__tests__/useQueries.test-d.tsx:708— "handles when queryFn returns a Promise" repeats the code it sits on: 4 of its 5 words (query, fn, returns, promise) are already in `const result5 = useQueries(() => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:550— "The base pages of the first type line that has any." repeats the code it sits on: 4 of its 5 words (base, pages, type, line) are already in `async function findBasePages(outputDir: string, typeLines: Array<string>)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/generate-labeler-config.ts:18— "Check if REDACTED exists for the folder before adding it" repeats the code it sits on: 5 of its 6 words (check, package, json, exists, folder) are already in `if (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Deprecated: @ungap/structured-clone REDACTED:13485— @ungap/structured-clone 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: copy-concurrently REDACTED:15319— copy-concurrently 1.0.5 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: figgy-pudding REDACTED:16604— figgy-pudding 3.5.2 is resolved in REDACTED and is marked deprecated by its publisher: "This module is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: fs-write-stream-atomic REDACTED:16781— fs-write-stream-atomic 1.0.10 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". 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:16893— 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:16902— 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:17280— 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: move-concurrently REDACTED:18547— move-concurrently 1.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: node-domexception REDACTED:18741— node-domexception 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: resolve-url REDACTED:20138— resolve-url 0.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "https://github.com/lydell/resolve-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:20189— rimraf 2.7.1 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-resolve REDACTED:20796— source-map-resolve 0.5.3 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-resolve#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-url REDACTED:20803— source-map-url 0.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: unplugin-vue-router REDACTED:21739— unplugin-vue-router 0.19.2 is resolved in REDACTED and is marked deprecated by its publisher: "Merged into vuejs/router. Migrate: https://router.vuejs.org/guide/migration/v4-to-v5.html". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: urix REDACTED:21896— urix 0.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Please see https://github.com/lydell/urix#deprecated". 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:22501— 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.
Mock-dominated test: should catch and log errors in `persistClient` packages/query-persist-client-core/src/__tests__/persist.test.ts:46— This test sets up 3 test doubles (for example `vi
.spyOn`) against 1 real object(s) of its own, and its only verification is 5 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: should notify queryCache and mutationCache if focused packages/query-core/src/__tests__/queryClient.test.tsx:2840— This test sets up 3 test doubles (for example `vi.spyOn`) against 1 real object(s) of its own, and its only verification is 5 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: should notify queryCache and mutationCache if online packages/query-core/src/__tests__/queryClient.test.tsx:2869— This test sets up 3 test doubles (for example `vi.spyOn`) against 1 real object(s) of its own, and its only verification is 5 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: should notify queryCache and mutationCache after multiple mounts and single unmount packages/query-core/src/__tests__/queryClient.test.tsx:3148— This test sets up 3 test doubles (for example `vi.spyOn`) against 1 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.
Mock-dominated test: should not notify queryCache and mutationCache after multiple mounts/unmounts packages/query-core/src/__tests__/queryClient.test.tsx:3182— This test sets up 3 test doubles (for example `vi.spyOn`) against 1 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.
Mock-dominated test: should not schedule timers for disabled observers packages/query-core/src/__tests__/queryObserver.test.tsx:1406— This test sets up 3 test doubles (for example `vi.spyOn`) against 1 real object(s) of its own, and its only verification is 2 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: should not schedule timers on the server packages/query-core/src/__tests__/queryObserver.test.tsx:1428— This test sets up 3 test doubles (for example `vi.spyOn`) against 1 real object(s) of its own, and its only verification is 2 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: should proxy calls to globalThis setTimeout/clearTimeout by default packages/query-core/src/__tests__/timeoutManager.test.tsx:39— This test sets up 4 test doubles (for example `vi.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.
Mock-dominated test: should preserve the mount/unmount contract when the provider is swapped while disconnected packages/lit-query/src/__tests__/QueryClientProvider.test.ts:115— This test sets up 4 test doubles (for example `vi.spyOn`) against 2 real object(s) of its own, and its only verification is 13 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.
Orphaned file packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs: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/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.output.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 packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.input.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 packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.output.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 packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.input.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 packages/query-codemods/src/v5/is-loading/is-loading.cjs: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/angular-query-persist-client/src/with-persist-query-client.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.
Documentation: no build, run or usage example packages/preact-query/README.md:1— `preact-query` is a published package (`REDACTED` without `"private": true`) and neither `packages/preact-query/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/react-query/README.md:1— `react-query` is a published package (`REDACTED` without `"private": true`) and neither `packages/react-query/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/solid-query/README.md:1— `solid-query` is a published package (`REDACTED` without `"private": true`) and neither `packages/solid-query/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/svelte-query/README.md:1— `svelte-query` is a published package (`REDACTED` without `"private": true`) and neither `packages/svelte-query/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Outdated (npm): @solid-primitives/storage packages/query-devtools/package.json:67— @solid-primitives/storage is pinned at 1.3.11; registry.npmjs.org publishes 4.4.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 36 significant file(s) lose their only recent owner: REDACTED, oxlint.config.ts, packages/preact-query/src/useInfiniteQuery.ts, packages/react-query/src/useInfiniteQuery.ts, packages/preact-query/src/infiniteQueryOptions.ts, packages/solid-query/src/useQuery.ts, packages/svelte-query/src/createQuery.ts, packages/preact-query/src/useMutation.ts (+28 more). Pair on, review, or document these before any departure.
D21 · Naming Consistency· `usePokemonID` spells `ID` where 92 names in the project spell it `Id` · ×1
`usePokemonID` spells `ID` where 92 names in the project spell it `Id` examples/solid/ssr-astro/src/components/SolidApp.tsx:26— 92 of 93 names in project root spell the token `Id` (92 of 93; unit: names in project root containing `Id`). Peers: PostComponent.postId (examples/angular/basic-angular-router/src/app/components/post.component.ts:24); AppComponent.postId (examples/angular/basic-persister/src/app/app.component.ts:12); PostComponent.setPostId (examples/angular/basic-persister/src/app/components/post.component.ts:19); PostComponent.postId (examples/angular/basic-persister/src/app/components/post.component.ts:20); PostsComponent.setPostId (examples/angular/basic-persister/src/app/components/posts.component.ts:18). Rename to `usePokemonId`. [rule N6]
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 7 of 200 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; 200 of the 535 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: packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs, packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.output.tsx, packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.input.tsx, packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.output.tsx, packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.input.tsx, packages/query-codemods/src/v5/is-loading/is-loading.cjs, packages/angular-query-persist-client/src/with-persist-query-client.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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
README/code drift docs/framework/react/guides/mutations.md:66— docs/framework/react/guides/mutations.md names React 16, but the manifest declares `react` ^19.3.1. 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.
No SAST .github/workflows/autofix.yml:4— 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 4 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.
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.
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 0/8 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 193/200 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~1.4 `!` null assertions per 1k TypeScript source lines — 82 assertion(s) across the 57626 source line(s) of the 339 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/query-devtools/src/Devtools.tsx (27), packages/query-devtools/src/Explorer.tsx (10), packages/solid-query/src/useQueries.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Outdated (npm): @algolia/client-search — @algolia/client-search is pinned at 5.59.0; registry.npmjs.org publishes 5.64.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): @angular/common — @angular/common is pinned at 22.2.4; registry.npmjs.org publishes 22.2.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): @angular/compiler — @angular/compiler is pinned at 22.2.4; registry.npmjs.org publishes 22.2.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): @angular/core — @angular/core is pinned at 22.2.4; registry.npmjs.org publishes 22.2.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): @angular/forms — @angular/forms is pinned at 22.2.4; registry.npmjs.org publishes 22.2.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): @angular/platform-browser — @angular/platform-browser is pinned at 22.2.4; registry.npmjs.org publishes 22.2.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): @angular/router — @angular/router is pinned at 22.2.4; registry.npmjs.org publishes 22.2.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): @astrojs/check — @astrojs/check is pinned at 0.9.10; registry.npmjs.org publishes 0.9.12 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): @astrojs/node — @astrojs/node is pinned at 11.1.9; registry.npmjs.org publishes 11.1.13 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): @astrojs/solid-js — @astrojs/solid-js is pinned at 7.0.2; registry.npmjs.org publishes 7.1.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): @lit-labs/ssr — @lit-labs/ssr is pinned at 3.3.1; registry.npmjs.org publishes 4.1.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): @solidjs/meta — @solidjs/meta is pinned at 0.29.4; registry.npmjs.org publishes 0.29.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): @solidjs/router — @solidjs/router is pinned at 1.0.1; registry.npmjs.org publishes 1.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @solidjs/start — @solidjs/start is pinned at 2.2.0; registry.npmjs.org publishes 2.2.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): @tailwindcss/vite — @tailwindcss/vite is pinned at 4.3.3; registry.npmjs.org publishes 4.3.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tanstack/match-sorter-utils — @tanstack/match-sorter-utils is pinned at 9.1.2; registry.npmjs.org publishes 9.2.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): @tanstack/react-pacer — @tanstack/react-pacer is pinned at 0.23.0; registry.npmjs.org publishes 0.24.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): @tanstack/solid-virtual — @tanstack/solid-virtual is pinned at 3.13.52; registry.npmjs.org publishes 3.13.53 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/utils — @typescript-eslint/utils is pinned at 8.72.0; registry.npmjs.org publishes 8.72.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): @vitejs/plugin-react — @vitejs/plugin-react is pinned at 6.2.1; registry.npmjs.org publishes 6.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): @vue/devtools-api — @vue/devtools-api is pinned at 6.6.4; registry.npmjs.org publishes 8.2.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): @zag-js/preact — @zag-js/preact is pinned at 1.46.0; registry.npmjs.org publishes 1.48.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): @zag-js/toast — @zag-js/toast is pinned at 1.46.0; registry.npmjs.org publishes 1.48.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): astro — astro is pinned at 7.4.4; registry.npmjs.org publishes 7.4.12 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): expo — expo is pinned at 58.0.22; registry.npmjs.org publishes 58.0.25 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.
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/ssr.test.ts:19— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/useMutation.test.ts:582— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/useMutation.test.ts:640— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/useMutation.test.ts:661— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/useQueries.test.ts:422— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/useQuery.test.ts:405— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:62— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:76— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:90— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:101— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:149— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:163— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:178— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:192— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:207— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:222— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:252— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/vue-query/src/__tests__/vueQueryPlugin.test.ts:271— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): should transition injectQueries to an idle state (once injectQueries is functional) packages/angular-query-persist-client/src/__tests__/with-persist-query-client.test.ts:155— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
doc comments repeat the names packages/angular-query-experimental/src/devtools-panel/types.ts:6— 1 of 50 documented parameters and 1 of 140 summaries in `@tanstack/angular-query-experimental` only repeat the member or parameter name (e.g. "Options for `injectDevtoolsPanel`." for `InjectDevtoolsPanelOptions`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/preact-query/src/types.ts:309— 0 of 70 documented parameters and 2 of 121 summaries in `@tanstack/preact-query` only repeat the member or parameter name (e.g. "The result of `useQuery`. Same as ." for `UseQueryResult`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/query-core/src/query.ts:131— 4 of 172 documented parameters and 2 of 648 summaries in `@tanstack/query-core` only repeat the member or parameter name (e.g. "The options of this fetch." for `fetchOptions`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/query-devtools/src/utils.tsx:93— 0 of 55 documented parameters and 3 of 119 summaries in `@tanstack/query-devtools` only repeat the member or parameter name (e.g. "Returns the color of a query status label." for `getQueryStatusColorByLabel`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/query-persist-client-core/src/createPersister.ts:25— 0 of 20 documented parameters and 3 of 56 summaries in `@tanstack/query-persist-client-core` only repeat the member or parameter name (e.g. "The hash of the query." for `queryHash`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/react-query/src/types.ts:310— 0 of 63 documented parameters and 2 of 120 summaries in `@tanstack/react-query` only repeat the member or parameter name (e.g. "The result of `useQuery`. Same as ." for `UseQueryResult`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/solid-query/src/types.ts:333— 0 of 41 documented parameters and 1 of 68 summaries in `@tanstack/solid-query` only repeat the member or parameter name (e.g. "The result of `useMutation`. Same as ." for `UseMutationResult`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/svelte-query/src/types.ts:28— 0 of 48 documented parameters and 8 of 67 summaries in `@tanstack/svelte-query` only repeat the member or parameter name (e.g. "Options for createBaseQuery" for `CreateBaseQueryOptions`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/svelte-query-persist-client/src/utils.svelte.ts:5— 1 of 1 documented parameters and 0 of 1 summaries in `@tanstack/svelte-query-persist-client` only repeat the member or parameter name (e.g. "The initial value of `current`." for `initial`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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 8 file(s) — `integrations/react/next-15/app/make-query-client.ts`, `integrations/react/next-16/app/make-query-client.ts`, `knip.ts`, `packages/eslint-plugin-query/src/index.ts`, `packages/query-core/src/mutation.ts`, … (+3 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
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.
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.
Run 01a1d9bf-9506-7dd5-a6e0-aa88296ed93d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 33 · Warnings: 1316 · Recommendations: 1084 · Info: 79 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 11:09 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.