TanStack/query

Executive summary

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 in part because we found no access checks on the code's endpoints or handlers. It scores 41 out of 100, which the At risk rating leaves unchanged.

Security and Compliance, at 18, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 18 points. Fixing the password or key in the code comes next, worth about 5 points. Raising Security and Compliance to 70 would lift the score to about 59.

Fifty-five known security holes in the packages the code depends on can be used by attackers. Twenty-two passwords or keys in the code's history and one in the code are open to anyone who can read the repository, and two automatic updates take new releases before a bad one can be spotted. Replacing each exposed password or key, updating the vulnerable packages and setting a waiting period for automatic updates would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code, and correcting the flagged pipeline settings would deal with the weakness in the build pipeline's configuration. The three sets of files in separate parts that keep changing together need that dependency made explicit.

The product code is 73,134 lines, about €160,000 to rebuild.

Code Health 67 Adequate Architecture 97 ★ Exemplary Maturity 63 Adequate, capped by Architecture documentation Production Readiness 48 Weak, capped by Observability and Security & performance tooling Security and Compliance 18 ⚠ Critical, capped by Secrets (history), Static Analysis (SAST), Dependency Vulnerabilities, Supply-chain Provenance & Signing and Access Controls Accessibility 76 Strong Performance 100 ★ Exemplary

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Security and Compliance 18 · counts for 46%Production Readiness 48 · counts for 25%Maturity 63 · counts for 14%Code Health 67 · counts for 8%Accessibility 76 · counts for 4%Architecture 97 · counts for 2%Performance 100 · counts for 1%

If Security and Compliance rose from 18 to 70, the lowest score rated Strong, the score would rise from 41 to about 59.

Code composition: what the lines of code are

Product code 38%Tests 62%

New since the last survey: 190 findings

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

Cognitive Complexity · infiniteQueryBehavior.infiniteQueryBehavior.onFetch::fetchFn (cognitive 18) packages/query-core/src/infiniteQueryBehavior.ts
Test Quality · No assertions: should be typed if key is tagged packages/vue-query/src/__tests__/queryClient.test-d.ts
Test Quality · No assertions: should be typed including error if key is tagged packages/vue-query/src/__tests__/queryClient.test-d.ts
Test Quality · No assertions: should infer unknown if key is not tagged packages/vue-query/src/__tests__/queryClient.test-d.ts
Test Quality · No assertions: should accept a ref key packages/vue-query/src/__tests__/queryClient.test-d.ts
Test Quality · No assertions: should infer passed generic if passed packages/vue-query/src/__tests__/queryClient.test-d.ts
Test Quality · No assertions: should accept reactive filters without fetchStatus packages/vue-query/src/__tests__/queryClient.test-d.ts
Test Quality · No assertions: should reject a fetchStatus filter packages/vue-query/src/__tests__/queryClient.test-d.ts
Test Quality · No assertions: should work when passed to useQueries packages/vue-query/src/__tests__/queryOptions.test-d.ts
Test Quality · No assertions: should work when passed to query with enabled: false packages/vue-query/src/__tests__/queryOptions.test-d.ts
Test Quality · No assertions: should work when passed to query with skipToken packages/vue-query/src/__tests__/queryOptions.test-d.ts
Test Quality · No assertions: should return the proper type when passed to getQueryState packages/vue-query/src/__tests__/queryOptions.test-d.ts
Test Quality · No assertions: should infer even if there is a conditional skipToken packages/vue-query/src/__tests__/queryOptions.test-d.ts
Test Quality · No assertions: should infer to unknown if we disable a query with just a skipToken packages/vue-query/src/__tests__/queryOptions.test-d.ts
Test Quality · No assertions: should allow undefined response in initialData packages/vue-query/src/__tests__/queryOptions.test-d.ts
Test Quality · No assertions: should accept filters without fetchStatus packages/vue-query/src/__tests__/useIsFetching.test-d.ts
Test Quality · No assertions: should accept reactive filters without fetchStatus packages/vue-query/src/__tests__/useIsFetching.test-d.ts
Test Quality · No assertions: should reject a fetchStatus filter packages/vue-query/src/__tests__/useIsFetching.test-d.ts
Test Quality · No assertions: should return the result typed with the exported MutationResult packages/vue-query/src/__tests__/useMutation.test-d.tsx
Test Quality · No assertions: should accept filters without fetchStatus packages/svelte-query/tests/useIsFetching/useIsFetching.test-d.ts
Test Quality · No assertions: should reject a fetchStatus filter packages/svelte-query/tests/useIsFetching/useIsFetching.test-d.ts
Test Quality · No assertions: should accept filters without fetchStatus packages/solid-query/src/__tests__/useIsFetching.test-d.tsx
Test Quality · No assertions: should reject a fetchStatus filter packages/solid-query/src/__tests__/useIsFetching.test-d.tsx
Test Quality · No assertions: should default to unknown when the query function is unspecified packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should infer the result type from the query function packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should be possible to specify the result type packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should be possible to specify the error type packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should provide the result type in the configuration packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should be possible to specify a union type as result type packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should error when the query function result does not match with the specified type packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should infer the result type from a generic query function packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should accept a query function typed with 'QueryFunction' packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should handle query functions that return Promise<any> packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should handle wrapped queries with custom fetcher passed as inline queryFn packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should handle wrapped queries with custom fetcher passed directly to useQuery packages/solid-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should preserve discriminated union narrowing in setQueryData updaterFn packages/react-query/src/__tests__/queryOptions.test-d.tsx
Test Quality · No assertions: should accept filters without fetchStatus packages/react-query/src/__tests__/useIsFetching.test-d.tsx
Test Quality · No assertions: should reject a fetchStatus filter packages/react-query/src/__tests__/useIsFetching.test-d.tsx
Test Quality · No assertions: should default to unknown when the query function is unspecified packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should infer the result type from the query function packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should be possible to specify the result type packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should be possible to specify the error type packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should provide the result type in the configuration packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should be possible to specify a union type as result type packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should error when the query function result does not match with the specified type packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should infer the result type from a generic query function packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should accept a query function typed with 'QueryFunction' packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should handle query functions that return Promise<any> packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should handle wrapped queries with custom fetcher passed as inline queryFn packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should handle wrapped queries with custom fetcher passed directly to useQuery packages/react-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should accept filters without fetchStatus packages/preact-query/src/__tests__/useIsFetching.test-d.tsx
Test Quality · No assertions: should reject a fetchStatus filter packages/preact-query/src/__tests__/useIsFetching.test-d.tsx
Test Quality · No assertions: should default to unknown when the query function is unspecified packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should infer the result type from the query function packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should be possible to specify the result type packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should be possible to specify the error type packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should provide the result type in the configuration packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should be possible to specify a union type as result type packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should error when the query function result does not match with the specified type packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should infer the result type from a generic query function packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should accept a query function typed with 'QueryFunction' packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should handle query functions that return Promise<any> packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should handle wrapped queries with custom fetcher passed as inline queryFn packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should handle wrapped queries with custom fetcher passed directly to useQuery packages/preact-query/src/__tests__/useQuery.test-d.tsx
Test Quality · No assertions: should accept filters without fetchStatus packages/lit-query/src/__tests__/useIsFetching.test-d.ts
Test Quality · No assertions: should reject a fetchStatus filter packages/lit-query/src/__tests__/useIsFetching.test-d.ts
Test Quality · No assertions: should accept filters without fetchStatus packages/angular-query-experimental/src/__tests__/inject-is-fetching.test-d.ts
Test Quality · No assertions: should reject a fetchStatus filter packages/angular-query-experimental/src/__tests__/inject-is-fetching.test-d.ts
Dependency Hygiene · Deprecated: eslint REDACTED
Dependency Hygiene · Deprecated: eslint packages/eslint-plugin-query/package.json
Dependency Hygiene · Deprecated: vue packages/vue-query/package.json
Dependency Hygiene · Deprecated: vue packages/vue-query/package.json
REDACTED Scanning · REDACTED
Churn × Complexity Hotspots · Hotspot: packages/query-devtools/src/Devtools.tsx packages/query-devtools/src/Devtools.tsx
Churn × Complexity Hotspots · Repeated repair: examples/react/chat/src/index.tsx examples/react/chat/src/index.tsx
Boundary Type-Coupling · Cross-context type Theme (query-devtools → angular-query-experimental) packages/angular-query-experimental/src/devtools-panel/types.ts
Boundary Type-Coupling · Cross-context type DevtoolsButtonPosition (query-devtools → angular-query-experimental) packages/angular-query-experimental/src/devtools/types.ts
Boundary Type-Coupling · Cross-context type DevtoolsPosition (query-devtools → angular-query-experimental) packages/angular-query-experimental/src/devtools/types.ts
Boundary Type-Coupling · Cross-context type Theme (query-devtools → angular-query-experimental) packages/angular-query-experimental/src/devtools/types.ts
Boundary Type-Coupling · Cross-context type DevtoolsButtonPosition (query-devtools → preact-query-devtools) packages/preact-query-devtools/src/PreactQueryDevtools.tsx
Boundary Type-Coupling · Cross-context type DevtoolsPosition (query-devtools → preact-query-devtools) packages/preact-query-devtools/src/PreactQueryDevtools.tsx
Boundary Type-Coupling · Cross-context type Theme (query-devtools → preact-query-devtools) packages/preact-query-devtools/src/PreactQueryDevtools.tsx
Boundary Type-Coupling · Cross-context type Theme (query-devtools → preact-query-devtools) packages/preact-query-devtools/src/PreactQueryDevtoolsPanel.tsx
Boundary Type-Coupling · Cross-context type QueryObserverResult (query-core → preact-query) packages/preact-query/src/errorBoundaryUtils.ts
Boundary Type-Coupling · Cross-context type ThrowOnError (query-core → preact-query) packages/preact-query/src/errorBoundaryUtils.ts
Boundary Type-Coupling · Cross-context type QueryObserverResult (query-core → preact-query) packages/preact-query/src/suspense.ts
Boundary Type-Coupling · Cross-context type QueryObserverResult (query-core → preact-query) packages/preact-query/src/useBaseQuery.ts
Boundary Type-Coupling · Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/createCacheSubscriptionRegistry.ts
Boundary Type-Coupling · Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/createCacheSubscriptionRegistry.ts
Boundary Type-Coupling · Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/contexts/types.ts
Boundary Type-Coupling · Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/contexts/types.ts
Boundary Type-Coupling · Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/contexts/types.ts
Boundary Type-Coupling · Cross-context type QueryCacheNotifyEvent (query-core → query-devtools) packages/query-devtools/src/contexts/types.ts
Boundary Type-Coupling · Cross-context type MutationCacheNotifyEvent (query-core → query-devtools) packages/query-devtools/src/contexts/types.ts
Boundary Type-Coupling · Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/contexts/types.ts
Boundary Type-Coupling · Cross-context type DevtoolsButtonPosition (query-devtools → react-query-devtools) packages/react-query-devtools/src/ReactQueryDevtools.tsx
Boundary Type-Coupling · Cross-context type DevtoolsPosition (query-devtools → react-query-devtools) packages/react-query-devtools/src/ReactQueryDevtools.tsx
Boundary Type-Coupling · Cross-context type Theme (query-devtools → react-query-devtools) packages/react-query-devtools/src/ReactQueryDevtools.tsx
Boundary Type-Coupling · Cross-context type Theme (query-devtools → react-query-devtools) packages/react-query-devtools/src/ReactQueryDevtoolsPanel.tsx
Boundary Type-Coupling · Cross-context type QueryObserverResult (query-core → react-query) packages/react-query/src/errorBoundaryUtils.ts

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

Fixed since the last survey: 169 findings

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

Cyclomatic Complexity · with-devtools.withDevtools (cyclomatic 16) packages/angular-query-experimental/src/devtools/with-devtools.ts
Cognitive Complexity · infiniteQueryBehavior.infiniteQueryBehavior.onFetch (cognitive 23) packages/query-core/src/infiniteQueryBehavior.ts
Test Quality · No assertions: should not change state if unmounted packages/preact-query/src/__tests__/useMutation.test.tsx
Test Quality · No assertions: should not change state if unmounted packages/react-query/src/__tests__/useMutation.test.tsx
Test Quality · No assertions: should not change state if unmounted packages/solid-query/src/__tests__/useQueries.test.tsx
Test Quality · No assertions: should not change state if unmounted packages/solid-query/src/__tests__/useMutation.test.tsx
Test Quality · No assertions: should not change state if unmounted packages/solid-query/src/__tests__/useIsMutating.test.tsx
Explicit Debt · TodoComment packages/solid-query/src/__tests__/suspense.test.tsx
Explicit Debt · TodoComment packages/solid-query/src/__tests__/suspense.test.tsx
Dependency Vulnerabilities · Critical vulnerability: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Critical vulnerability: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Critical vulnerability: [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 · Medium CVE: [GHSA redacted] REDACTED
Code Duplication · Duplicated block with local edits (66 matched lines × 2 locations) packages/query-core/src/queryClient.ts
Code Duplication · Wholesale file copy (59 identical lines × 2 files) packages/preact-query/src/useMutationState.ts
Code Duplication · Wholesale file copy (51 identical lines × 2 files) packages/preact-query/src/useBaseQuery.ts
Code Duplication · Duplicated block (41 lines × 3 locations) packages/preact-query/src/useMutationState.ts
Code Duplication · Duplicated block (38 lines × 27 locations) oxlint.config.ts
Code Duplication · Duplicated block (30 lines × 2 locations) packages/angular-query-experimental/src/inject-is-fetching.ts
Code Duplication · Duplicated block (28 lines × 3 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (28 lines × 2 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (28 lines × 10 locations) packages/query-devtools/src/icons/index.tsx
Code Duplication · Duplicated block (27 lines × 27 locations) oxlint.config.ts
Code Duplication · Duplicated block (26 lines × 2 locations) integrations/react-next-15/app/client-component.tsx
Code Duplication · Duplicated block (26 lines × 2 locations) packages/preact-query/src/useSuspenseQuery.ts
Code Duplication · Duplicated block (26 lines × 2 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (26 lines × 4 locations) packages/react-query-devtools/oxlint.config.ts
Code Duplication · Duplicated block (25 lines × 16 locations) packages/lit-query/root.tsdown.config.js
Code Duplication · Duplicated block with local edits (25 matched lines × 2 locations) packages/preact-query/src/usePrefetchQuery.tsx
Code Duplication · Duplicated block with local edits (25 matched lines × 2 locations) packages/svelte-query/src/useMutationState.svelte.ts
Code Duplication · Duplicated block (24 lines × 2 locations) packages/query-codemods/src/v5/remove-overloads/transformers/filter-aware-usage-transformer.cjs
Code Duplication · Duplicated block (24 lines × 2 locations) packages/solid-query/src/infiniteQueryOptions.ts
Code Duplication · Duplicated block (24 lines × 2 locations) packages/vue-query/src/queryOptions.ts
Code Duplication · Duplicated block (23 lines × 2 locations) packages/preact-query/src/QueryErrorResetBoundary.tsx
Code Duplication · Duplicated block (23 lines × 2 locations) packages/preact-query/src/useInfiniteQuery.ts
Code Duplication · Duplicated block (23 lines × 8 locations) packages/query-devtools/src/icons/index.tsx
Code Duplication · Duplicated block (22 lines × 2 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (22 lines × 2 locations) packages/query-devtools/src/icons/index.tsx
Code Duplication · Duplicated block (22 lines × 3 locations) packages/query-devtools/tsdown.config.ts
Code Duplication · Duplicated block (22 lines × 2 locations) packages/vue-query/src/mutationOptions.ts
Code Duplication · Duplicated block (21 lines × 2 locations) packages/query-core/src/focusManager.ts
Code Duplication · Duplicated block with local edits (21 matched lines × 2 locations) packages/query-core/src/queriesObserver.ts
Code Duplication · Duplicated block (21 lines × 2 locations) packages/query-core/src/queryClient.ts
Code Duplication · Duplicated block (21 lines × 3 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (21 lines × 2 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (21 lines × 2 locations) packages/vue-query/src/queryClient.ts
Code Duplication · Duplicated block (20 lines × 5 locations) packages/angular-query-experimental/src/infinite-query-options.ts
Code Duplication · Duplicated block (20 lines × 14 locations) packages/angular-query-experimental/src/infinite-query-options.ts
Code Duplication · Duplicated block (19 lines × 2 locations) integrations/react-webpack-4/src/App.js
Code Duplication · Duplicated block (19 lines × 4 locations) packages/query-devtools/src/icons/index.tsx
Code Duplication · Duplicated block (19 lines × 2 locations) packages/vue-query/src/queryClient.ts
Code Duplication · Duplicated block (18 lines × 2 locations) integrations/react-next-15/app/providers.tsx
Code Duplication · Duplicated block (18 lines × 2 locations) packages/preact-query/src/useQuery.ts
Code Duplication · Duplicated block (18 lines × 3 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (18 lines × 2 locations) packages/query-devtools/src/DevtoolsComponent.tsx
Code Duplication · Duplicated block (18 lines × 3 locations) packages/svelte-query/src/createInfiniteQuery.ts
Code Duplication · Duplicated block (18 lines × 2 locations) packages/svelte-query/src/types.ts
Code Duplication · Duplicated block (18 lines × 2 locations) packages/vue-query/src/queryClient.ts
Code Duplication · Duplicated block (17 lines × 3 locations) integrations/react-next-14/app/layout.tsx
Code Duplication · Duplicated block (17 lines × 3 locations) packages/lit-query/src/queryOptions.ts
Code Duplication · Duplicated block (17 lines × 3 locations) packages/preact-query/src/useQuery.ts
Code Duplication · Duplicated block (17 lines × 5 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (17 lines × 3 locations) packages/query-devtools/src/icons/index.tsx
Code Duplication · Duplicated block (17 lines × 2 locations) packages/react-query/src/useQuery.ts
Code Duplication · Duplicated block (16 lines × 2 locations) integrations/react-next-14/app/client-component.tsx
Code Duplication · Duplicated block (16 lines × 6 locations) packages/angular-query-experimental/src/inject-infinite-query.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/preact-query-devtools/src/PreactQueryDevtools.tsx
Code Duplication · Duplicated block (16 lines × 5 locations) packages/query-devtools/src/icons/index.tsx
Code Duplication · Duplicated block (16 lines × 3 locations) packages/solid-query/src/useInfiniteQuery.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/angular-query-experimental/src/inject-mutation.ts
Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/preact-query-devtools/src/PreactQueryDevtools.tsx
Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/preact-query/src/useIsFetching.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/query-codemods/src/v5/keep-previous-data/utils/already-has-placeholder-data-property.cjs
Code Duplication · Duplicated block (14 lines × 2 locations) packages/query-persist-client-core/src/createPersister.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/vue-query/src/useIsFetching.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/preact-query-devtools/src/PreactQueryDevtoolsPanel.tsx
Code Duplication · Duplicated block (13 lines × 2 locations) packages/preact-query-devtools/src/index.ts
Code Duplication · Duplicated block (13 lines × 3 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (13 lines × 2 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (13 lines × 4 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (13 lines × 2 locations) packages/query-devtools/src/Explorer.tsx
Code Duplication · Duplicated block (13 lines × 2 locations) packages/solid-query-devtools/src/devtools.tsx
Code Duplication · Duplicated block (13 lines × 3 locations) packages/solid-query-devtools/tsdown.config.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/solid-query/src/queryOptions.ts
Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/angular-query-experimental/src/inject-mutation-state.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/lit-query/src/createMutationController.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/lit-query/src/types.ts
Code Duplication · Duplicated block (12 lines × 3 locations) packages/vue-query/src/useInfiniteQuery.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/preact-query/src/useQuery.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/query-codemods/src/utils/index.cjs
Code Duplication · Duplicated block (11 lines × 2 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (11 lines × 2 locations) packages/query-devtools/src/Devtools.tsx
Code Duplication · Duplicated block (11 lines × 2 locations) packages/svelte-query/src/createQuery.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/vue-query/src/useMutation.ts

Rebuild cost: about €160,000 · Estimate

Cost to rebuild	€55,000 to €280,000, for 913 to 2,895 hours of work, about 1.1 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 41. 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: 73,134 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: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

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

Raises the score by about 18 points · Medium effort · Access Controls

Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.

Raises the score by about 5 points · Low effort · REDACTED Scanning

Resolve the 18 High secret finding(s) in Secrets (history) — start with REDACTED (18).

Raises the score by about 6 points · Medium effort · Secrets (history)

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk

This code would cost about €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Security and Compliance, at 18 (Critical). 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 18 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.5 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 164,095 lines over the last 90 days, which is about 665,496 lines a year. At that pace, the extra work comes to an estimated 33.3 to 221.8 engineer-days a year, and it grows as more code changes.

How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.

Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history

What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

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.

159 modules, with 228 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; 119 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	1 angular-query-experimental.src.types	2 lit-query.src.accessor	3 preact-query.src.types	4 query-core.src.subscribable	5 query-core.src.hydration	6 query-core.src.retryer	7 query-core.src.types	8 query-core.src.utils	9 query-core.src.queryClient	11 lit-query.src.controllers.BaseController	12 preact-query.src.HydrationBoundary	13 query-core.src.queryObserver	14 query-devtools.src.contexts.types	15 query-persist-client-core.src.persist	25 query-core.src.queryCache	26 query-core.src.query	29 query-core.src.mutationObserver	32 query-core.src.mutation	34 query-core.src.mutationCache	39 vue-query.src.types
1 angular-query-experimental.src.types
2 lit-query.src.accessor
3 preact-query.src.types
4 query-core.src.subscribable
5 query-core.src.hydration																1		1
6 query-core.src.retryer							1
7 query-core.src.types					1	4									1	1			1
8 query-core.src.utils							2
9 query-core.src.queryClient							17	2							1				1
10 lit-query.src	3	7					6	2	8
11 lit-query.src.controllers.BaseController									1
12 preact-query.src.HydrationBoundary									1
13 query-core.src.queryObserver				1			3		1							2
14 query-devtools.src.contexts.types		2							1
15 query-persist-client-core.src.persist					3				1
16 angular-query-experimental.src.devtools-panel.types									1				2
17 angular-query-experimental.src.devtools.types									1				4
18 lit-query.src.createInfiniteQueryController	1	1					1		1	1
19 lit-query.src.createMutationController	1	1					1		1	1
20 lit-query.src.createQueriesController		1					2		1	1
21 lit-query.src.createQueryController	1	1					1		1	1
22 lit-query.src.useIsFetching		1						1	1	1
23 lit-query.src.useIsMutating		1						1	1	1
24 query-core.src.queriesObserver				1			2		1			1
25 query-core.src.queryCache				1			1	1	1			3				10
26 query-core.src.query						1	7		3			1			1
27 preact-query.src			7				2	2	13		1	1				1
28 query-core.src.infiniteQueryObserver							5		1			1				1
29 query-core.src.mutationObserver				1			3		1							1		1
30 query-persist-client-core.src							1	1	1					3		1
31 react-query.src			7				2	2	13		1	1				1
32 query-core.src.mutation						1	3		2							1	1		2
33 query-core.src					5	2	6	3	1							6		4
34 query-core.src.mutationCache				1			1	1	1							1	3	8
35 query-devtools.src		1											1			1		1
36 angular-query-experimental.src	1							2	1										1
37 solid-query.src		9	4				2	2	9							1			1
38 svelte-query.src	5	5			1			2	11										1
39 vue-query.src.types					1		1								1				1
40 vue-query.src			3						10										1	5

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 67% · Adequate ·

The Good

D3 · TypeScript God Classes 8.5 D17 · TypeScript Explicit Debt 9.9 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 R1 · React / TS Type Safety 10.0 R10 · React / TS Code Duplication 9.0 R2 · React / TS Cyclomatic Complexity 9.4 R3 · React / TS Large Files 7.1 R7 · React / TS Dead Code 8.9 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X5 · Repo Nullable reference types 9.3

The Bad

D1 · TypeScript Cyclomatic Complexity 6.7 D2 · TypeScript Cognitive Complexity 5.7 X3 · Repo Exception handling 6.0

The Ugly

X2 · Repo Cancellation propagation 4.0

At a glance — Architecture · 97% · Exemplary ·

The Good

D5 · TypeScript Coupling 9.4 D6 · TypeScript Cohesion (LCOM4) 10.0 D23 · TypeScript Boundary Type-Coupling 8.6 D26 · TypeScript Project Cohesion 10.0 D35 · TypeScript Change Coupling 9.9 AX10 · Repo Code composition 9.6 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0 R11 · React / TS Import Boundaries 9.3 R9 · React / TS Circular Imports 10.0

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

The Good

D15 · TypeScript Churn × Complexity Hotspots 10.0 D16 · TypeScript Bus Factor 8.1 D19 · TypeScript Documentation Quality 10.0 D34 · TypeScript Knowledge Freshness 9.5 M1 · Repo Documentation (README) 7.5 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 8.0

The Ugly

M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 48% · Weak · gated by P2, P3 ·

The Good

D9 · TypeScript Test Distribution 10.0 D10 · TypeScript Test Quality 7.2 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 R4 · React / TS Test Coverage 8.2 R6 · React / TS Tooling 10.0 R8 · React / TS Dependency Hygiene 7.5

The Bad

D12 · TypeScript Dependency Hygiene 6.2 D13 · TypeScript REDACTED Scanning 5.0

The Ugly

P2 · Repo Observability 0.0 P3 · Repo Security & performance tooling 3.0

At a glance — Security · 18% · Critical · gated by D28, D29, D30, D36, C2 ·

The Good

D43 · TypeScript Malicious Dependencies 10.0 D44 · TypeScript Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0

The Ugly

D28 · TypeScript Secrets (history) 0.0 D29 · TypeScript Static Analysis (SAST) 3.3 D30 · TypeScript Dependency Vulnerabilities 0.0 D36 · TypeScript Supply-chain Provenance & Signing 2.5 C2 · Repo Access Controls 0.0 X17 · Repo Uncapped recursion over a caller-supplied document 3.0 X24 · Repo Document value interpolated into markup unescaped 4.3

At a glance — Accessibility · 76% · Strong ·

The Good

AC2 · Repo Forms & labels 10.0 AC5 · Repo ARIA correctness 10.0

The Bad

AC3 · Repo Page structure 6.8 AC7 · Repo A11y enforcement 6.0

At a glance — Performance · 100% · Exemplary ·

The Good

PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A03:2025 — Software Supply Chain Failures	82	High / Critical
A07:2025 — Authentication Failures	24	High / Critical
A05:2025 — Injection	11	High / Critical

Roadmap

First, implement a global authentication guard with explicit public opt-outs and named role rules to enforce default-deny access controls. Next, immediately resolve the 18 high-severity secrets and 1 leaked secret found in the lock file to secure sensitive credentials. Finally, address the 48 deprecated dependencies and 46 high-severity vulnerabilities in the lock file to restore dependency hygiene and eliminate known security risks.

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.	+17.8 pts	Medium	Access Controls
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.	+4.8 pts	Low	REDACTED Scanning
Resolve the 18 High secret finding(s) in Secrets (history) — start with REDACTED (18).	+6.0 pts	Medium	Secrets (history)
Resolve the 48 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (48).	+5.2 pts	Medium	Dependency Hygiene
Resolve the 46 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (46).	+4.5 pts	Medium	Dependency Vulnerabilities
Adopt pino (or winston) and log at meaningful points in the services you run.	+4.0 pts	Medium	Observability
Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED.	+1.5 pts	Low	Secrets (history)
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.	+1.5 pts	Low	Static Analysis (SAST)

File quality

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

File	Score	Band	Worst signal
REDACTED	0.0	Slop	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	4.0	Mixed	Static Analysis (SAST): Medium: REDACTED
packages/vue-query/src/queryClient.ts	4.6	Mixed	God Classes: TooManyMethods: QueryClient
packages/solid-query/src/useQueries.ts	5.0	Mixed	Change Coupling: Boundary-crossing change coupling: useQueries.ts ↔ useQueries.ts
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
packages/solid-query/src/useBaseQuery.ts	5.9	Mixed	Cyclomatic Complexity: useBaseQuery.useBaseQuery (cyclomatic 34)
packages/vue-query/src/__tests__/useInfiniteQuery.test-d.tsx	6.0	Mixed	Explicit Debt: TodoComment
packages/svelte-query/tests/createInfiniteQuery/createInfiniteQuery.test-d.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/solid-query/src/__tests__/useInfiniteQuery.test-d.tsx	6.0	Mixed	Explicit Debt: TodoComment
packages/react-query/src/__tests__/useInfiniteQuery.test-d.tsx	6.0	Mixed	Explicit Debt: TodoComment
packages/preact-query/src/__tests__/useInfiniteQuery.test-d.tsx	6.0	Mixed	Explicit Debt: TodoComment
packages/lit-query/src/__tests__/createInfiniteQueryController.test-d.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/query-core/src/__tests__/queryClient.test-d.tsx	6.3	Mixed	Explicit Debt: TodoComment
REDACTED	6.9	Mixed	Static Analysis (SAST): Medium: REDACTED
packages/query-devtools/src/Devtools.tsx	7.0	Mixed	Cyclomatic Complexity: Devtools.DraggablePanel (cyclomatic 51)
packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts	7.0	Mixed	Test Quality: No assertions: should not allow excess properties
packages/vue-query/src/__tests__/mutationOptions.test-d.ts	7.0	Mixed	Test Quality: No assertions: should not allow excess properties
packages/vue-query/src/__tests__/queryClient.test-d.ts	7.0	Mixed	Test Quality: No assertions: should be typed if key is tagged
packages/vue-query/src/__tests__/queryOptions.test-d.ts	7.0	Mixed	Test Quality: No assertions: should not allow excess properties
packages/vue-query/src/__tests__/useMutation.test-d.tsx	7.0	Mixed	Test Quality: No assertions: should have possibly undefined data by default

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

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

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

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

Could not be resolved — 11

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 77 of 77 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 77 dimensions across the health lenses

D1D2D3D5D6D9D10D12D13D14D15D16D17D19D23D26D28D29D30D34D35D36D43D44AC2AC3AC5AC7AX10AX3AX4AX6AX8C2GD1IC1M1M2M3M4P1P10P2P3P4P6PF3R1R10R11R2R3R4R6R7R8R9X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X5

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, 2494 of 2565 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	—	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a178be-1184-7fc6-ac39-5c2eeeafa4c1.

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

Run transparency — what happened this run

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

D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `integrations/react-next-15/app/make-query-client.ts`, `integrations/react-next-16/app/make-query-client.ts`, `knip.ts`, `packages/angular-query-experimental/src/index.ts`, `packages/eslint-plugin-query/src/index.ts`, … (+8 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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').
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 102 further occurrence(s) are not listed individually; the score already reflects all 142.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 18 further occurrence(s) are not listed individually; the score already reflects all 58.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 352 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP 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

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
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.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.7 / 10Adequate✓ Tool-verified

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

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

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

25 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Devtools.DraggablePanel at 51.

Devtools.DraggablePanel (cyclomatic 51)packages/query-devtools/src/Devtools.tsx:416

Devtools.ContentView (cyclomatic 50)packages/query-devtools/src/Devtools.tsx:690

Explorer.Explorer (cyclomatic 39)packages/query-devtools/src/Explorer.tsx:284

useBaseQuery.useBaseQuery (cyclomatic 34)packages/solid-query/src/useBaseQuery.ts:124

generate-docs.addReferenceDetails (cyclomatic 33)REDACTED:712

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

What to do

Bring the 25 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Devtools.DraggablePanel (cyclomatic 51), Devtools.ContentView (cyclomatic 50), Explorer.Explorer (cyclomatic 39). — 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 25 together lifts Cyclomatic Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity5.7 / 10Adequate✓ Tool-verified

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

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

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

38 method(s) exceeded the cognitive complexity threshold of 15; the worst was Devtools.DraggablePanel at 73.

HydrationBoundary.HydrationBoundary (cognitive 21) · ×2packages/preact-query/src/HydrationBoundary.tsx:86

Devtools.DraggablePanel (cognitive 73)packages/query-devtools/src/Devtools.tsx:416

generate-docs.addReferenceDetails (cognitive 71)REDACTED:712

Devtools.ContentView (cognitive 48)packages/query-devtools/src/Devtools.tsx:690

QueryObserver.createResult (cognitive 33)packages/query-core/src/queryObserver.ts:589

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

What to do

Bring the 9 bodies over 30 down to 30 or less in Cognitive Complexity — start with Devtools.DraggablePanel (cognitive 73), generate-docs.addReferenceDetails (cognitive 71), Devtools.ContentView (cognitive 48). — 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 9 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.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes8.5 / 10Strong✓ Tool-verified

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

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

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

39 god class(es) detected.

FunctionTooLong: Devtools.stylesFactory · ×22packages/query-devtools/src/Devtools.tsx:2728

FileTooLong: src/Devtools.tsx · ×9packages/query-devtools/src/Devtools.tsx

MethodTooLong: Query.fetch · ×3packages/query-core/src/query.ts:703

ClassTooLong: QueryClient · ×3packages/vue-query/src/queryClient.ts:52

TooManyMethods: QueryClient · ×2packages/vue-query/src/queryClient.ts:52

What to do

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 9 FileTooLong finding(s) in God Classes — start with queryClient.ts (2), Devtools.tsx, index.tsx. — One of this dimension's main actionable groups (9 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).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D5 · Coupling9.4 / 10Stronggated by 3 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.

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

37 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 30 of the 37 (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 · ×3

What to do

Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

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

0 of 31 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality7.2 / 10Strong✓ Tool-verified

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

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

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

19 skipped (19 with a documented reason), 1903 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4840 tests (1 harness-style project(s) excluded from the assertion penalty).

No assertions: should re-export core query filters · ×917packages/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 · ×986packages/query-core/src/__tests__/OmitKeyof.test-d.ts:5

Mock-dominated test: should notify queryCache and mutationCache if focused · ×8packages/query-core/src/__tests__/queryClient.test.tsx:2752

Skipped (documented): (unnamed test) · ×19packages/vue-query/src/__tests__/ssr.test.ts:19

What to do

Resolve the 986 No direct assertions finding(s) in Test Quality — start with queryObserver.test-d.tsx (130), queryClient.test-d.tsx (129), infiniteQueryObserver.test-d.tsx (90). — One of this dimension's main actionable groups (986 recommendation-level).
Resolve the 917 No assertions finding(s) in Test Quality — start with queryOptions.test-d.ts (82), queryOptions.test-d.tsx (76), useQuery.test-d.tsx (72). — One of this dimension's main actionable groups (917 warning-level).
Resolve the 8 Mock-dominated test finding(s) in Test Quality — start with queryClient.test.tsx (4), queryObserver.test.tsx (2), timeoutManager.test.tsx. — One of this dimension's main actionable groups (8 recommendation-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D12 · Dependency Hygiene6.2 / 10Adequate✓ Tool-verified

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

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

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

47 outdated direct production npm dependency(ies) of 83 graded, 3 pinning defect(s), across 118 REDACTED (41 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 · ×3

Deprecated: @angular/animations · ×48REDACTED:4435

Outdated (npm): @solid-primitives/storagepackages/query-devtools/package.json:67

Outdated (npm): @algolia/client-search · ×46

What to do

Resolve the 48 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (48). — One of this dimension's main actionable groups (48 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 3 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D13 · REDACTED Scanning5.0 / 10Adequate✓ Tool-verified

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

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

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

1 secret(s) detected.

REDACTED

What to do

Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

0 of 83 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 83 production dependency(ies) this repository's committed lockfile resolves, across 41 product REDACTED manifest(s). Its 719 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 9 serious findings✓ Tool-verified

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

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

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

Top hotspots: packages/query-core/src/queryObserver.ts (18×29=522); packages/query-core/src/query.ts (16×25=400); packages/query-devtools/src/Devtools.tsx (5×50=250) Repeated repair below the complexity floor: examples/react/chat/src/index.tsx (3 of 4 changes were fixes)

Hotspot: packages/query-core/src/queryObserver.ts · ×8packages/query-core/src/queryObserver.ts:589

Repeated repair: examples/react/chat/src/index.tsxexamples/react/chat/src/index.tsx:25

What to do

Resolve the 8 Hotspot finding(s) in Churn × Complexity Hotspots — start with queryObserver.ts, query.ts, Devtools.tsx. — One of this dimension's main actionable groups (8 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.1 / 10Strong✓ Tool-verified

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

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

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

38 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 195 of the 517 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

Further sole-owners (lower concentration)

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).
Resolve the 1 Further sole-owners (lower concentration) 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.

Do you agree with this assessment?

D17 · Explicit Debt9.9 / 10Stronggated by 19 serious findings✓ Tool-verified

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

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

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

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

TodoComment · ×18packages/vue-query/src/__tests__/useInfiniteQuery.test-d.tsx:20

HackCommentpackages/vue-query/src/vueQueryPlugin.ts:128

What to do

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).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

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

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

1 of 1 documentation facets pass in full. 314 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D23 · Boundary Type-Coupling8.6 / 10Strong✓ Tool-verified

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

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

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

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

51 domain type(s) cross context boundaries across 72 contexts.

Cross-context type Accessor (lit-query → solid-query) · ×9packages/solid-query/src/QueryClientProvider.tsx:47

Cross-context type Accessor (lit-query → query-devtools) · ×6packages/query-devtools/src/createCacheSubscriptionRegistry.ts:25

Cross-context type Accessor (lit-query → svelte-query) · ×5packages/svelte-query/src/createBaseQuery.svelte.ts:20

Cross-context type Updater (query-core → vue-query) · ×4packages/vue-query/src/queryClient.ts:145

Cross-context type QueryObserverResult (query-core → preact-query) · ×3packages/preact-query/src/errorBoundaryUtils.ts:76

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

What to do

Resolve the 9 Cross-context type Accessor (lit-query → solid-query) finding(s) in Boundary Type-Coupling — start with QueryClientProvider.tsx, useBaseQuery.ts, useQuery.ts. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 6 Cross-context type Accessor (lit-query → query-devtools) finding(s) in Boundary Type-Coupling — start with types.ts (4), createCacheSubscriptionRegistry.ts (2). — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 Cross-context type Accessor (lit-query → svelte-query) finding(s) in Boundary Type-Coupling — start with createBaseQuery.svelte.ts, createInfiniteQuery.ts, createMutation.svelte.ts. — One of this dimension's main actionable groups (5 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 of 40 build units (npm) flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED

What to do

Resolve the 18 High secret finding(s) in Secrets (history) — start with REDACTED (18). — One of this dimension's main actionable groups (18 issue-level).
Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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.

Do you agree with this assessment?

D29 · Static Analysis (SAST)3.3 / 10Weak✓ Tool-verified

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

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

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

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

12 finding(s): 0 critical, 4 high, 8 medium, 0 low. semgrep hit a parse error in 24 file(s) — `integrations/react-next-15/app/make-query-client.ts` (lines 6–13), `integrations/react-next-16/app/make-query-client.ts` (lines 6–13), `knip.ts` (lines 18–58), `packages/angular-query-experimental/src/index.ts` (line 6), `packages/eslint-plugin-query/src/index.ts` (lines 76–78), … (+19 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

+ 2 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.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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

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

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

78 finding(s): 8 critical, 47 high, 16 medium, 7 low.

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D34 · Knowledge Freshness9.5 / 10Exemplary✓ Tool-verified

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

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

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

10 of 195 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 195 of the 517 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×10packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs:1

Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D35 · Change Coupling9.9 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: devtools.tsx↔Devtools.svelte 57%; useQueries.ts↔useQueries.ts 57%; inject-queries.ts↔useQueries.ts 55%

Boundary-crossing change coupling: devtools.tsx ↔ Devtools.svelte · ×3packages/solid-query-devtools/src/devtools.tsx:1

What to do

Resolve the 3 Boundary-crossing change coupling finding(s) in Change Coupling — start with devtools.tsx, useQueries.ts, inject-queries.ts. — One of this dimension's main actionable groups (3 issue-level).

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

Do you agree with this assessment?

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

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

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

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 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.

Do you agree with this assessment?

AC3 · Page structure6.8 / 10Adequate✓ Tool-verified

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

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

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

No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — integrations/lit-vite/index.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.

Do you agree with this assessment?

AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

Do you agree with this assessment?

AC7 · A11y enforcement6.0 / 10Adequate✓ Tool-verified

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

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

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

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

What to do

Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

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

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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

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

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.

Do you agree with this assessment?

C2 · Access Controls0.0 / 10Critical✓ Tool-verified

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

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

This repository serves requests — 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.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

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.

A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. — scripts/create-github-release.mjs:1

What to do

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

Do you agree with this assessment?

M1 · Documentation (README)7.5 / 10Strong✓ Tool-verified

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

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

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 31 of 117 project(s) that lack one — worth up to 0.5 pts.

Do you agree with this assessment?

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

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

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

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

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

M4 · Documentation accuracy8.0 / 10Strong✓ Tool-verified

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

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

docs/framework/react/guides/mutations.md names React 16, but the manifest declares `react` ^19.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/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.0.0.

Do you agree with this assessment?

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

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

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

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

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

No logging call was found in the 366 JavaScript/TypeScript production file(s) this check read across 41 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.
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.

Do you agree with this assessment?

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

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

What to do

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

Do you agree with this assessment?

P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

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

What to do

Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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.

Do you agree with this assessment?

R10 · Code Duplication9.0 / 10Exemplary✓ Tool-verified

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

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

integrations/react-next-15/ and integrations/react-next-16/ are near-verbatim copies of each other: 10 files are byte-identical under the same relative paths (~286 lines; the trees hold 12 and 12 files). That is one structural fact, not 10 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
113 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) — 50 of them are reported below, and 63 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 113 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 113 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 113 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
11 duplicated blocks under integrations/ have copies in at least two of the sibling directories react-next-14, react-next-15, react-next-16, react-vite, react-webpack-4, react-webpack-5 — 8 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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:23 · packages/preact-query/src/infiniteQueryOptions.ts:24 · packages/react-query/src/infiniteQueryOptions.ts:23 — 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:23
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:21 · packages/preact-query/src/queryOptions.ts:22 · packages/react-query/src/queryOptions.ts:21 — 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:21
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/query-core/src/queryClient.ts:368 · packages/vue-query/src/queryClient.ts:187 — the two spans are one implementation copied and then locally edited — 251 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:368
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/angular-query-experimental/src/mutation-options.ts:38 · packages/preact-query/src/mutationOptions.ts:32 · packages/react-query/src/mutationOptions.ts:31 · packages/solid-query/src/mutationOptions.ts:31 · +1 more site(s) not listed — the 5 copies are spread across 5 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/mutation-options.ts:38
packages/solid-query-persist-client/tsdown.config.ts:4 · packages/solid-query/tsdown.config.ts:4 — 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:4
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
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:225 · packages/angular-query-experimental/root.oxlint.config.ts:225 · packages/angular-query-persist-client/root.oxlint.config.ts:225 · packages/eslint-plugin-query/root.oxlint.config.ts:225 · +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:225
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
packages/svelte-query/src/infiniteQueryOptions.ts:41 · packages/vue-query/src/infiniteQueryOptions.ts:47 — 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/svelte-query/src/infiniteQueryOptions.ts:41
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
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/react-query-devtools/oxlint.config.ts:6 · packages/react-query-persist-client/oxlint.config.ts:6 · packages/react-query/oxlint.config.ts:6 — 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/react-query-devtools/oxlint.config.ts:6

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.

Do you agree with this assessment?

R11 · Import Boundaries9.3 / 10Exemplary✓ Tool-verified

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

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

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.

Do you agree with this assessment?

R2 · Cyclomatic Complexity9.4 / 10Exemplary✓ Tool-verified

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

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

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
ContentView has cyclomatic complexity 28 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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:690
fetch has cyclomatic complexity 22 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/query-core/src/query.ts:703
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
Explorer has cyclomatic complexity 20 and cognitive complexity 15; 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:284
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:416
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:624
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
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

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

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 3572 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 1093 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 1009 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-core/src/queryObserver.ts has 870 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/query-core/src/utils.ts has 668 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/vue-query/src/queryClient.ts has 668 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/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/query-devtools/src/Explorer.tsx 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/query-devtools/src/Explorer.tsx: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/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-core/src/mutation.ts has 511 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/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 448 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/query-persist-client-core/src/createPersister.ts has 437 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/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/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.2 / 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) — REDACTED:1, scripts/create-github-release.mjs:1, packages/react-query-next-experimental/src/HydrationStreamProvider.tsx: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) (~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 335 application, 164 tooling and 364 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 (335 application, 164 tooling, 364 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 (×30) — 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 (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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.

Do you agree with this assessment?

R8 · Dependency Hygiene7.5 / 10Strong✓ Tool-verified

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

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

Declared in 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-20/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.

Do you agree with this assessment?

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document3.0 / 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.

`updateNestedDataByPath` is exported and takes `oldData: unknown` from its caller, and it calls itself at line 235 (`updateNestedDataByPath`) with a piece of `oldData` (and at line 260, line 276) — 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:235
`deleteNestedDataByPath` is exported and takes `oldData: unknown` from its caller, and it calls itself at line 303 (`deleteNestedDataByPath`) with a piece of `oldData` (and at line 322, line 338) — 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:303
`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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

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

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

Only 0/10 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`resolveUsername` 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 })`. — scripts/create-github-release.mjs:12
`resolveAuthorForPR` 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 })`. — scripts/create-github-release.mjs:32
`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:14, 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.

Do you agree with this assessment?

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

`html.join('')` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/react-query-next-experimental/src/HydrationStreamProvider.tsx:158

What to do

Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

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.

Do you agree with this assessment?

X3 · Exception handling6.0 / 10Adequate✓ Tool-verified

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

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

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — scripts/create-github-release.mjs:241, scripts/create-github-release.mjs:268, packages/svelte-query/src/createBaseQuery.svelte.ts:108, …
`.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:1949, packages/lit-query/src/createMutationController.ts:190

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.

Do you agree with this assessment?

X5 · Nullable reference types9.3 / 10Exemplary✓ Tool-verified

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

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

170/172 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.5 `!` null assertions per 1k TypeScript source lines — 86 assertion(s) across the 57136 source line(s) of the 322 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 (23), REDACTED (21), packages/query-devtools/src/Explorer.tsx (6). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

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

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).

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC5 · ARIA correctness	4.1.2	Partial signal
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	67%	Adequate	Acceptable, with room to improve.
Architecture	97%	Exemplary	Solid.
Maturity	63%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	48%	Weak — gated by P2, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	18%	Critical — gated by D28, D29, D30, D36, C2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	76%	Strong	Solid.
Performance	100%	Exemplary	Strongest area.

Unscored — 1 check(s) recorded observations but carry no score

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

X10 Duplicated predicate — 19 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 — 53 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 did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — 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.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .cts, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.mjs,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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) — 13 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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage --coverage.reporter=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
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 applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — Not assessed: 352 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, 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. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.

Critical — 85 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×46

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 21 more in this group — see findings.md.

D28 · Secrets (history) · High secret · ×18

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×5

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D28 · Secrets (history) · REDACTED · ×4

REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Critical vulnerability · ×3

REDACTED
REDACTED
REDACTED

D35 · Change Coupling · Boundary-crossing change coupling · ×3

Boundary-crossing change coupling: devtools.tsx ↔ Devtools.svelte packages/solid-query-devtools/src/devtools.tsx:1 — `packages/solid-query-devtools/src/devtools.tsx` (context solid-query-devtools) and `packages/svelte-query-devtools/src/Devtools.svelte` (context svelte-query-devtools) sit in DIFFERENT parts of the tree yet change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `a5d5e004` docs(*-devtools): describe how the 'theme' prop interacts with the th…; `688f6e07` docs(*): describe 'shadowDOMTarget' as the shadow DOM the devtools st…; `868577d5` docs(devtools): align logo, panel, and option union descriptions acro… — run `git show` on any of them.
Boundary-crossing change coupling: useQueries.ts ↔ useQueries.ts packages/solid-query/src/useQueries.ts:1 — `packages/solid-query/src/useQueries.ts` (context solid-query) and `packages/vue-query/src/useQueries.ts` (context vue-query) sit in DIFFERENT parts of the tree yet change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `79d2384d` docs(*): fix 'homogenous', 'stoage', 'supressed', 'compoennts' spelli…; `f63ba16d` fix(types): prevent type errors and improve inference for dynamic que… (at that commit the file was still `packages/solid-query/src/createQueries.ts`); `6f08200c` refactor(*): improved type inference for useQueries with skipToken (#… (at that commit the file was still `packages/solid-query/src/createQueries.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: inject-queries.ts ↔ useQueries.ts packages/angular-query-experimental/src/inject-queries.ts:1 — `packages/angular-query-experimental/src/inject-queries.ts` (context angular-query-experimental) and `packages/vue-query/src/useQueries.ts` (context vue-query) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `79d2384d` docs(*): fix 'homogenous', 'stoage', 'supressed', 'compoennts' spelli…; `f63ba16d` fix(types): prevent type errors and improve inference for dynamic que…; `6f08200c` refactor(*): improved type inference for useQueries with skipToken (#… — run `git show` on any of them.

D13 · REDACTED Scanning · Leaked secret · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×1

REDACTED

Serious — 1320 finding(s)

D10 · Test Quality · No assertions · ×917

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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when passed to infiniteQuery 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when passed to infiniteQuery with select packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:81 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should tag the queryKey with the result type of the QueryFn packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:99 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should tag the queryKey even if no promise is returned 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should tag the queryKey with the result type of the QueryFn if select is used packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:123 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should return the proper type when passed to getQueryData packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:136 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should properly type when passed to setQueryData packages/vue-query/src/__tests__/infiniteQueryOptions.test-d.ts:153 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when used with useIsMutating packages/vue-query/src/__tests__/mutationOptions.test-d.ts:166 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when used with queryClient.isMutating packages/vue-query/src/__tests__/mutationOptions.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when used with useMutationState packages/vue-query/src/__tests__/mutationOptions.test-d.ts:202 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 892 more in this group — see findings.md.

R4 · Test Coverage · No test reaches this file · ×40

No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/create-github-release.mjs: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/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 scripts/generate-labeler-config.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/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 scripts/getTsdownConfig.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 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 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-20/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-vite/src/App.jsx: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.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 integrations/react-webpack-5/src/App.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.
+ 15 more in this group — see findings.md.

D3 · God Classes · FunctionTooLong · ×22

FunctionTooLong: Devtools.stylesFactory packages/query-devtools/src/Devtools.tsx:2728 — FunctionTooLong — stylesFactory runs 904 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 804 over it, 9.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: 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:690 — FunctionTooLong — ContentView runs 594 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 494 over it, 5.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Devtools.QueryDetails packages/query-devtools/src/Devtools.tsx:1865 — FunctionTooLong — QueryDetails runs 456 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 356 over it, 4.56× 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:284 — FunctionTooLong — Explorer runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.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.DraggablePanel packages/query-devtools/src/Devtools.tsx:416 — 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: createPersister.experimental_createQueryPersister packages/query-persist-client-core/src/createPersister.ts:137 — FunctionTooLong — experimental_createQueryPersister runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× 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.MutationDetails packages/query-devtools/src/Devtools.tsx:2412 — FunctionTooLong — MutationDetails runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× 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: 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: Devtools.Devtools packages/query-devtools/src/Devtools.tsx:119 — FunctionTooLong — Devtools runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: 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: Explorer.stylesFactory packages/query-devtools/src/Explorer.tsx:554 — FunctionTooLong — stylesFactory runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: useBaseQuery.useBaseQuery packages/vue-query/src/useBaseQuery.ts:73 — FunctionTooLong — useBaseQuery runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× 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: 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.
FunctionTooLong: retryer.createRetryer packages/query-core/src/retryer.ts:149 — FunctionTooLong — createRetryer runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× 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.

D17 · Explicit Debt · TodoComment · ×18

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:38 — // 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:115 — // 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:173 — // 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:219 — // 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:98 — // 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:156 — // 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:202 — // 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 · ×14

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

X2 · Cancellation propagation · Async function without AbortSignal · ×10

Async function without AbortSignal: resolveUsername scripts/create-github-release.mjs:12 — `resolveUsername` 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: resolveAuthorForPR scripts/create-github-release.mjs:32 — `resolveAuthorForPR` 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 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:14 — `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:14 — `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 })`.

D23 · Boundary Type-Coupling · Cross-context type Accessor (lit-query → solid-query) · ×9

Cross-context type Accessor (lit-query → solid-query) packages/solid-query/src/QueryClientProvider.tsx:47 — Accessor (context lit-query) is exposed in solid-query's public surface via QueryClientProvider.useQueryClientResolver — couples the contexts.
Cross-context type Accessor (lit-query → solid-query) packages/solid-query/src/useBaseQuery.ts:124 — Accessor (context lit-query) is exposed in solid-query's public surface via useBaseQuery.useBaseQuery — couples the contexts.
Cross-context type Accessor (lit-query → solid-query) packages/solid-query/src/useQuery.ts:237 — Accessor (context lit-query) is exposed in solid-query's public surface via useQuery.useQuery — couples the contexts.
Cross-context type Accessor (lit-query → solid-query) packages/solid-query/src/useInfiniteQuery.ts:201 — Accessor (context lit-query) is exposed in solid-query's public surface via useInfiniteQuery.useInfiniteQuery — couples the contexts.
Cross-context type Accessor (lit-query → solid-query) packages/solid-query/src/useMutation.ts:170 — Accessor (context lit-query) is exposed in solid-query's public surface via useMutation.useMutation — couples the contexts.
Cross-context type Accessor (lit-query → solid-query) packages/solid-query/src/useQueries.ts:272 — Accessor (context lit-query) is exposed in solid-query's public surface via useQueries.useQueries — couples the contexts.
Cross-context type Accessor (lit-query → solid-query) packages/solid-query/src/useIsFetching.ts:27 — Accessor (context lit-query) is exposed in solid-query's public surface via useIsFetching.useIsFetching — couples the contexts.
Cross-context type Accessor (lit-query → solid-query) packages/solid-query/src/useIsMutating.ts:26 — Accessor (context lit-query) is exposed in solid-query's public surface via useIsMutating.useIsMutating — couples the contexts.
Cross-context type Accessor (lit-query → solid-query) packages/solid-query/src/useMutationState.ts:127 — Accessor (context lit-query) is exposed in solid-query's public surface via useMutationState.useMutationState — couples the contexts.

D3 · God Classes · FileTooLong · ×9

FileTooLong: src/Devtools.tsx packages/query-devtools/src/Devtools.tsx — FileTooLong — 3083 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2583 over it, 6.17× 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: REDACTED REDACTED — FileTooLong — 757 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 257 over it, 1.51× 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 — 556 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 56 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/queryClient.ts packages/vue-query/src/queryClient.ts — FileTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: QueryClient (52-698). The bar is 500 significant lines; this is 36 over it, 1.07× 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 — 527 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: QueryClient (78-1170). The bar is 500 significant lines; this is 27 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/queryObserver.ts packages/query-core/src/queryObserver.ts — FileTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: QueryObserver (56-869). The bar is 500 significant lines; this is 21 over it, 1.04× 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 — 510 significant lines (blank, comment-only and punctuation-only lines excluded), about 66% of them inside a single declaration: Query (283-1017). The bar is 500 significant lines; this is 10 over it, 1.02× 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.

D15 · Churn × Complexity Hotspots · Hotspot · ×8

Hotspot: packages/query-core/src/queryObserver.ts packages/query-core/src/queryObserver.ts:589 — packages/query-core/src/queryObserver.ts changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in QueryObserver.createResult at line 589. 5 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 23:23:26 +09:00' --until='2026-10-26 23:23:26 +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:703 — packages/query-core/src/query.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in Query.fetch at line 703. 2 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 23:23:26 +09:00' --until='2026-10-26 23:23:26 +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/query-devtools/src/Devtools.tsx packages/query-devtools/src/Devtools.tsx:690 — packages/query-devtools/src/Devtools.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in Devtools.ContentView at line 690. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 23:23:26 +09:00' --until='2026-10-26 23:23:26 +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/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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 23:23:26 +09:00' --until='2026-10-26 23:23:26 +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/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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 23:23:26 +09:00' --until='2026-10-26 23:23:26 +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 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in retryer.createRetryer.run at line 223. 1 of those changes was a fix/bug commit, 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 23:23:26 +09:00' --until='2026-10-26 23:23:26 +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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 23:23:26 +09:00' --until='2026-10-26 23:23:26 +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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 23:23:26 +09:00' --until='2026-10-26 23:23:26 +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.

X3 · Exception handling · Swallowed exception (empty catch) · ×7

Swallowed exception (empty catch) scripts/create-github-release.mjs:241 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/create-github-release.mjs:268 — 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/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:1949 — `.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.

D23 · Boundary Type-Coupling · Cross-context type Accessor (lit-query → query-devtools) · ×6

Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/createCacheSubscriptionRegistry.ts:25 — Accessor (context lit-query) is exposed in query-devtools's public surface via createCacheSubscriptionRegistry.createCacheSubscriptionRegistry.register — couples the contexts.
Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/createCacheSubscriptionRegistry.ts:44 — Accessor (context lit-query) is exposed in query-devtools's public surface via createCacheSubscriptionRegistry.createCacheSubscriptionRegistry.notify — couples the contexts.
Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/contexts/types.ts:110 — Accessor (context lit-query) is exposed in query-devtools's public surface via DevtoolsState.selectedQueryHash — couples the contexts.
Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/contexts/types.ts:118 — Accessor (context lit-query) is exposed in query-devtools's public surface via DevtoolsState.selectedMutationId — couples the contexts.
Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/contexts/types.ts:126 — Accessor (context lit-query) is exposed in query-devtools's public surface via DevtoolsState.panelWidth — couples the contexts.
Cross-context type Accessor (lit-query → query-devtools) packages/query-devtools/src/contexts/types.ts:162 — Accessor (context lit-query) is exposed in query-devtools's public surface via DevtoolsOfflineState.offline — couples the contexts.

R7 · Dead Code · Dead file (~81 LoC) · ×6

Dead file (~81 LoC) packages/query-codemods/src/v5/is-loading/__testfixtures__/default-import.input.tsx — no import path from any entry point (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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

D23 · Boundary Type-Coupling · Cross-context type Accessor (lit-query → svelte-query) · ×5

Cross-context type Accessor (lit-query → svelte-query) packages/svelte-query/src/createBaseQuery.svelte.ts:20 — Accessor (context lit-query) is exposed in svelte-query's public surface via createBaseQuery.svelte.createBaseQuery — couples the contexts.
Cross-context type Accessor (lit-query → svelte-query) packages/svelte-query/src/createInfiniteQuery.ts:199 — Accessor (context lit-query) is exposed in svelte-query's public surface via createInfiniteQuery.createInfiniteQuery — couples the contexts.
Cross-context type Accessor (lit-query → svelte-query) packages/svelte-query/src/createMutation.svelte.ts:165 — Accessor (context lit-query) is exposed in svelte-query's public surface via createMutation.svelte.createMutation — couples the contexts.
Cross-context type Accessor (lit-query → svelte-query) packages/svelte-query/src/createQueries.svelte.ts:259 — Accessor (context lit-query) is exposed in svelte-query's public surface via createQueries.svelte.createQueries — couples the contexts.
Cross-context type Accessor (lit-query → svelte-query) packages/svelte-query/src/createQuery.ts:259 — Accessor (context lit-query) is exposed in svelte-query's public surface via createQuery.createQuery — couples the contexts.

R11 · Import Boundaries · Boundary violation [package · ×5

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.

D12 · Dependency Hygiene · Deprecated · ×4

Deprecated: eslint REDACTED:64 — eslint 9.39.4, 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.4, 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:72 — 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:73 — 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.

D23 · Boundary Type-Coupling · Cross-context type Updater (query-core → vue-query) · ×4

Cross-context type Updater (query-core → vue-query) packages/vue-query/src/queryClient.ts:145 — Updater (context query-core) is exposed in vue-query's public surface via QueryClient.setQueryData — couples the contexts.
Cross-context type Updater (query-core → vue-query) packages/vue-query/src/queryClient.ts:158 — Updater (context query-core) is exposed in vue-query's public surface via QueryClient.setQueryData — couples the contexts.
Cross-context type Updater (query-core → vue-query) packages/vue-query/src/queryClient.ts:163 — Updater (context query-core) is exposed in vue-query's public surface via QueryClient.setQueryData — couples the contexts.
Cross-context type Updater (query-core → vue-query) packages/vue-query/src/queryClient.ts:175 — Updater (context query-core) is exposed in vue-query's public surface via QueryClient.setQueriesData — couples the contexts.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

D12 · Dependency Hygiene · One package at two majors across the workspace · ×3

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: 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.

D23 · Boundary Type-Coupling · Cross-context type QueryObserverResult (query-core → preact-query) · ×3

Cross-context type QueryObserverResult (query-core → preact-query) packages/preact-query/src/errorBoundaryUtils.ts:76 — QueryObserverResult (context query-core) is exposed in preact-query's public surface via errorBoundaryUtils.getHasError — couples the contexts.
Cross-context type QueryObserverResult (query-core → preact-query) packages/preact-query/src/suspense.ts:69 — QueryObserverResult (context query-core) is exposed in preact-query's public surface via suspense.shouldSuspend — couples the contexts.
Cross-context type QueryObserverResult (query-core → preact-query) packages/preact-query/src/useBaseQuery.ts:39 — QueryObserverResult (context query-core) is exposed in preact-query's public surface via useBaseQuery.useBaseQuery — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type QueryObserverResult (query-core → react-query) · ×3

Cross-context type QueryObserverResult (query-core → react-query) packages/react-query/src/errorBoundaryUtils.ts:76 — QueryObserverResult (context query-core) is exposed in react-query's public surface via errorBoundaryUtils.getHasError — couples the contexts.
Cross-context type QueryObserverResult (query-core → react-query) packages/react-query/src/suspense.ts:68 — QueryObserverResult (context query-core) is exposed in react-query's public surface via suspense.shouldSuspend — couples the contexts.
Cross-context type QueryObserverResult (query-core → react-query) packages/react-query/src/useBaseQuery.ts:39 — QueryObserverResult (context query-core) is exposed in react-query's public surface via useBaseQuery.useBaseQuery — couples the contexts.

D3 · God Classes · MethodTooLong · ×3

MethodTooLong: Query.fetch packages/query-core/src/query.ts:703 — MethodTooLong — fetch runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: QueryObserver.createResult packages/query-core/src/queryObserver.ts:589 — MethodTooLong — createResult runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Mutation.execute packages/query-core/src/mutation.ts:301 — MethodTooLong — execute runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× 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.

D3 · God Classes · ClassTooLong · ×3

ClassTooLong: QueryClient packages/vue-query/src/queryClient.ts:52 — ClassTooLong — 500 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 100 over it, 1.25× 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 — 476 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 76 over it, 1.19× 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 — 441 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 41 over it, 1.10× 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.

D5 · Coupling · Off the main sequence · ×3

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.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: @tanstack/vue-query — @tanstack/vue-query: abstractness 0.05, instability 0.25, distance 0.70 — 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 · ×3

Recursive walk over a caller-supplied document has no depth cap packages/query-devtools/src/utils.tsx:235 — `updateNestedDataByPath` is exported and takes `oldData: unknown` from its caller, and it calls itself at line 235 (`updateNestedDataByPath`) with a piece of `oldData` (and at line 260, line 276) — 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:303 — `deleteNestedDataByPath` is exported and takes `oldData: unknown` from its caller, and it calls itself at line 303 (`deleteNestedDataByPath`) with a piece of `oldData` (and at line 322, line 338) — 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.

D2 · Cognitive Complexity · HydrationBoundary.HydrationBoundary (cognitive 21) · ×2

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.

D23 · Boundary Type-Coupling · Cross-context type Theme (query-devtools → angular-query-experimental) · ×2

Cross-context type Theme (query-devtools → angular-query-experimental) packages/angular-query-experimental/src/devtools-panel/types.ts:57 — Theme (context query-devtools) is exposed in angular-query-experimental's public surface via DevtoolsPanelOptions.theme — couples the contexts.
Cross-context type Theme (query-devtools → angular-query-experimental) packages/angular-query-experimental/src/devtools/types.ts:85 — Theme (context query-devtools) is exposed in angular-query-experimental's public surface via DevtoolsOptions.theme — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type Theme (query-devtools → preact-query-devtools) · ×2

Cross-context type Theme (query-devtools → preact-query-devtools) packages/preact-query-devtools/src/PreactQueryDevtools.tsx:63 — Theme (context query-devtools) is exposed in preact-query-devtools's public surface via DevtoolsOptions.theme — couples the contexts.
Cross-context type Theme (query-devtools → preact-query-devtools) packages/preact-query-devtools/src/PreactQueryDevtoolsPanel.tsx:49 — Theme (context query-devtools) is exposed in preact-query-devtools's public surface via DevtoolsPanelOptions.theme — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type Theme (query-devtools → react-query-devtools) · ×2

Cross-context type Theme (query-devtools → react-query-devtools) packages/react-query-devtools/src/ReactQueryDevtools.tsx:60 — Theme (context query-devtools) is exposed in react-query-devtools's public surface via DevtoolsOptions.theme — couples the contexts.
Cross-context type Theme (query-devtools → react-query-devtools) packages/react-query-devtools/src/ReactQueryDevtoolsPanel.tsx:51 — Theme (context query-devtools) is exposed in react-query-devtools's public surface via DevtoolsPanelOptions.theme — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type Theme (query-devtools → vue-query-devtools) · ×2

Cross-context type Theme (query-devtools → vue-query-devtools) packages/vue-query-devtools/src/types.ts:55 — Theme (context query-devtools) is exposed in vue-query-devtools's public surface via DevtoolsOptions.theme — couples the contexts.
Cross-context type Theme (query-devtools → vue-query-devtools) packages/vue-query-devtools/src/types.ts:101 — Theme (context query-devtools) is exposed in vue-query-devtools's public surface via DevtoolsPanelOptions.theme — couples the contexts.

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D3 · God Classes · TooManyMethods · ×2

TooManyMethods: QueryClient packages/vue-query/src/queryClient.ts:52 — 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.

D30 · Dependency Vulnerabilities · Medium vulnerability · ×2

REDACTED
REDACTED

R10 · Code Duplication · Duplicated block (33 lines × 2 locations) · ×2

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.

R2 · Cyclomatic Complexity · Complex function replaceEqualDeep (cyclomatic 22, cognitive 29) · ×2

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.

R2 · Cyclomatic Complexity · Complex function partialMatchKey (cyclomatic 14, cognitive 23) · ×2

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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 20) · ×2

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.

R7 · Dead Code · Dead file (~284 LoC) · ×2

Dead file (~284 LoC) packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/default.input.tsx — no import path from any entry point (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~271 LoC) · ×2

Dead file (~271 LoC) packages/query-codemods/src/v5/keep-previous-data/keep-previous-data.cjs — no import path from any entry point (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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

R7 · Dead Code · Dead file (~96 LoC) · ×2

Dead file (~96 LoC) packages/query-codemods/src/v4/__testfixtures__/default-import.output.tsx — no import path from any entry point (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~58 LoC) · ×2

Dead file (~58 LoC) knip.ts — no import path from any entry point (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~55 LoC) · ×2

Dead file (~55 LoC) packages/query-codemods/src/v5/remove-overloads/__testfixtures__/bug-reports.input.tsx — no import path from any entry point (335 application, 164 tooling, 364 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 (335 application, 164 tooling, 364 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

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

C2 · Access Controls · No authorization · ×1

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.

D1 · Cyclomatic Complexity · Devtools.DraggablePanel (cyclomatic 51) · ×1

Devtools.DraggablePanel (cyclomatic 51) packages/query-devtools/src/Devtools.tsx:416 — 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. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/query-devtools/src/Devtools.tsx holds 4 of the 23 methods over the threshold — including the worst — and 86 of the 225 points over it (38%), 3.6× the next-largest file (packages/query-devtools/src/Explorer.tsx at 24). 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.

D1 · Cyclomatic Complexity · Devtools.ContentView (cyclomatic 50) · ×1

Devtools.ContentView (cyclomatic 50) packages/query-devtools/src/Devtools.tsx:690 — Devtools.ContentView has cyclomatic complexity 50 (threshold 15). Of this number, 28 points are the body's own statements and 22 belong to 14 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. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/query-devtools/src/Devtools.tsx holds 4 of the 23 methods over the threshold — including the worst — and 86 of the 225 points over it (38%), 3.6× the next-largest file (packages/query-devtools/src/Explorer.tsx at 24). 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.

D1 · Cyclomatic Complexity · Explorer.Explorer (cyclomatic 39) · ×1

Explorer.Explorer (cyclomatic 39) packages/query-devtools/src/Explorer.tsx:284 — Explorer.Explorer has cyclomatic complexity 39 (threshold 15). Of this number, 19 points are the body's own statements and 20 belong to 6 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · useBaseQuery.useBaseQuery (cyclomatic 34) · ×1

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.

D1 · Cyclomatic Complexity · generate-docs.addReferenceDetails (cyclomatic 33) · ×1

generate-docs.addReferenceDetails (cyclomatic 33) REDACTED:712 — generate-docs.addReferenceDetails has cyclomatic complexity 33 (threshold 15). Of this number, 26 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · QueryObserver.createResult (cyclomatic 29) · ×1

QueryObserver.createResult (cyclomatic 29) packages/query-core/src/queryObserver.ts:589 — QueryObserver.createResult has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Query.fetch (cyclomatic 25) · ×1

Query.fetch (cyclomatic 25) packages/query-core/src/query.ts:703 — Query.fetch has cyclomatic complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Devtools.QueryDetails (cyclomatic 24) · ×1

Devtools.QueryDetails (cyclomatic 24) packages/query-devtools/src/Devtools.tsx:1865 — 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 2190, a function literal at line 1872, …). 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 cyclomatic complexity CONCENTRATES: packages/query-devtools/src/Devtools.tsx holds 4 of the 23 methods over the threshold — including the worst — and 86 of the 225 points over it (38%), 3.6× the next-largest file (packages/query-devtools/src/Explorer.tsx at 24). 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.

D1 · Cyclomatic Complexity · utils.replaceEqualDeep (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · query-fn-aware-usage-transformer.transformQueryFnAwareUsages (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · hydration.hydrate (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · Devtools.Devtools (cyclomatic 21) · ×1

Devtools.Devtools (cyclomatic 21) packages/query-devtools/src/Devtools.tsx:119 — 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 150, 133, 141, …). 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. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/query-devtools/src/Devtools.tsx holds 4 of the 23 methods over the threshold — including the worst — and 86 of the 225 points over it (38%), 3.6× the next-largest file (packages/query-devtools/src/Explorer.tsx at 24). 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.

D1 · Cyclomatic Complexity · exports (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · PiPContext.PiPProvider (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · index.broadcastQueryClient (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · useBaseQuery.useBaseQuery (cyclomatic 19) · ×1

useBaseQuery.useBaseQuery (cyclomatic 19) packages/vue-query/src/useBaseQuery.ts:73 — useBaseQuery.useBaseQuery has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 104, 218, 178, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · exports (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · key-replacer.default (cyclomatic 18) · ×1

key-replacer.default (cyclomatic 18) packages/query-codemods/src/v4/utils/replacers/key-replacer.cjs:8 — key-replacer.default has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 5 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.

D1 · Cyclomatic Complexity · containers.svelte.createRawRef (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · infiniteQueryBehavior.infiniteQueryBehavior.onFetch (cyclomatic 17) · ×1

infiniteQueryBehavior.infiniteQueryBehavior.onFetch (cyclomatic 17) packages/query-core/src/infiniteQueryBehavior.ts:28 — 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.

D1 · Cyclomatic Complexity · QueryObserver.setOptions (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · filter-aware-usage-transformer.transformFilterAwareUsages · ×1

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.

D1 · Cyclomatic Complexity · utils.matchQuery (cyclomatic 16) · ×1

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.

D15 · Churn × Complexity Hotspots · Repeated repair · ×1

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), 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 23:23:26 +09:00' --until='2026-10-26 23:23:26 +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.

D17 · Explicit Debt · HackComment · ×1

HackComment packages/vue-query/src/vueQueryPlugin.ts:128 — // 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.

D2 · Cognitive Complexity · Devtools.DraggablePanel (cognitive 73) · ×1

Devtools.DraggablePanel (cognitive 73) packages/query-devtools/src/Devtools.tsx:416 — 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.

D2 · Cognitive Complexity · generate-docs.addReferenceDetails (cognitive 71) · ×1

generate-docs.addReferenceDetails (cognitive 71) REDACTED:712 — generate-docs.addReferenceDetails has cognitive complexity 71 (threshold 15). Drivers by points: ternaries 18 (45 pts), if/else 5 (14 pts), loops 4 (8 pts), boolean chains 4 (nesting depth added 40). Of this number, 63 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Devtools.ContentView (cognitive 48) · ×1

Devtools.ContentView (cognitive 48) packages/query-devtools/src/Devtools.tsx:690 — Devtools.ContentView has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 19 (21 pts), boolean chains 18, if/else 9 (nesting depth added 2). Of this number, 21 points are the body's own statements and 27 belong to 14 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.

D2 · Cognitive Complexity · QueryObserver.createResult (cognitive 33) · ×1

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.

D2 · Cognitive Complexity · Query.fetch (cognitive 33) · ×1

Query.fetch (cognitive 33) packages/query-core/src/query.ts:703 — Query.fetch has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 4, error handling 1, ternaries 1 (nesting depth added 10). Of this number, 32 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · filter-aware-usage-transformer.transformFilterAwareUsages · ×1

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.

D2 · Cognitive Complexity · useBaseQuery.useBaseQuery (cognitive 32) · ×1

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.

D2 · Cognitive Complexity · createPersister.experimental_createQueryPersister.restoreQueries (cognitive 31) · ×1

createPersister.experimental_createQueryPersister.restoreQueries (cognitive 31) packages/query-persist-client-core/src/createPersister.ts:363 — createPersister.experimental_createQueryPersister.restoreQueries has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (25 pts), error handling 1 (4 pts), loops 1 (2 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · Explorer.Explorer (cognitive 30) · ×1

Explorer.Explorer (cognitive 30) packages/query-devtools/src/Explorer.tsx:284 — Explorer.Explorer has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 14, if/else 7 (8 pts), ternaries 8 (nesting depth added 1). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 300, 331, 289, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · transformUsages (cognitive 28) · ×1

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.

D2 · Cognitive Complexity · Devtools.QueryDetails (cognitive 26) · ×1

Devtools.QueryDetails (cognitive 26) packages/query-devtools/src/Devtools.tsx:1865 — 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 2190, restoreQueryAfterLoadingOrError, a function literal at line 2240, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · createPersister.experimental_createQueryPersister.removeQueries (cognitive 25) · ×1

createPersister.experimental_createQueryPersister.removeQueries (cognitive 25) packages/query-persist-client-core/src/createPersister.ts:419 — createPersister.experimental_createQueryPersister.removeQueries has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (19 pts), error handling 1 (4 pts), loops 1 (2 pts) (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · utils.replaceEqualDeep (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · PiPContext.PiPProvider (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · useBaseQuery.useBaseQuery (cognitive 24) · ×1

useBaseQuery.useBaseQuery (cognitive 24) packages/vue-query/src/useBaseQuery.ts:73 — useBaseQuery.useBaseQuery has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 2, ternaries 2, loops 1 (nesting depth added 6). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 178, 104, 189, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · exports (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · key-replacer.default (cognitive 23) · ×1

key-replacer.default (cognitive 23) packages/query-codemods/src/v4/utils/replacers/key-replacer.cjs:8 — key-replacer.default has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 2, error handling 1, ternaries 1 (nesting depth added 6). None of this is in the body itself: all 23 points belong to 5 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.

D2 · Cognitive Complexity · utils.partialMatchKey (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · Devtools.Devtools (cognitive 22) · ×1

Devtools.Devtools (cognitive 22) packages/query-devtools/src/Devtools.tsx:119 — 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.

D2 · Cognitive Complexity · utils.matchQuery (cognitive 20) · ×1

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.

D2 · Cognitive Complexity · createPersister.experimental_createQueryPersister.retrieveQuery (cognitive 19) · ×1

createPersister.experimental_createQueryPersister.retrieveQuery (cognitive 19) packages/query-persist-client-core/src/createPersister.ts:181 — createPersister.experimental_createQueryPersister.retrieveQuery has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 2 (5 pts) (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · exports (cognitive 19) · ×1

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.

D2 · Cognitive Complexity · infiniteQueryBehavior.infiniteQueryBehavior.onFetch · ×1

infiniteQueryBehavior.infiniteQueryBehavior.onFetch::fetchFn (cognitive 18) packages/query-core/src/infiniteQueryBehavior.ts:36 — 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.

D2 · Cognitive Complexity · transformUsages (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · MutationObserver.#notify (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · hydration.hydrate (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · containers.svelte.createRawRef (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · generate-docs.declaredTypeLabel (cognitive 17) · ×1

generate-docs.declaredTypeLabel (cognitive 17) REDACTED:393 — generate-docs.declaredTypeLabel has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (7 pts), boolean chains 5, if/else 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · query-fn-aware-usage-transformer.transformQueryFnAwareUsages · ×1

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.

D2 · Cognitive Complexity · Mutation.execute (cognitive 16) · ×1

Mutation.execute (cognitive 16) packages/query-core/src/mutation.ts:301 — Mutation.execute has cognitive complexity 16 (threshold 15). Drivers by points: error handling 5 (9 pts), if/else 5 (7 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MutationCache.remove (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · streamedQuery.streamedQuery (cognitive 16) · ×1

streamedQuery.streamedQuery (cognitive 16) packages/query-core/src/streamedQuery.ts:70 — streamedQuery.streamedQuery has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (nesting depth added 4). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 84, 126). 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.

D23 · Boundary Type-Coupling · Cross-context type DevtoolsButtonPosition (query-devtools → angular-query-experimental) · ×1

Cross-context type DevtoolsButtonPosition (query-devtools → angular-query-experimental) packages/angular-query-experimental/src/devtools/types.ts:52 — DevtoolsButtonPosition (context query-devtools) is exposed in angular-query-experimental's public surface via DevtoolsOptions.buttonPosition — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type DevtoolsPosition (query-devtools → angular-query-experimental) · ×1

Cross-context type DevtoolsPosition (query-devtools → angular-query-experimental) packages/angular-query-experimental/src/devtools/types.ts:58 — DevtoolsPosition (context query-devtools) is exposed in angular-query-experimental's public surface via DevtoolsOptions.position — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type DevtoolsButtonPosition (query-devtools → preact-query-devtools) · ×1

Cross-context type DevtoolsButtonPosition (query-devtools → preact-query-devtools) packages/preact-query-devtools/src/PreactQueryDevtools.tsx:27 — DevtoolsButtonPosition (context query-devtools) is exposed in preact-query-devtools's public surface via DevtoolsOptions.buttonPosition — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type DevtoolsPosition (query-devtools → preact-query-devtools) · ×1

Cross-context type DevtoolsPosition (query-devtools → preact-query-devtools) packages/preact-query-devtools/src/PreactQueryDevtools.tsx:33 — DevtoolsPosition (context query-devtools) is exposed in preact-query-devtools's public surface via DevtoolsOptions.position — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type ThrowOnError (query-core → preact-query) · ×1

Cross-context type ThrowOnError (query-core → preact-query) packages/preact-query/src/errorBoundaryUtils.ts:76 — ThrowOnError (context query-core) is exposed in preact-query's public surface via errorBoundaryUtils.getHasError — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type QueryCacheNotifyEvent (query-core → query-devtools) · ×1

Cross-context type QueryCacheNotifyEvent (query-core → query-devtools) packages/query-devtools/src/contexts/types.ts:141 — QueryCacheNotifyEvent (context query-core) is exposed in query-devtools's public surface via DevtoolsSubscriptions.queryCacheSubscriptions — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type MutationCacheNotifyEvent (query-core → query-devtools) · ×1

Cross-context type MutationCacheNotifyEvent (query-core → query-devtools) packages/query-devtools/src/contexts/types.ts:147 — MutationCacheNotifyEvent (context query-core) is exposed in query-devtools's public surface via DevtoolsSubscriptions.mutationCacheSubscriptions — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type DevtoolsButtonPosition (query-devtools → react-query-devtools) · ×1

Cross-context type DevtoolsButtonPosition (query-devtools → react-query-devtools) packages/react-query-devtools/src/ReactQueryDevtools.tsx:27 — DevtoolsButtonPosition (context query-devtools) is exposed in react-query-devtools's public surface via DevtoolsOptions.buttonPosition — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type DevtoolsPosition (query-devtools → react-query-devtools) · ×1

Cross-context type DevtoolsPosition (query-devtools → react-query-devtools) packages/react-query-devtools/src/ReactQueryDevtools.tsx:33 — DevtoolsPosition (context query-devtools) is exposed in react-query-devtools's public surface via DevtoolsOptions.position — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type ThrowOnError (query-core → react-query) · ×1

Cross-context type ThrowOnError (query-core → react-query) packages/react-query/src/errorBoundaryUtils.ts:76 — ThrowOnError (context query-core) is exposed in react-query's public surface via errorBoundaryUtils.getHasError — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type Theme (query-devtools → solid-query-devtools) · ×1

Cross-context type Theme (query-devtools → solid-query-devtools) packages/solid-query-devtools/src/devtoolsPanel.tsx:51 — Theme (context query-devtools) is exposed in solid-query-devtools's public surface via DevtoolsPanelOptions.theme — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type DevtoolsButtonPosition (query-devtools → vue-query-devtools) · ×1

Cross-context type DevtoolsButtonPosition (query-devtools → vue-query-devtools) packages/vue-query-devtools/src/types.ts:22 — DevtoolsButtonPosition (context query-devtools) is exposed in vue-query-devtools's public surface via DevtoolsOptions.buttonPosition — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type DevtoolsPosition (query-devtools → vue-query-devtools) · ×1

Cross-context type DevtoolsPosition (query-devtools → vue-query-devtools) packages/vue-query-devtools/src/types.ts:28 — DevtoolsPosition (context query-devtools) is exposed in vue-query-devtools's public surface via DevtoolsOptions.position — couples the contexts.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

P2 · Observability · No structured logging · ×1

No structured logging — No logging call was found in the 366 JavaScript/TypeScript production file(s) this check read across 41 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.

R10 · Code Duplication · Forked directory tree (10 identical files, ~286 lines × 2 trees) · ×1

Forked directory tree (10 identical files, ~286 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: 10 files are byte-identical under the same relative paths (~286 lines; the trees hold 12 and 12 files). That is one structural fact, not 10 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.

R10 · Code Duplication · Duplication concentrated across 25 sibling directories (113 clone groups) · ×1

Duplication concentrated across 25 sibling directories (113 clone groups) packages/preact-query/src/useQueries.ts:6 — 113 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) — 50 of them are reported below, and 63 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 113 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 113 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 113 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 6 sibling directories (11 clone groups) · ×1

Duplication concentrated across 6 sibling directories (11 clone groups) integrations/react-next-15/app/make-query-client.ts:21 — 11 duplicated blocks under integrations/ have copies in at least two of the sibling directories react-next-14, react-next-15, react-next-16, react-vite, react-webpack-4, react-webpack-5 — 8 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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.

R10 · Code Duplication · Wholesale file copy (181 identical lines × 2 files) · ×1

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.

R10 · Code Duplication · Wholesale file copy (143 identical lines × 2 files) · ×1

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.

R10 · Code Duplication · Wholesale file copy (129 identical lines × 2 files) · ×1

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.

R10 · Code Duplication · Duplicated block (98 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Wholesale file copy (96 identical lines × 2 files) · ×1

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.

R10 · Code Duplication · Duplicated block (91 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (75 lines × 3 locations) · ×1

Duplicated block (75 lines × 3 locations) packages/angular-query-experimental/src/infinite-query-options.ts:23 — packages/angular-query-experimental/src/infinite-query-options.ts:23 · packages/preact-query/src/infiniteQueryOptions.ts:24 · packages/react-query/src/infiniteQueryOptions.ts:23 — 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 (66 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Wholesale file copy (63 identical lines × 2 files) · ×1

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.

R10 · Code Duplication · Wholesale file copy (59 identical lines × 2 files) · ×1

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.

R10 · Code Duplication · Wholesale file copy (57 identical lines × 2 files) · ×1

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.

R10 · Code Duplication · Duplicated block (57 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (53 lines × 3 locations) · ×1

Duplicated block (53 lines × 3 locations) packages/angular-query-experimental/src/query-options.ts:21 — packages/angular-query-experimental/src/query-options.ts:21 · packages/preact-query/src/queryOptions.ts:22 · packages/react-query/src/queryOptions.ts:21 — 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.

R10 · Code Duplication · Wholesale file copy (53 identical lines × 2 files) · ×1

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.

R10 · Code Duplication · Wholesale file copy (51 identical lines × 2 files) · ×1

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 (50 matched lines × 2 locations) · ×1

Duplicated block with local edits (50 matched lines × 2 locations) packages/query-core/src/queryClient.ts:368 — packages/query-core/src/queryClient.ts:368 · packages/vue-query/src/queryClient.ts:187 — the two spans are one implementation copied and then locally edited — 251 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.

R10 · Code Duplication · Duplicated block (42 lines × 3 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (39 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (38 lines × 5 locations) · ×1

Duplicated block (38 lines × 5 locations) packages/angular-query-experimental/src/mutation-options.ts:38 — packages/angular-query-experimental/src/mutation-options.ts:38 · packages/preact-query/src/mutationOptions.ts:32 · packages/react-query/src/mutationOptions.ts:31 · packages/solid-query/src/mutationOptions.ts:31 · +1 more site(s) not listed — the 5 copies are spread across 5 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 (37 lines × 2 locations) · ×1

Duplicated block (37 lines × 2 locations) packages/solid-query-persist-client/tsdown.config.ts:4 — packages/solid-query-persist-client/tsdown.config.ts:4 · packages/solid-query/tsdown.config.ts:4 — 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 (36 lines × 3 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (32 lines × 27 locations) · ×1

Duplicated block (32 lines × 27 locations) oxlint.config.ts:225 — oxlint.config.ts:225 · packages/angular-query-experimental/root.oxlint.config.ts:225 · packages/angular-query-persist-client/root.oxlint.config.ts:225 · packages/eslint-plugin-query/root.oxlint.config.ts:225 · +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.

R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×1

Duplicated block (32 lines × 2 locations) packages/svelte-query/src/infiniteQueryOptions.ts:41 — packages/svelte-query/src/infiniteQueryOptions.ts:41 · packages/vue-query/src/infiniteQueryOptions.ts:47 — 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.

R10 · Code Duplication · Duplicated block (31 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×1

Duplicated block (29 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.

R10 · Code Duplication · Duplicated block (29 lines × 3 locations) · ×1

Duplicated block (29 lines × 3 locations) packages/react-query-devtools/oxlint.config.ts:6 — packages/react-query-devtools/oxlint.config.ts:6 · packages/react-query-persist-client/oxlint.config.ts:6 · packages/react-query/oxlint.config.ts:6 — 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.

R2 · Cyclomatic Complexity · Complex function addReferenceDetails (cyclomatic 28, cognitive 89) · ×1

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 ContentView (cyclomatic 28, cognitive 27) · ×1

Complex function ContentView (cyclomatic 28, cognitive 27) packages/query-devtools/src/Devtools.tsx:690 — ContentView has cyclomatic complexity 28 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function fetch (cyclomatic 22, cognitive 31) · ×1

Complex function fetch (cyclomatic 22, cognitive 31) packages/query-core/src/query.ts:703 — fetch has cyclomatic complexity 22 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 22, cognitive 20) · ×1

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.

R2 · Cyclomatic Complexity · Complex function Explorer (cyclomatic 20, cognitive 15) · ×1

Complex function Explorer (cyclomatic 20, cognitive 15) packages/query-devtools/src/Explorer.tsx:284 — Explorer has cyclomatic complexity 20 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function CallExpression (cyclomatic 18, cognitive 24) · ×1

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.

R2 · Cyclomatic Complexity · Complex function DraggablePanel (cyclomatic 18, cognitive 17) · ×1

Complex function DraggablePanel (cyclomatic 18, cognitive 17) packages/query-devtools/src/Devtools.tsx:416 — 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.

R2 · Cyclomatic Complexity · Complex function visit (cyclomatic 17, cognitive 13) · ×1

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.

R2 · Cyclomatic Complexity · Complex function replacer (cyclomatic 16, cognitive 32) · ×1

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.

R2 · Cyclomatic Complexity · Complex function matchQuery (cyclomatic 16, cognitive 20) · ×1

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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 15, cognitive 29) · ×1

Complex function (anonymous) (cyclomatic 15, cognitive 29) packages/query-devtools/src/Devtools.tsx:624 — (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.

R2 · Cyclomatic Complexity · Complex function declaredTypeLabel (cyclomatic 15, cognitive 16) · ×1

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.

R2 · Cyclomatic Complexity · Complex function CallExpression (cyclomatic 14, cognitive 17) · ×1

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.

R2 · Cyclomatic Complexity · Complex function isRelevantReference (cyclomatic 14, cognitive 16) · ×1

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.

R3 · Large Files · packages/query-devtools/src/Devtools.tsx · ×1

packages/query-devtools/src/Devtools.tsx: 3572 lines of code packages/query-devtools/src/Devtools.tsx:1 — packages/query-devtools/src/Devtools.tsx has 3572 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: 1093 lines of code packages/query-core/src/queryClient.ts:1 — packages/query-core/src/queryClient.ts has 1093 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · REDACTED · ×1

REDACTED: 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: 1009 lines of code packages/query-core/src/query.ts:1 — packages/query-core/src/query.ts has 1009 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: 870 lines of code packages/query-core/src/queryObserver.ts:1 — packages/query-core/src/queryObserver.ts has 870 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: 668 lines of code packages/query-core/src/utils.ts:1 — packages/query-core/src/utils.ts has 668 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: 668 lines of code packages/vue-query/src/queryClient.ts:1 — packages/vue-query/src/queryClient.ts has 668 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/query-devtools/src/Explorer.tsx · ×1

packages/query-devtools/src/Explorer.tsx: 654 lines of code packages/query-devtools/src/Explorer.tsx:1 — packages/query-devtools/src/Explorer.tsx 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/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-core/src/mutation.ts · ×1

packages/query-core/src/mutation.ts: 511 lines of code packages/query-core/src/mutation.ts:1 — packages/query-core/src/mutation.ts has 511 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: 448 lines of code packages/vue-query/src/useQueries.ts:1 — packages/vue-query/src/useQueries.ts has 448 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: 437 lines of code packages/query-persist-client-core/src/createPersister.ts:1 — packages/query-persist-client-core/src/createPersister.ts has 437 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/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.

R7 · Dead Code · Dead file (~501 LoC) · ×1

Dead file (~501 LoC) packages/query-codemods/src/v5/remove-overloads/__testfixtures__/default-import.output.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~290 LoC) · ×1

Dead file (~290 LoC) packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.output.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~289 LoC) · ×1

Dead file (~289 LoC) packages/query-codemods/src/v5/keep-previous-data/__testfixtures__/named.input.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~244 LoC) · ×1

Dead file (~244 LoC) packages/query-codemods/src/v5/is-loading/is-loading.cjs — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~210 LoC) · ×1

Dead file (~210 LoC) packages/query-codemods/src/v5/remove-overloads/__testfixtures__/default-import.input.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~208 LoC) · ×1

Dead file (~208 LoC) packages/query-codemods/src/utils/index.cjs — no import path from any entry point (335 application, 164 tooling, 364 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

R7 · Dead Code · Dead file (~185 LoC) · ×1

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 (335 application, 164 tooling, 364 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

R7 · Dead Code · Dead file (~181 LoC) · ×1

Dead file (~181 LoC) packages/query-codemods/src/v4/key-transformation.cjs — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~175 LoC) · ×1

Dead file (~175 LoC) packages/query-codemods/src/v4/__testfixtures__/parameter-is-object-expression.output.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~164 LoC) · ×1

Dead file (~164 LoC) packages/query-codemods/src/v4/utils/replacers/key-replacer.cjs — no import path from any entry point (335 application, 164 tooling, 364 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

R7 · Dead Code · Dead file (~127 LoC) · ×1

Dead file (~127 LoC) packages/query-codemods/src/v4/__testfixtures__/parameter-is-object-expression.input.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~124 LoC) · ×1

Dead file (~124 LoC) packages/query-codemods/src/utils/transformers/query-cache-transformer.cjs — no import path from any entry point (335 application, 164 tooling, 364 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

R7 · Dead Code · Dead file (~123 LoC) · ×1

Dead file (~123 LoC) packages/query-codemods/src/v5/remove-overloads/utils/index.cjs — no import path from any entry point (335 application, 164 tooling, 364 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

R7 · Dead Code · Dead file (~103 LoC) · ×1

Dead file (~103 LoC) scripts/generate-labeler-config.ts — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~98 LoC) · ×1

Dead file (~98 LoC) packages/query-codemods/src/v4/__testfixtures__/named-import.output.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~94 LoC) · ×1

Dead file (~94 LoC) packages/query-codemods/src/v4/__testfixtures__/default-import.input.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~88 LoC) · ×1

Dead file (~88 LoC) packages/query-codemods/src/v4/__testfixtures__/namespaced-import.output.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~86 LoC) · ×1

Dead file (~86 LoC) packages/query-codemods/src/v4/__testfixtures__/namespaced-import.input.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~62 LoC) · ×1

Dead file (~62 LoC) packages/query-codemods/src/v5/remove-overloads/__testfixtures__/bug-reports.output.tsx — no import path from any entry point (335 application, 164 tooling, 364 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~53 LoC) · ×1

Dead file (~53 LoC) packages/query-codemods/src/utils/transformers/query-client-transformer.cjs — no import path from any entry point (335 application, 164 tooling, 364 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

R7 · Dead Code · Dead file (~49 LoC) · ×1

Dead file (~49 LoC) packages/query-codemods/src/v4/__testfixtures__/parameter-is-identifier.input.tsx — no import path from any entry point (335 application, 164 tooling, 364 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

R8 · Dependency Hygiene · Unused dependency '@arethetypeswrong/cli' · ×1

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.

R8 · Dependency Hygiene · Unused dependency '@size-limit/preset-small-lib' · ×1

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.

R8 · Dependency Hygiene · Unused dependency '@angular/cli' · ×1

Unused dependency '@angular/cli' — Declared in integrations/angular-cli-20/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.

X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×1

Untrusted text written into markup unescaped packages/react-query-next-experimental/src/HydrationStreamProvider.tsx:158 — `html.join('')` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.

Minor — 1095 finding(s)

D10 · Test Quality · No direct assertions · ×986

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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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 986 of 1604 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.
+ 961 more in this group — see findings.md.

D12 · Dependency Hygiene · Deprecated · ×48

Deprecated: @angular/animations REDACTED:4435 — @angular/animations 20.3.18 is resolved in REDACTED and is marked deprecated by its publisher: "@angular/animations is deprecated. Use `animate.enter` and `animate.leave` instead. For more information see: https://v22.angular.dev/guide/animations.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @react-navigation/core REDACTED:8549 — @react-navigation/core 6.4.17 is resolved in REDACTED and is marked deprecated by its publisher: "This version 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: @react-navigation/elements REDACTED:8555 — @react-navigation/elements 1.3.31 is resolved in REDACTED and is marked deprecated by its publisher: "This version 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: @react-navigation/native REDACTED:8564 — @react-navigation/native 6.1.18 is resolved in REDACTED and is marked deprecated by its publisher: "This version 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: @react-navigation/routers REDACTED:8571 — @react-navigation/routers 6.1.9 is resolved in REDACTED and is marked deprecated by its publisher: "This version 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: @react-navigation/stack REDACTED:8575 — @react-navigation/stack 6.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "This version 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: @ungap/structured-clone REDACTED:10214 — @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: @xmldom/xmldom REDACTED:10684 — @xmldom/xmldom 0.8.12 is resolved in REDACTED and is marked deprecated by its publisher: "this version has critical issues, please update to the latest version". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-android-arm64 REDACTED:10698 — @yuku-codegen/binding-android-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-darwin-arm64 REDACTED:10704 — @yuku-codegen/binding-darwin-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-darwin-x64 REDACTED:10710 — @yuku-codegen/binding-darwin-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-freebsd-x64 REDACTED:10716 — @yuku-codegen/binding-freebsd-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm-gnu REDACTED:10722 — @yuku-codegen/binding-linux-arm-gnu 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm-musl REDACTED:10729 — @yuku-codegen/binding-linux-arm-musl 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm64-gnu REDACTED:10736 — @yuku-codegen/binding-linux-arm64-gnu 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm64-musl REDACTED:10743 — @yuku-codegen/binding-linux-arm64-musl 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-x64-gnu REDACTED:10750 — @yuku-codegen/binding-linux-x64-gnu 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-x64-musl REDACTED:10757 — @yuku-codegen/binding-linux-x64-musl 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-win32-arm64 REDACTED:10764 — @yuku-codegen/binding-win32-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-win32-x64 REDACTED:10770 — @yuku-codegen/binding-win32-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-android-arm64 REDACTED:10776 — @yuku-parser/binding-android-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-darwin-arm64 REDACTED:10782 — @yuku-parser/binding-darwin-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-darwin-x64 REDACTED:10788 — @yuku-parser/binding-darwin-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-freebsd-x64 REDACTED:10794 — @yuku-parser/binding-freebsd-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-arm-gnu REDACTED:10800 — @yuku-parser/binding-linux-arm-gnu 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
+ 23 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×19

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:21 — `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/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/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.

D34 · Knowledge Freshness · Orphaned file · ×10

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/vue-query/src/devtools/devtools.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/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/solid-query/src/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/eslint-plugin-query/src/rules/stable-query-client/stable-query-client.rule.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/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.

D10 · Test Quality · Mock-dominated test · ×8

Mock-dominated test: should notify queryCache and mutationCache if focused packages/query-core/src/__tests__/queryClient.test.tsx:2752 — 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:2781 — 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:3060 — 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:3094 — 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:1386 — 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:1408 — 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.

D30 · Dependency Vulnerabilities · Low CVE · ×7

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1

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

D12 · Dependency Hygiene · Outdated (npm) · ×1

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.

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 37 significant file(s) lose their only recent owner: REDACTED, packages/preact-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, packages/query-persist-client-core/src/persist.ts, packages/svelte-query/src/createInfiniteQuery.ts (+29 more). Pair on, review, or document these before any departure.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (38 single-owned of 195 analysed files in total, 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; 195 of the 517 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/query-devtools/tsdown.config.ts.

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 — 10 of 195 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; 195 of the 517 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/vue-query/src/devtools/devtools.ts, packages/query-codemods/src/v5/is-loading/is-loading.cjs, packages/solid-query/src/index.ts (and 2 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

IC1 · Incompleteness & stubs · Blanket warning suppression · ×1

Blanket warning suppression scripts/create-github-release.mjs:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.

M2 · Architecture documentation · No ADRs · ×1

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

M4 · Documentation accuracy · README/code drift · ×1

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.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.

P3 · Security & performance tooling · No SAST · ×1

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

P4 · Deployment & Rollback · No release approval gate · ×1

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

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/10 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.

X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1

Strict null checking is not enabled everywhere the repository type-checks — 170/172 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.

X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1

Null assertions (`!`) reduce the strict null checking score — ~1.5 `!` null assertions per 1k TypeScript source lines — 86 assertion(s) across the 57136 source line(s) of the 322 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 (23), REDACTED (21), packages/query-devtools/src/Explorer.tsx (6). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

Minor — 65 finding(s)

D12 · Dependency Hygiene · Outdated (npm) · ×46

Outdated (npm): @algolia/client-search — @algolia/client-search is pinned at 5.59.0; registry.npmjs.org publishes 5.60.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 20.3.18; registry.npmjs.org publishes 22.2.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): @angular/compiler — @angular/compiler is pinned at 20.3.18; registry.npmjs.org publishes 22.2.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): @angular/core — @angular/core is pinned at 20.3.18; registry.npmjs.org publishes 22.2.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): @angular/forms — @angular/forms is pinned at 20.3.18; registry.npmjs.org publishes 22.2.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): @angular/platform-browser — @angular/platform-browser is pinned at 20.3.18; registry.npmjs.org publishes 22.2.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): @angular/router — @angular/router is pinned at 20.3.18; registry.npmjs.org publishes 22.2.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): @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.6; registry.npmjs.org publishes 11.1.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @astrojs/solid-js — @astrojs/solid-js is pinned at 7.0.2; registry.npmjs.org publishes 7.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @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): @react-navigation/native — @react-navigation/native is pinned at 6.1.18; registry.npmjs.org publishes 7.5.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): @react-navigation/stack — @react-navigation/stack is pinned at 6.4.1; registry.npmjs.org publishes 7.12.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): @solidjs/router — @solidjs/router is pinned at 0.15.4; registry.npmjs.org publishes 1.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @solidjs/start — @solidjs/start is pinned at 1.3.2; registry.npmjs.org publishes 2.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): @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): @vitejs/plugin-react — @vitejs/plugin-react is pinned at 6.1.1; registry.npmjs.org publishes 6.1.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): @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): astro — astro is pinned at 7.3.5; registry.npmjs.org publishes 7.4.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): expo — expo is pinned at 57.0.24; registry.npmjs.org publishes 58.0.19 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-constants — expo-constants is pinned at 57.0.19; registry.npmjs.org publishes 58.0.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): expo-status-bar — expo-status-bar is pinned at 57.0.1; registry.npmjs.org publishes 58.0.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): graphql — graphql is pinned at 16.13.2; registry.npmjs.org publishes 17.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): msw — msw is pinned at 2.15.0; registry.npmjs.org publishes 3.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.
+ 21 more in this group — see findings.md.

D10 · Test Quality · Skipped (documented) · ×19

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:339 — 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

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f3d7f42ff41d4f76bf19980b0c8ee83d/history.json --exit-code 0 --source .	13	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f3d7f42ff41d4f76bf19980b0c8ee83d/tree.json --exit-code 0 --source .	3	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude .arrow --exclude .avro --exclude .csv --exclude .dat --exclude .db --exclude .feather --exclude .geojson --exclude .h5 --exclude .hdf5 --exclude .jsonl --exclude .log --exclude .ndjson --exclude .npy --exclude .npz --exclude .orc --exclude .parquet --exclude .pickle --exclude .pkl --exclude .psv --exclude .sqlite --exclude .sqlite3 --exclude .tfrecord --exclude .tsv --exclude .txt --exclude examples/react/offline/public --exclude examples/solid/offline/public .	12	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	78	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 13 file(s) — `integrations/react-next-15/app/make-query-client.ts`, `integrations/react-next-16/app/make-query-client.ts`, `knip.ts`, `packages/angular-query-experimental/src/index.ts`, `packages/eslint-plugin-query/src/index.ts`, … (+8 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a178be-1184-7fc6-ac39-5c2eeeafa4c1 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 67% · Adequate ·

At a glance — Architecture · 97% · Exemplary ·

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

At a glance — Readiness · 48% · Weak · gated by P2, P3 ·

At a glance — Security · 18% · Critical · gated by D28, D29, D30, D36, C2 ·

At a glance — Accessibility · 76% · Strong ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts