Public report of apollographql/apollo-client, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 12:53 UTC · Survey ID cd_dbdd9188c3364f70aefff7252143feb5
apollographql/apollo-client
Measured 17 November 2026, 12:50 UTC, at code version 53bae5b
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 80,796 lines of product code in 8 projects, tests not counted · Estimated rebuild effort: about 2.1 person-years · Weakest lens: Production Readiness, 37.6
Findings by how serious they are
67 critical655 serious139 minor
7 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 12:50 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
66of 66 dimensions measured by tools.
828of 861 findings point to an exact file and line, so you can open each one in the code. The other 33 concern the repository as a whole, such as missing documentation.
66dimensions across 6 lenses, read from 80,796 lines of product code in 8 projects.
apollographql/apollo-client is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no logging, tracing or health checks in the code, and it has packages under a licence on your banned list. It scores 53.9 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 37.6, is the weakest lens and counts most in the score. The best first step is replacing the 11 packages under a banned licence, worth about 14.3 points. Replacing the 36 deprecated dependencies comes next, worth about 11.1 points. Raising Production Readiness to 70 would lift the score to about 67.3.
Thirty-six known security holes in the packages the code depends on can be used by attackers. Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and eleven packages carry licence risk. Updating the vulnerable packages, pinning each tool to an exact version and replacing or clearing the banned-licence packages would close these risks. Setting a waiting period for automatic updates would fix the two automatic dependency updates that take new releases at once. The five tests that check nothing need to check the result they produce.
The product code is 80,796 lines, about €310,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 37.6 to 70, the lowest score rated Strong, the score would rise from 53.9 to about 67.3.
Code composition: what the lines of code are
Product code 26%Tests 74%
Rebuild cost: about €310,000 · Estimate
Cost to rebuild
€100,000 to €520,000, for 1,715 to 5,440 hours of work, about 2.1 person-years for 1 to 5 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.8 at a score of 54. 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: 80,796 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 11 Banned license finding(s) in License Compliance — start with pnpm-lock.yaml (11).
Raises the score by about 14.3 points · Medium effort · License Compliance
2
Resolve the 36 Deprecated finding(s) in Dependency Hygiene — start with pnpm-lock.yaml (32), REDACTED (4).
Raises the score by about 11.1 points · Medium effort · Dependency Hygiene
3
Resolve the 5 No assertions (empty test) finding(s) in Test Quality — start with types.test.ts (2), cache.ts, optimistic.ts.
Raises the score by about 4.6 points · Low effort · Test Quality
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 €310,000 to build again, about 2.1 person-years of work. Its weakest lens is Production Readiness, at 37.6 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 11 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 14.3 points for medium effort, because it clears the 11 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 9% on every change. The history of the code shows how much it changes: about 17,956 lines over the last 90 days, which is about 72,822 lines a year. At that pace, the extra work comes to an estimated 7.6 to 45.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: 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.
185 modules, with 275 dependencies between them. 2 loops run through 15 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 145 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.
src.cache.core.types.Cache uses src.masking.GraphQLCodegenDataMasking, so a change to src.masking.GraphQLCodegenDataMasking can break src.cache.core.types.Cache, while a change to src.cache.core.types.Cache can't break src.masking.GraphQLCodegenDataMasking.
Position
Below the diagonal: src.cache.core.types.Cache uses a module listed above it, which is the healthy direction.
src.cache.inmemory.types uses src.utilities.graphql.storeUtils, so a change to src.utilities.graphql.storeUtils can break src.cache.inmemory.types, while a change to src.cache.inmemory.types can't break src.utilities.graphql.storeUtils.
Position
Below the diagonal: src.cache.inmemory.types uses a module listed above it, which is the healthy direction.
11→24 src.core.watchQueryOptions uses src.core.ObservableQuerypart of a loop✕
Connections
1 pair of types, where a type in src.core.watchQueryOptions uses a type in src.core.ObservableQuery.
src.core.watchQueryOptions uses src.core.ObservableQuery, so a change to src.core.ObservableQuery can break src.core.watchQueryOptions, while a change to src.core.watchQueryOptions can't break src.core.ObservableQuery.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→20 src.link.core.ApolloLink uses src.core.typespart of a loop✕
Connections
1 pair of types, where a type in src.link.core.ApolloLink uses a type in src.core.types.
src.link.core.ApolloLink uses src.core.types, so a change to src.core.types can break src.link.core.ApolloLink, while a change to src.link.core.ApolloLink can't break src.core.types.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→25 src.link.core.ApolloLink uses src.core.ApolloClientpart of a loop✕
Connections
2 pairs of types, where a type in src.link.core.ApolloLink uses a type in src.core.ApolloClient.
src.link.core.ApolloLink uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.link.core.ApolloLink, while a change to src.link.core.ApolloLink can't break src.core.ApolloClient.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.cache.inmemory.entityStore uses src.utilities.graphql.storeUtils, so a change to src.utilities.graphql.storeUtils can break src.cache.inmemory.entityStore, while a change to src.cache.inmemory.entityStore can't break src.utilities.graphql.storeUtils.
Position
Below the diagonal: src.cache.inmemory.entityStore uses a module listed above it, which is the healthy direction.
src.cache.inmemory.entityStore uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.cache.inmemory.entityStore, while a change to src.cache.inmemory.entityStore can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.cache.inmemory.entityStore uses a module listed above it, which is the healthy direction.
src.cache.inmemory.entityStore uses src.cache.inmemory.types, so a change to src.cache.inmemory.types can break src.cache.inmemory.entityStore, while a change to src.cache.inmemory.entityStore can't break src.cache.inmemory.types.
Position
Below the diagonal: src.cache.inmemory.entityStore uses a module listed above it, which is the healthy direction.
13→37 src.cache.inmemory.entityStore uses src.cache.inmemory.policiespart of a loop✕
Connections
1 pair of types, where a type in src.cache.inmemory.entityStore uses a type in src.cache.inmemory.policies.
src.cache.inmemory.entityStore uses src.cache.inmemory.policies, so a change to src.cache.inmemory.policies can break src.cache.inmemory.entityStore, while a change to src.cache.inmemory.entityStore can't break src.cache.inmemory.policies.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.cache.inmemory.readFromStore uses src.utilities.internal.types.FragmentMap, so a change to src.utilities.internal.types.FragmentMap can break src.cache.inmemory.readFromStore, while a change to src.cache.inmemory.readFromStore can't break src.utilities.internal.types.FragmentMap.
Position
Below the diagonal: src.cache.inmemory.readFromStore uses a module listed above it, which is the healthy direction.
src.cache.inmemory.readFromStore uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.cache.inmemory.readFromStore, while a change to src.cache.inmemory.readFromStore can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.cache.inmemory.readFromStore uses a module listed above it, which is the healthy direction.
src.cache.inmemory.readFromStore uses src.cache.inmemory.types, so a change to src.cache.inmemory.types can break src.cache.inmemory.readFromStore, while a change to src.cache.inmemory.readFromStore can't break src.cache.inmemory.types.
Position
Below the diagonal: src.cache.inmemory.readFromStore uses a module listed above it, which is the healthy direction.
14→33 src.cache.inmemory.readFromStore uses src.cache.inmemory.inMemoryCachepart of a loop✕
Connections
1 pair of types, where a type in src.cache.inmemory.readFromStore uses a type in src.cache.inmemory.inMemoryCache.
src.cache.inmemory.readFromStore uses src.cache.inmemory.inMemoryCache, so a change to src.cache.inmemory.inMemoryCache can break src.cache.inmemory.readFromStore, while a change to src.cache.inmemory.readFromStore can't break src.cache.inmemory.inMemoryCache.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→37 src.cache.inmemory.readFromStore uses src.cache.inmemory.policiespart of a loop✕
Connections
1 pair of types, where a type in src.cache.inmemory.readFromStore uses a type in src.cache.inmemory.policies.
src.cache.inmemory.readFromStore uses src.cache.inmemory.policies, so a change to src.cache.inmemory.policies can break src.cache.inmemory.readFromStore, while a change to src.cache.inmemory.readFromStore can't break src.cache.inmemory.policies.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.core uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.core, while a change to src.core can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
src.core uses src.core.watchQueryOptions, so a change to src.core.watchQueryOptions can break src.core, while a change to src.core can't break src.core.watchQueryOptions.
Position
Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
src.core uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.core, while a change to src.core can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.core uses a module listed above it, which is the healthy direction.
src.link.client-awareness.ClientAwarenessLink uses src.cache.core.Scalar, so a change to src.cache.core.Scalar can break src.link.client-awareness.ClientAwarenessLink, while a change to src.link.client-awareness.ClientAwarenessLink can't break src.cache.core.Scalar.
Position
Below the diagonal: src.link.client-awareness.ClientAwarenessLink uses a module listed above it, which is the healthy direction.
src.link.client-awareness.ClientAwarenessLink uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.link.client-awareness.ClientAwarenessLink, while a change to src.link.client-awareness.ClientAwarenessLink can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.link.client-awareness.ClientAwarenessLink uses a module listed above it, which is the healthy direction.
src.link.http.BaseHttpLink uses src.cache.core.Scalar, so a change to src.cache.core.Scalar can break src.link.http.BaseHttpLink, while a change to src.link.http.BaseHttpLink can't break src.cache.core.Scalar.
Position
Below the diagonal: src.link.http.BaseHttpLink uses a module listed above it, which is the healthy direction.
src.link.http.BaseHttpLink uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.link.http.BaseHttpLink, while a change to src.link.http.BaseHttpLink can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.link.http.BaseHttpLink uses a module listed above it, which is the healthy direction.
src.testing.core.mocking.mockLink uses src.cache.core.Scalar, so a change to src.cache.core.Scalar can break src.testing.core.mocking.mockLink, while a change to src.testing.core.mocking.mockLink can't break src.cache.core.Scalar.
Position
Below the diagonal: src.testing.core.mocking.mockLink uses a module listed above it, which is the healthy direction.
src.testing.core.mocking.mockLink uses src.core.defaultOptions, so a change to src.core.defaultOptions can break src.testing.core.mocking.mockLink, while a change to src.testing.core.mocking.mockLink can't break src.core.defaultOptions.
Position
Below the diagonal: src.testing.core.mocking.mockLink uses a module listed above it, which is the healthy direction.
src.testing.core.mocking.mockLink uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.testing.core.mocking.mockLink, while a change to src.testing.core.mocking.mockLink can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.testing.core.mocking.mockLink uses a module listed above it, which is the healthy direction.
src.cache.inmemory.writeToStore uses src.utilities.graphql.storeUtils, so a change to src.utilities.graphql.storeUtils can break src.cache.inmemory.writeToStore, while a change to src.cache.inmemory.writeToStore can't break src.utilities.graphql.storeUtils.
Position
Below the diagonal: src.cache.inmemory.writeToStore uses a module listed above it, which is the healthy direction.
src.cache.inmemory.writeToStore uses src.utilities.internal.types.FragmentMap, so a change to src.utilities.internal.types.FragmentMap can break src.cache.inmemory.writeToStore, while a change to src.cache.inmemory.writeToStore can't break src.utilities.internal.types.FragmentMap.
Position
Below the diagonal: src.cache.inmemory.writeToStore uses a module listed above it, which is the healthy direction.
src.cache.inmemory.writeToStore uses src.cache.inmemory.types, so a change to src.cache.inmemory.types can break src.cache.inmemory.writeToStore, while a change to src.cache.inmemory.writeToStore can't break src.cache.inmemory.types.
Position
Below the diagonal: src.cache.inmemory.writeToStore uses a module listed above it, which is the healthy direction.
src.cache.inmemory.writeToStore uses src.cache.inmemory.readFromStore, so a change to src.cache.inmemory.readFromStore can break src.cache.inmemory.writeToStore, while a change to src.cache.inmemory.writeToStore can't break src.cache.inmemory.readFromStore.
Position
Below the diagonal: src.cache.inmemory.writeToStore uses a module listed above it, which is the healthy direction.
19→33 src.cache.inmemory.writeToStore uses src.cache.inmemory.inMemoryCachepart of a loop✕
Connections
1 pair of types, where a type in src.cache.inmemory.writeToStore uses a type in src.cache.inmemory.inMemoryCache.
src.cache.inmemory.writeToStore uses src.cache.inmemory.inMemoryCache, so a change to src.cache.inmemory.inMemoryCache can break src.cache.inmemory.writeToStore, while a change to src.cache.inmemory.writeToStore can't break src.cache.inmemory.inMemoryCache.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.core.types uses src.link.client-awareness.ClientAwarenessLink, so a change to src.link.client-awareness.ClientAwarenessLink can break src.core.types, while a change to src.core.types can't break src.link.client-awareness.ClientAwarenessLink.
Position
Below the diagonal: src.core.types uses a module listed above it, which is the healthy direction.
src.link.http uses src.cache.core.Scalar, so a change to src.cache.core.Scalar can break src.link.http, while a change to src.link.http can't break src.cache.core.Scalar.
Position
Below the diagonal: src.link.http uses a module listed above it, which is the healthy direction.
src.link.http uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.link.http, while a change to src.link.http can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.link.http uses a module listed above it, which is the healthy direction.
src.link.http uses src.link.http.BaseHttpLink, so a change to src.link.http.BaseHttpLink can break src.link.http, while a change to src.link.http can't break src.link.http.BaseHttpLink.
Position
Below the diagonal: src.link.http uses a module listed above it, which is the healthy direction.
src.core.QueryManager uses config.schema_package_json, so a change to config.schema_package_json can break src.core.QueryManager, while a change to src.core.QueryManager can't break config.schema_package_json.
Position
Below the diagonal: src.core.QueryManager uses a module listed above it, which is the healthy direction.
src.core.QueryManager uses src.cache.core.Scalar, so a change to src.cache.core.Scalar can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.cache.core.Scalar.
Position
Below the diagonal: src.core.QueryManager uses a module listed above it, which is the healthy direction.
src.core.QueryManager uses src.core.defaultOptions, so a change to src.core.defaultOptions can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.core.defaultOptions.
Position
Below the diagonal: src.core.QueryManager uses a module listed above it, which is the healthy direction.
src.core.QueryManager uses src.core.networkStatus, so a change to src.core.networkStatus can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.core.networkStatus.
Position
Below the diagonal: src.core.QueryManager uses a module listed above it, which is the healthy direction.
src.core.QueryManager uses src.incremental.types, so a change to src.incremental.types can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.incremental.types.
Position
Below the diagonal: src.core.QueryManager uses a module listed above it, which is the healthy direction.
src.core.QueryManager uses src.masking.GraphQLCodegenDataMasking, so a change to src.masking.GraphQLCodegenDataMasking can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.masking.GraphQLCodegenDataMasking.
Position
Below the diagonal: src.core.QueryManager uses a module listed above it, which is the healthy direction.
src.core.QueryManager uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.core.QueryManager uses a module listed above it, which is the healthy direction.
src.core.QueryManager uses src.core.watchQueryOptions, so a change to src.core.watchQueryOptions can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.core.watchQueryOptions.
Position
Below the diagonal: src.core.QueryManager uses a module listed above it, which is the healthy direction.
src.core.QueryManager uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.core.QueryManager uses a module listed above it, which is the healthy direction.
src.core.QueryManager uses src.core.types, so a change to src.core.types can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.core.types.
Position
Below the diagonal: src.core.QueryManager uses a module listed above it, which is the healthy direction.
22→24 src.core.QueryManager uses src.core.ObservableQuerypart of a loop✕
Connections
1 pair of types, where a type in src.core.QueryManager uses a type in src.core.ObservableQuery.
src.core.QueryManager uses src.core.ObservableQuery, so a change to src.core.ObservableQuery can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.core.ObservableQuery.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→25 src.core.QueryManager uses src.core.ApolloClientpart of a loop✕
Connections
3 pairs of types, where a type in src.core.QueryManager uses a type in src.core.ApolloClient.
src.core.QueryManager uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.core.QueryManager, while a change to src.core.QueryManager can't break src.core.ApolloClient.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.local-state.LocalState uses src.utilities.internal.types.FragmentMap, so a change to src.utilities.internal.types.FragmentMap can break src.local-state.LocalState, while a change to src.local-state.LocalState can't break src.utilities.internal.types.FragmentMap.
Position
Below the diagonal: src.local-state.LocalState uses a module listed above it, which is the healthy direction.
src.local-state.LocalState uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.local-state.LocalState, while a change to src.local-state.LocalState can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.local-state.LocalState uses a module listed above it, which is the healthy direction.
src.local-state.LocalState uses src.core.watchQueryOptions, so a change to src.core.watchQueryOptions can break src.local-state.LocalState, while a change to src.local-state.LocalState can't break src.core.watchQueryOptions.
Position
Below the diagonal: src.local-state.LocalState uses a module listed above it, which is the healthy direction.
src.local-state.LocalState uses src.core.types, so a change to src.core.types can break src.local-state.LocalState, while a change to src.local-state.LocalState can't break src.core.types.
Position
Below the diagonal: src.local-state.LocalState uses a module listed above it, which is the healthy direction.
23→25 src.local-state.LocalState uses src.core.ApolloClientpart of a loop✕
Connections
3 pairs of types, where a type in src.local-state.LocalState uses a type in src.core.ApolloClient.
src.local-state.LocalState uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.local-state.LocalState, while a change to src.local-state.LocalState can't break src.core.ApolloClient.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.core.ObservableQuery uses config.schema_package_json, so a change to config.schema_package_json can break src.core.ObservableQuery, while a change to src.core.ObservableQuery can't break config.schema_package_json.
Position
Below the diagonal: src.core.ObservableQuery uses a module listed above it, which is the healthy direction.
src.core.ObservableQuery uses src.cache.core.Scalar, so a change to src.cache.core.Scalar can break src.core.ObservableQuery, while a change to src.core.ObservableQuery can't break src.cache.core.Scalar.
Position
Below the diagonal: src.core.ObservableQuery uses a module listed above it, which is the healthy direction.
src.core.ObservableQuery uses src.core.networkStatus, so a change to src.core.networkStatus can break src.core.ObservableQuery, while a change to src.core.ObservableQuery can't break src.core.networkStatus.
Position
Below the diagonal: src.core.ObservableQuery uses a module listed above it, which is the healthy direction.
src.core.ObservableQuery uses src.masking.GraphQLCodegenDataMasking, so a change to src.masking.GraphQLCodegenDataMasking can break src.core.ObservableQuery, while a change to src.core.ObservableQuery can't break src.masking.GraphQLCodegenDataMasking.
Position
Below the diagonal: src.core.ObservableQuery uses a module listed above it, which is the healthy direction.
src.core.ObservableQuery uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.core.ObservableQuery, while a change to src.core.ObservableQuery can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.core.ObservableQuery uses a module listed above it, which is the healthy direction.
src.core.ObservableQuery uses src.core.watchQueryOptions, so a change to src.core.watchQueryOptions can break src.core.ObservableQuery, while a change to src.core.ObservableQuery can't break src.core.watchQueryOptions.
Position
Below the diagonal: src.core.ObservableQuery uses a module listed above it, which is the healthy direction.
src.core.ObservableQuery uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.core.ObservableQuery, while a change to src.core.ObservableQuery can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.core.ObservableQuery uses a module listed above it, which is the healthy direction.
src.core.ObservableQuery uses src.core.types, so a change to src.core.types can break src.core.ObservableQuery, while a change to src.core.ObservableQuery can't break src.core.types.
Position
Below the diagonal: src.core.ObservableQuery uses a module listed above it, which is the healthy direction.
src.core.ObservableQuery uses src.core.QueryManager, so a change to src.core.QueryManager can break src.core.ObservableQuery, while a change to src.core.ObservableQuery can't break src.core.QueryManager.
Position
Below the diagonal: src.core.ObservableQuery uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses config.schema_package_json, so a change to config.schema_package_json can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break config.schema_package_json.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.cache.core.Scalar, so a change to src.cache.core.Scalar can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.cache.core.Scalar.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.core.defaultOptions, so a change to src.core.defaultOptions can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.core.defaultOptions.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.incremental.types, so a change to src.incremental.types can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.incremental.types.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.masking.GraphQLCodegenDataMasking, so a change to src.masking.GraphQLCodegenDataMasking can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.masking.GraphQLCodegenDataMasking.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.link.client-awareness.ClientAwarenessLink, so a change to src.link.client-awareness.ClientAwarenessLink can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.link.client-awareness.ClientAwarenessLink.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.core.types, so a change to src.core.types can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.core.types.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.core.QueryManager, so a change to src.core.QueryManager can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.core.QueryManager.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.local-state.LocalState, so a change to src.local-state.LocalState can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.local-state.LocalState.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
src.core.ApolloClient uses src.core.ObservableQuery, so a change to src.core.ObservableQuery can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.core.ObservableQuery.
Position
Below the diagonal: src.core.ApolloClient uses a module listed above it, which is the healthy direction.
25→28 src.core.ApolloClient uses src.cache.core.cachepart of a loop✕
Connections
2 pairs of types, where a type in src.core.ApolloClient uses a type in src.cache.core.cache.
src.core.ApolloClient uses src.cache.core.cache, so a change to src.cache.core.cache can break src.core.ApolloClient, while a change to src.core.ApolloClient can't break src.cache.core.cache.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.core.QueryInfo uses src.incremental.types, so a change to src.incremental.types can break src.core.QueryInfo, while a change to src.core.QueryInfo can't break src.incremental.types.
Position
Below the diagonal: src.core.QueryInfo uses a module listed above it, which is the healthy direction.
src.core.QueryInfo uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.core.QueryInfo, while a change to src.core.QueryInfo can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.core.QueryInfo uses a module listed above it, which is the healthy direction.
src.core.QueryInfo uses src.cache.inmemory.types, so a change to src.cache.inmemory.types can break src.core.QueryInfo, while a change to src.core.QueryInfo can't break src.cache.inmemory.types.
Position
Below the diagonal: src.core.QueryInfo uses a module listed above it, which is the healthy direction.
src.core.QueryInfo uses src.core.watchQueryOptions, so a change to src.core.watchQueryOptions can break src.core.QueryInfo, while a change to src.core.QueryInfo can't break src.core.watchQueryOptions.
Position
Below the diagonal: src.core.QueryInfo uses a module listed above it, which is the healthy direction.
src.core.QueryInfo uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.core.QueryInfo, while a change to src.core.QueryInfo can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.core.QueryInfo uses a module listed above it, which is the healthy direction.
src.core.QueryInfo uses src.core.QueryManager, so a change to src.core.QueryManager can break src.core.QueryInfo, while a change to src.core.QueryInfo can't break src.core.QueryManager.
Position
Below the diagonal: src.core.QueryInfo uses a module listed above it, which is the healthy direction.
src.core.QueryInfo uses src.core.ObservableQuery, so a change to src.core.ObservableQuery can break src.core.QueryInfo, while a change to src.core.QueryInfo can't break src.core.ObservableQuery.
Position
Below the diagonal: src.core.QueryInfo uses a module listed above it, which is the healthy direction.
src.react.internal.cache.QueryReference uses src.masking.GraphQLCodegenDataMasking, so a change to src.masking.GraphQLCodegenDataMasking can break src.react.internal.cache.QueryReference, while a change to src.react.internal.cache.QueryReference can't break src.masking.GraphQLCodegenDataMasking.
Position
Below the diagonal: src.react.internal.cache.QueryReference uses a module listed above it, which is the healthy direction.
src.react.internal.cache.QueryReference uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.react.internal.cache.QueryReference, while a change to src.react.internal.cache.QueryReference can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.react.internal.cache.QueryReference uses a module listed above it, which is the healthy direction.
src.react.internal.cache.QueryReference uses src.core.ObservableQuery, so a change to src.core.ObservableQuery can break src.react.internal.cache.QueryReference, while a change to src.react.internal.cache.QueryReference can't break src.core.ObservableQuery.
Position
Below the diagonal: src.react.internal.cache.QueryReference uses a module listed above it, which is the healthy direction.
src.cache.core.cache uses src.masking.GraphQLCodegenDataMasking, so a change to src.masking.GraphQLCodegenDataMasking can break src.cache.core.cache, while a change to src.cache.core.cache can't break src.masking.GraphQLCodegenDataMasking.
Position
Below the diagonal: src.cache.core.cache uses a module listed above it, which is the healthy direction.
src.cache.core.cache uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.cache.core.cache, while a change to src.cache.core.cache can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.cache.core.cache uses a module listed above it, which is the healthy direction.
src.cache.core.cache uses src.core.types, so a change to src.core.types can break src.cache.core.cache, while a change to src.cache.core.cache can't break src.core.types.
Position
Below the diagonal: src.cache.core.cache uses a module listed above it, which is the healthy direction.
src.cache.core.cache uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.cache.core.cache, while a change to src.cache.core.cache can't break src.core.ApolloClient.
Position
Below the diagonal: src.cache.core.cache uses a module listed above it, which is the healthy direction.
src.react.hooks.useLazyQuery uses src.core.networkStatus, so a change to src.core.networkStatus can break src.react.hooks.useLazyQuery, while a change to src.react.hooks.useLazyQuery can't break src.core.networkStatus.
Position
Below the diagonal: src.react.hooks.useLazyQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useLazyQuery uses src.masking.GraphQLCodegenDataMasking, so a change to src.masking.GraphQLCodegenDataMasking can break src.react.hooks.useLazyQuery, while a change to src.react.hooks.useLazyQuery can't break src.masking.GraphQLCodegenDataMasking.
Position
Below the diagonal: src.react.hooks.useLazyQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useLazyQuery uses src.core.watchQueryOptions, so a change to src.core.watchQueryOptions can break src.react.hooks.useLazyQuery, while a change to src.react.hooks.useLazyQuery can't break src.core.watchQueryOptions.
Position
Below the diagonal: src.react.hooks.useLazyQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useLazyQuery uses src.core.types, so a change to src.core.types can break src.react.hooks.useLazyQuery, while a change to src.react.hooks.useLazyQuery can't break src.core.types.
Position
Below the diagonal: src.react.hooks.useLazyQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useLazyQuery uses src.core.ObservableQuery, so a change to src.core.ObservableQuery can break src.react.hooks.useLazyQuery, while a change to src.react.hooks.useLazyQuery can't break src.core.ObservableQuery.
Position
Below the diagonal: src.react.hooks.useLazyQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useLazyQuery uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.react.hooks.useLazyQuery, while a change to src.react.hooks.useLazyQuery can't break src.core.ApolloClient.
Position
Below the diagonal: src.react.hooks.useLazyQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useQuery uses src.core.networkStatus, so a change to src.core.networkStatus can break src.react.hooks.useQuery, while a change to src.react.hooks.useQuery can't break src.core.networkStatus.
Position
Below the diagonal: src.react.hooks.useQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useQuery uses src.masking.GraphQLCodegenDataMasking, so a change to src.masking.GraphQLCodegenDataMasking can break src.react.hooks.useQuery, while a change to src.react.hooks.useQuery can't break src.masking.GraphQLCodegenDataMasking.
Position
Below the diagonal: src.react.hooks.useQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useQuery uses src.core.watchQueryOptions, so a change to src.core.watchQueryOptions can break src.react.hooks.useQuery, while a change to src.react.hooks.useQuery can't break src.core.watchQueryOptions.
Position
Below the diagonal: src.react.hooks.useQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useQuery uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.react.hooks.useQuery, while a change to src.react.hooks.useQuery can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.react.hooks.useQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useQuery uses src.core.types, so a change to src.core.types can break src.react.hooks.useQuery, while a change to src.react.hooks.useQuery can't break src.core.types.
Position
Below the diagonal: src.react.hooks.useQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useQuery uses src.core.ObservableQuery, so a change to src.core.ObservableQuery can break src.react.hooks.useQuery, while a change to src.react.hooks.useQuery can't break src.core.ObservableQuery.
Position
Below the diagonal: src.react.hooks.useQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useQuery uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.react.hooks.useQuery, while a change to src.react.hooks.useQuery can't break src.core.ApolloClient.
Position
Below the diagonal: src.react.hooks.useQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useSubscription uses src.masking.GraphQLCodegenDataMasking, so a change to src.masking.GraphQLCodegenDataMasking can break src.react.hooks.useSubscription, while a change to src.react.hooks.useSubscription can't break src.masking.GraphQLCodegenDataMasking.
Position
Below the diagonal: src.react.hooks.useSubscription uses a module listed above it, which is the healthy direction.
src.react.hooks.useSubscription uses src.core.watchQueryOptions, so a change to src.core.watchQueryOptions can break src.react.hooks.useSubscription, while a change to src.react.hooks.useSubscription can't break src.core.watchQueryOptions.
Position
Below the diagonal: src.react.hooks.useSubscription uses a module listed above it, which is the healthy direction.
src.react.hooks.useSubscription uses src.core.types, so a change to src.core.types can break src.react.hooks.useSubscription, while a change to src.react.hooks.useSubscription can't break src.core.types.
Position
Below the diagonal: src.react.hooks.useSubscription uses a module listed above it, which is the healthy direction.
src.react.hooks.useSubscription uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.react.hooks.useSubscription, while a change to src.react.hooks.useSubscription can't break src.core.ApolloClient.
Position
Below the diagonal: src.react.hooks.useSubscription uses a module listed above it, which is the healthy direction.
src.react.hooks.useSuspenseQuery uses src.core.networkStatus, so a change to src.core.networkStatus can break src.react.hooks.useSuspenseQuery, while a change to src.react.hooks.useSuspenseQuery can't break src.core.networkStatus.
Position
Below the diagonal: src.react.hooks.useSuspenseQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useSuspenseQuery uses src.core.watchQueryOptions, so a change to src.core.watchQueryOptions can break src.react.hooks.useSuspenseQuery, while a change to src.react.hooks.useSuspenseQuery can't break src.core.watchQueryOptions.
Position
Below the diagonal: src.react.hooks.useSuspenseQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useSuspenseQuery uses src.core.types, so a change to src.core.types can break src.react.hooks.useSuspenseQuery, while a change to src.react.hooks.useSuspenseQuery can't break src.core.types.
Position
Below the diagonal: src.react.hooks.useSuspenseQuery uses a module listed above it, which is the healthy direction.
src.react.hooks.useSuspenseQuery uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.react.hooks.useSuspenseQuery, while a change to src.react.hooks.useSuspenseQuery can't break src.core.ApolloClient.
Position
Below the diagonal: src.react.hooks.useSuspenseQuery uses a module listed above it, which is the healthy direction.
src.cache.inmemory.inMemoryCache uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.cache.inmemory.inMemoryCache, while a change to src.cache.inmemory.inMemoryCache can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.cache.inmemory.inMemoryCache uses a module listed above it, which is the healthy direction.
src.cache.inmemory.inMemoryCache uses src.cache.inmemory.types, so a change to src.cache.inmemory.types can break src.cache.inmemory.inMemoryCache, while a change to src.cache.inmemory.inMemoryCache can't break src.cache.inmemory.types.
Position
Below the diagonal: src.cache.inmemory.inMemoryCache uses a module listed above it, which is the healthy direction.
src.cache.inmemory.inMemoryCache uses src.cache.inmemory.entityStore, so a change to src.cache.inmemory.entityStore can break src.cache.inmemory.inMemoryCache, while a change to src.cache.inmemory.inMemoryCache can't break src.cache.inmemory.entityStore.
Position
Below the diagonal: src.cache.inmemory.inMemoryCache uses a module listed above it, which is the healthy direction.
src.cache.inmemory.inMemoryCache uses src.cache.inmemory.readFromStore, so a change to src.cache.inmemory.readFromStore can break src.cache.inmemory.inMemoryCache, while a change to src.cache.inmemory.inMemoryCache can't break src.cache.inmemory.readFromStore.
Position
Below the diagonal: src.cache.inmemory.inMemoryCache uses a module listed above it, which is the healthy direction.
src.cache.inmemory.inMemoryCache uses src.cache.inmemory.writeToStore, so a change to src.cache.inmemory.writeToStore can break src.cache.inmemory.inMemoryCache, while a change to src.cache.inmemory.inMemoryCache can't break src.cache.inmemory.writeToStore.
Position
Below the diagonal: src.cache.inmemory.inMemoryCache uses a module listed above it, which is the healthy direction.
src.cache.inmemory.inMemoryCache uses src.cache.core.cache, so a change to src.cache.core.cache can break src.cache.inmemory.inMemoryCache, while a change to src.cache.inmemory.inMemoryCache can't break src.cache.core.cache.
Position
Below the diagonal: src.cache.inmemory.inMemoryCache uses a module listed above it, which is the healthy direction.
33→37 src.cache.inmemory.inMemoryCache uses src.cache.inmemory.policiespart of a loop✕
Connections
1 pair of types, where a type in src.cache.inmemory.inMemoryCache uses a type in src.cache.inmemory.policies.
src.cache.inmemory.inMemoryCache uses src.cache.inmemory.policies, so a change to src.cache.inmemory.policies can break src.cache.inmemory.inMemoryCache, while a change to src.cache.inmemory.inMemoryCache can't break src.cache.inmemory.policies.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
src.react.hooks uses src.cache.core.Scalar, so a change to src.cache.core.Scalar can break src.react.hooks, while a change to src.react.hooks can't break src.cache.core.Scalar.
Position
Below the diagonal: src.react.hooks uses a module listed above it, which is the healthy direction.
src.react.hooks uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.react.hooks, while a change to src.react.hooks can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.react.hooks uses a module listed above it, which is the healthy direction.
src.react.hooks uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.react.hooks, while a change to src.react.hooks can't break src.core.ApolloClient.
Position
Below the diagonal: src.react.hooks uses a module listed above it, which is the healthy direction.
src.react.hooks uses src.react.internal.cache.QueryReference, so a change to src.react.internal.cache.QueryReference can break src.react.hooks, while a change to src.react.hooks can't break src.react.internal.cache.QueryReference.
Position
Below the diagonal: src.react.hooks uses a module listed above it, which is the healthy direction.
src.react.hooks uses src.cache.core.cache, so a change to src.cache.core.cache can break src.react.hooks, while a change to src.react.hooks can't break src.cache.core.cache.
Position
Below the diagonal: src.react.hooks uses a module listed above it, which is the healthy direction.
src.react.hooks uses src.react.hooks.useQuery, so a change to src.react.hooks.useQuery can break src.react.hooks, while a change to src.react.hooks can't break src.react.hooks.useQuery.
Position
Below the diagonal: src.react.hooks uses a module listed above it, which is the healthy direction.
src.react.hooks uses src.react.hooks.useSuspenseQuery, so a change to src.react.hooks.useSuspenseQuery can break src.react.hooks, while a change to src.react.hooks can't break src.react.hooks.useSuspenseQuery.
Position
Below the diagonal: src.react.hooks uses a module listed above it, which is the healthy direction.
src.react.internal.cache.FragmentReference uses src.masking.GraphQLCodegenDataMasking, so a change to src.masking.GraphQLCodegenDataMasking can break src.react.internal.cache.FragmentReference, while a change to src.react.internal.cache.FragmentReference can't break src.masking.GraphQLCodegenDataMasking.
Position
Below the diagonal: src.react.internal.cache.FragmentReference uses a module listed above it, which is the healthy direction.
src.react.internal.cache.FragmentReference uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.react.internal.cache.FragmentReference, while a change to src.react.internal.cache.FragmentReference can't break src.core.ApolloClient.
Position
Below the diagonal: src.react.internal.cache.FragmentReference uses a module listed above it, which is the healthy direction.
src.react.internal.cache.FragmentReference uses src.cache.core.cache, so a change to src.cache.core.cache can break src.react.internal.cache.FragmentReference, while a change to src.react.internal.cache.FragmentReference can't break src.cache.core.cache.
Position
Below the diagonal: src.react.internal.cache.FragmentReference uses a module listed above it, which is the healthy direction.
src.testing.react.MockedProvider uses src.core.defaultOptions, so a change to src.core.defaultOptions can break src.testing.react.MockedProvider, while a change to src.testing.react.MockedProvider can't break src.core.defaultOptions.
Position
Below the diagonal: src.testing.react.MockedProvider uses a module listed above it, which is the healthy direction.
src.testing.react.MockedProvider uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.testing.react.MockedProvider, while a change to src.testing.react.MockedProvider can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.testing.react.MockedProvider uses a module listed above it, which is the healthy direction.
src.testing.react.MockedProvider uses src.testing.core.mocking.mockLink, so a change to src.testing.core.mocking.mockLink can break src.testing.react.MockedProvider, while a change to src.testing.react.MockedProvider can't break src.testing.core.mocking.mockLink.
Position
Below the diagonal: src.testing.react.MockedProvider uses a module listed above it, which is the healthy direction.
src.testing.react.MockedProvider uses src.local-state.LocalState, so a change to src.local-state.LocalState can break src.testing.react.MockedProvider, while a change to src.testing.react.MockedProvider can't break src.local-state.LocalState.
Position
Below the diagonal: src.testing.react.MockedProvider uses a module listed above it, which is the healthy direction.
src.testing.react.MockedProvider uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.testing.react.MockedProvider, while a change to src.testing.react.MockedProvider can't break src.core.ApolloClient.
Position
Below the diagonal: src.testing.react.MockedProvider uses a module listed above it, which is the healthy direction.
src.testing.react.MockedProvider uses src.cache.core.cache, so a change to src.cache.core.cache can break src.testing.react.MockedProvider, while a change to src.testing.react.MockedProvider can't break src.cache.core.cache.
Position
Below the diagonal: src.testing.react.MockedProvider uses a module listed above it, which is the healthy direction.
src.cache.inmemory.policies uses src.incremental.types, so a change to src.incremental.types can break src.cache.inmemory.policies, while a change to src.cache.inmemory.policies can't break src.incremental.types.
Position
Below the diagonal: src.cache.inmemory.policies uses a module listed above it, which is the healthy direction.
src.cache.inmemory.policies uses src.utilities.graphql.storeUtils, so a change to src.utilities.graphql.storeUtils can break src.cache.inmemory.policies, while a change to src.cache.inmemory.policies can't break src.utilities.graphql.storeUtils.
Position
Below the diagonal: src.cache.inmemory.policies uses a module listed above it, which is the healthy direction.
src.cache.inmemory.policies uses src.cache.inmemory.types, so a change to src.cache.inmemory.types can break src.cache.inmemory.policies, while a change to src.cache.inmemory.policies can't break src.cache.inmemory.types.
Position
Below the diagonal: src.cache.inmemory.policies uses a module listed above it, which is the healthy direction.
src.cache.inmemory.policies uses src.cache.inmemory.writeToStore, so a change to src.cache.inmemory.writeToStore can break src.cache.inmemory.policies, while a change to src.cache.inmemory.policies can't break src.cache.inmemory.writeToStore.
Position
Below the diagonal: src.cache.inmemory.policies uses a module listed above it, which is the healthy direction.
src.cache.inmemory.policies uses src.cache.inmemory.inMemoryCache, so a change to src.cache.inmemory.inMemoryCache can break src.cache.inmemory.policies, while a change to src.cache.inmemory.policies can't break src.cache.inmemory.inMemoryCache.
Position
Below the diagonal: src.cache.inmemory.policies uses a module listed above it, which is the healthy direction.
src.testing.internal uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.testing.internal, while a change to src.testing.internal can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.testing.internal uses a module listed above it, which is the healthy direction.
src.testing.internal uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.testing.internal, while a change to src.testing.internal can't break src.core.ApolloClient.
Position
Below the diagonal: src.testing.internal uses a module listed above it, which is the healthy direction.
src.testing.internal uses src.testing.react.MockedProvider, so a change to src.testing.react.MockedProvider can break src.testing.internal, while a change to src.testing.internal can't break src.testing.react.MockedProvider.
Position
Below the diagonal: src.testing.internal uses a module listed above it, which is the healthy direction.
src.utilities.internal uses config.schema_package_json, so a change to config.schema_package_json can break src.utilities.internal, while a change to src.utilities.internal can't break config.schema_package_json.
Position
Below the diagonal: src.utilities.internal uses a module listed above it, which is the healthy direction.
src.utilities.internal uses src.utilities.graphql.storeUtils, so a change to src.utilities.graphql.storeUtils can break src.utilities.internal, while a change to src.utilities.internal can't break src.utilities.graphql.storeUtils.
Position
Below the diagonal: src.utilities.internal uses a module listed above it, which is the healthy direction.
src.utilities.internal uses src.utilities.internal.types.FragmentMap, so a change to src.utilities.internal.types.FragmentMap can break src.utilities.internal, while a change to src.utilities.internal can't break src.utilities.internal.types.FragmentMap.
Position
Below the diagonal: src.utilities.internal uses a module listed above it, which is the healthy direction.
src.utilities.internal uses src.cache.core.types.Cache, so a change to src.cache.core.types.Cache can break src.utilities.internal, while a change to src.utilities.internal can't break src.cache.core.types.Cache.
Position
Below the diagonal: src.utilities.internal uses a module listed above it, which is the healthy direction.
src.utilities.internal uses src.cache.inmemory.types, so a change to src.cache.inmemory.types can break src.utilities.internal, while a change to src.utilities.internal can't break src.cache.inmemory.types.
Position
Below the diagonal: src.utilities.internal uses a module listed above it, which is the healthy direction.
src.utilities.internal uses src.link.core.ApolloLink, so a change to src.link.core.ApolloLink can break src.utilities.internal, while a change to src.utilities.internal can't break src.link.core.ApolloLink.
Position
Below the diagonal: src.utilities.internal uses a module listed above it, which is the healthy direction.
src.utilities.internal uses src.core.ApolloClient, so a change to src.core.ApolloClient can break src.utilities.internal, while a change to src.utilities.internal can't break src.core.ApolloClient.
Position
Below the diagonal: src.utilities.internal uses a module listed above it, which is the healthy direction.
src.utilities.internal uses src.cache.core.cache, so a change to src.cache.core.cache can break src.utilities.internal, while a change to src.utilities.internal can't break src.cache.core.cache.
Position
Below the diagonal: src.utilities.internal uses a module listed above it, which is the healthy direction.
src.utilities.internal uses src.cache.inmemory.inMemoryCache, so a change to src.cache.inmemory.inMemoryCache can break src.utilities.internal, while a change to src.utilities.internal can't break src.cache.inmemory.inMemoryCache.
Position
Below the diagonal: src.utilities.internal uses a module listed above it, which is the healthy direction.
src.cache.inmemory uses src.utilities.graphql.storeUtils, so a change to src.utilities.graphql.storeUtils can break src.cache.inmemory, while a change to src.cache.inmemory can't break src.utilities.graphql.storeUtils.
Position
Below the diagonal: src.cache.inmemory uses a module listed above it, which is the healthy direction.
src.cache.inmemory uses src.utilities.internal.types.FragmentMap, so a change to src.utilities.internal.types.FragmentMap can break src.cache.inmemory, while a change to src.cache.inmemory can't break src.utilities.internal.types.FragmentMap.
Position
Below the diagonal: src.cache.inmemory uses a module listed above it, which is the healthy direction.
src.cache.inmemory uses src.cache.inmemory.types, so a change to src.cache.inmemory.types can break src.cache.inmemory, while a change to src.cache.inmemory can't break src.cache.inmemory.types.
Position
Below the diagonal: src.cache.inmemory uses a module listed above it, which is the healthy direction.
src.cache.inmemory uses src.cache.inmemory.readFromStore, so a change to src.cache.inmemory.readFromStore can break src.cache.inmemory, while a change to src.cache.inmemory can't break src.cache.inmemory.readFromStore.
Position
Below the diagonal: src.cache.inmemory uses a module listed above it, which is the healthy direction.
src.cache.inmemory uses src.cache.core.cache, so a change to src.cache.core.cache can break src.cache.inmemory, while a change to src.cache.inmemory can't break src.cache.core.cache.
Position
Below the diagonal: src.cache.inmemory uses a module listed above it, which is the healthy direction.
src.cache.inmemory uses src.cache.inmemory.policies, so a change to src.cache.inmemory.policies can break src.cache.inmemory, while a change to src.cache.inmemory can't break src.cache.inmemory.policies.
Position
Below the diagonal: src.cache.inmemory uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 64.9 · Adequate · gated by D2 ·
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
54
High / Critical
A05:2025 — Injection
17
High / Critical
Roadmap
Top priorities: Resolve the 11 Banned license finding(s) in License Compliance — start with pnpm-lock.yaml (11); Resolve the 36 Deprecated finding(s) in Dependency Hygiene — start with pnpm-lock.yaml (32), REDACTED (4); Adopt pino (or winston) and log at meaningful points in the services you run.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 11 Banned license finding(s) in License Compliance — start with pnpm-lock.yaml (11).
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.
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.
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.
Test Quality: No assertions (empty test): allows resolvers of anything with no generic
src/core/QueryInfo.ts
6.0
Mixed
Explicit Debt: TodoComment
src/cache/inmemory/writeToStore.ts
6.0
Mixed
Explicit Debt: TodoComment
src/core/QueryManager.ts
6.0
Mixed
Explicit Debt: TodoComment
src/core/ObservableQuery.ts
6.0
Mixed
Explicit Debt: HackComment
src/cache/inmemory/policies.ts
6.0
Mixed
Explicit Debt: TodoComment
src/link/http/BaseHttpLink.ts
6.0
Mixed
Explicit Debt: XxxComment
src/react/hooks/useQuery.ts
6.0
Mixed
Explicit Debt: TodoComment
src/react/hooks/useSuspenseQuery.ts
6.0
Mixed
Explicit Debt: TodoComment
src/core/__tests__/ObservableQuery.ts
6.0
Mixed
Explicit Debt: TodoComment
src/core/__tests__/ApolloClient/general.test.ts
6.0
Mixed
Explicit Debt: TodoComment
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 — 67
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 — 655
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 — 139
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 66 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 66 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 828 of 861 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the jest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (npm error code EBADDEVENGINES), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the node:test suite in eslint-local-rules/ was NOT MEASURED: the dependency install for eslint-local-rules/ failed in the analyzer sandbox (npm error code EBADDEVENGINES), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in scripts/codemods/ac3-to-ac4/ was NOT MEASURED: the dependency install for scripts/codemods/ac3-to-ac4/ failed in the analyzer sandbox (npm error code EBADDEVENGINES), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `config/apiExtractor.ts`, `config/babel.ts`, `config/build.ts`, `config/precheck.ts`, `config/version.ts`, … (+35 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.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run start` in integration-tests/cra5/) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "TS7031: Binding element 'id' implicitly has an 'any' type. / 58 | return data ? / 59 | <ul> / > 60 | {data?.products.map(({ id, title }) => <li key={id}>{title}</li>)} / | ^^ / 61 | </ul> / 62 | : <>loading</>; / 63 | } / ERROR in src/App.tsx:60:36 / TS7031: Binding element 'title' implicitly has an 'any' type. / 58 | return data ? / 59 | <ul> / > 60 | {data?.products.map(({ id, title }) => <li key={id}>{title}</li>)} / | ^^^^^ / 61 | </ul> / 62 | : <>loading</>; / 63 | }" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start` in integration-tests/cra5/) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "TS7031: Binding element 'id' implicitly has an 'any' type. / 58 | return data ? / 59 | <ul> / > 60 | {data?.products.map(({ id, title }) => <li key={id}>{title}</li>)} / | ^^ / 61 | </ul> / 62 | : <>loading</>; / 63 | } / ERROR in src/App.tsx:60:36 / TS7031: Binding element 'title' implicitly has an 'any' type. / 58 | return data ? / 59 | <ul> / > 60 | {data?.products.map(({ id, title }) => <li key={id}>{title}</li>)} / | ^^^^^ / 61 | </ul> / 62 | : <>loading</>; / 63 | }" No runtime evidence was gathered.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 44 further occurrence(s) are not listed individually; the score already reflects all 84.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
R5 Dependency Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm outdated` failed and answered nothing (EBADDEVENGINES: The developer of this package has specified the following through devEngines
Invalid engine "runtime"
Invalid semver version ">=24" does not match "v22.13.0" for "runtime"); nothing here is a statement about the repository.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 406 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic 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: 8 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 41 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 46 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with LocalState.resolveClientField (cyclomatic 40), StoreReader.execSelectionSetImpl (cyclomatic 39), findReferences.findReferences (cyclomatic 38). — 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 46 together lifts Cyclomatic Complexity from 6.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 53 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with EntityStore.modify (cognitive 110), LocalState.resolveClientField (cognitive 74), StoreReader.execSelectionSetImpl (cognitive 68). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 3.0 to about 4.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 15 FileTooLong finding(s) in God Classes — start with ObservableQuery.ts, QueryManager.ts, ApolloClient.ts. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 7 MethodTooLong finding(s) in God Classes — start with QueryManager.ts (2), ObservableQuery.ts, LocalState.ts. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 FunctionTooLong finding(s) in God Classes — start with processInvariants.ts, getAllExports.ts, removeDirectivesFromDocument.ts. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
5 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 4 of the 5 (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).
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.
D10 · Test Quality9.2 / 10Adequategated by 5 critical findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
67 skipped, 129 zero-assertion, 2 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3983 tests.
No assertions (empty test): allows resolvers of anything with no generic · ×5src/local-state/__tests__/LocalState/types.test.ts:13
No assertions: returns string | undefined without fallback · ×124src/utilities/internal/__tests__/getOperationName.test.ts:58
Skipped test: type tests · ×67src/utilities/internal/types/__tests__/HTK.test.ts:25
Fixed-sleep synchronisation: %s: AbortSignal times out during render - can be resumed with `resumeAndPrerender` · ×2src/react/ssr/__tests__/prerenderStatic.test.tsx:301
Mock-dominated test: multiple subscribers will trigger multiple requestssrc/link/retry/__tests__/retryLink.ts:104
What to do
Resolve the 5 No assertions (empty test) finding(s) in Test Quality — start with types.test.ts (2), cache.ts, optimistic.ts. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 124 No assertions finding(s) in Test Quality — start with types.test.ts (27), useSubscription.test.tsx (14), useSuspenseFragment.test.tsx (14). — One of this dimension's main actionable groups (124 warning-level).
Resolve the 67 Skipped test finding(s) in Test Quality — start with stream.test.ts (30), defer.test.ts (26), ObservableQuery.ts (2). — One of this dimension's main actionable groups (67 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in the repository root; node:test via `npm ci --ignore-scripts` in eslint-local-rules/; its own test command under node's V8 coverage via `pnpm install --frozen-lockfile --ignore-scripts` in integration-tests/node/ (1 tests); vitest via `npm ci --ignore-scripts` in scripts/codemods/ac3-to-ac4/; node:test via `npm ci --ignore-scripts` in scripts/memory/ (1 tests)): measured (0 flaky).
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
25 outdated direct production npm dependency(ies) of 31 graded, 1 pinning defect(s), across 17 package.json (13 of them the product) and 4 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 3 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: next · ×5integration-tests/next/package.json:23
Resolve the 36 Deprecated finding(s) in Dependency Hygiene — start with pnpm-lock.yaml (32), REDACTED (4). — One of this dimension's main actionable groups (36 recommendation-level).
Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with package.json (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Floating npm dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
11 of 1379 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1379 package(s) this repository's committed lockfile installs for a consumer — its 33 production, optional and peer dependency(ies), across 13 product package.json manifest(s), and everything those install in turn. Its 151 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. Third-party code that ships WITHOUT a manifest entry was read too: 0 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 0 use a banned licence. 1 vendored, copied-in or compiled component(s) state no licence this pass can read — missing data, not charged. This repository publishes itself under ISC / MIT / UNLICENSED, which is its own choice and is not judged here.
Resolve the 11 Banned license finding(s) in License Compliance — start with pnpm-lock.yaml (11). — One of this dimension's main actionable groups (11 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with QueryInfo.ts, writeToStore.ts, readFromStore.ts. — One of this dimension's main actionable groups (3 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.6 / 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.
27 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is integration-tests/type-tests/signatures/modern/useMutation.ts. Counted over 189 of the 508 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.
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.
112 deducted task-comment markers across 80019 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 102 TodoComment finding(s) in Explicit Debt — start with useQuery.test.tsx (19), ObservableQuery.ts (10), QueryManager.ts (5). — One of this dimension's main actionable groups (102 warning-level).
Resolve the 8 XxxComment finding(s) in Explicit Debt — start with optimistic.ts (2), BaseHttpLink.ts, BaseBatchHttpLink.ts. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with ObservableQuery.ts, entityStore.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
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.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
1 of 8 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionpackage.json:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
26 % of calls cross a namespace and 6 % go through an interface, but 79 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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).
17 finding(s): 0 critical, 14 high, 3 medium, 0 low. semgrep hit a parse error in 63 file(s) — `config/apiExtractor.ts` (line 15), `config/babel.ts` (line 25), `config/build.ts` (line 51, line 52, line 68, …), `config/precheck.ts` (line 1), `config/version.ts` (line 7), … (+58 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (12). — One of this dimension's main actionable groups (12 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 35 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (35). — One of this dimension's main actionable groups (35 issue-level).
Resolve the 11 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
4 of 189 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/utilities/policies/pagination.ts. Counted over 189 of the 508 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with useSuspenseQuery.ts, QueryManager.ts. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with index.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 7 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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`Classic` declares 18 required operations under just 1 distinct name(s): `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 1 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/react/hooks/useSuspenseQuery.ts:308
`Classic` declares 30 required operations under just 1 distinct name(s): `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 30 separate responsibilities: a caller binds to 1 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 30 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/react/hooks/useBackgroundQuery.ts:302
What to do
Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`verifyVersion` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — config/version.ts:44
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×39) — src/__tests__/ApolloClient.ts:3153, src/__tests__/client.ts:795, src/__tests__/client.ts:852, …
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 475 JavaScript/TypeScript production file(s) this check read across 14 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 20 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/api-extractor.yml:2
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.writeFileSync` in `processInvariants` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — config/processInvariants.ts:77
`readFileSync` in `transformStep` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — config/react-compiler.ts:23
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety9.9 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
7 duplicated blocks under src/ have copies in at least two of the sibling directories cache, core, incremental, link, masking, react (+1 more sibling(s) not listed) — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/cache/core/cache.ts:571
src/react/hooks/useBackgroundQuery.ts:60 · src/react/hooks/useSuspenseQuery.ts:69 — the two spans are one implementation copied and then locally edited — 1992 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. — src/react/hooks/useBackgroundQuery.ts:60
src/react/hooks/useLazyQuery.ts:49 · src/react/hooks/useQuery.ts:66 — the two spans are one implementation copied and then locally edited — 800 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. — src/react/hooks/useLazyQuery.ts:49
src/react/hooks/useLazyQuery.ts:245 · src/react/hooks/useLoadableQuery.ts:118 — the two spans are one implementation copied and then locally edited — 568 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. — src/react/hooks/useLazyQuery.ts:245
src/react/hooks/useLoadableQuery.ts:213 · src/react/hooks/useSuspenseQuery.ts:302 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/react/hooks/useLoadableQuery.ts:213
src/react/hooks/useQuery.ts:215 · src/react/hooks/useSuspenseQuery.ts:170 — the two spans are one implementation copied and then locally edited — 237 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. — src/react/hooks/useQuery.ts:215
src/testing/internal/schemas/friendList.graphql17Alpha2.ts:16 · src/testing/internal/schemas/friendList.graphql17Alpha9.ts:19 — 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. — src/testing/internal/schemas/friendList.graphql17Alpha2.ts:16
src/react/hooks/useFragment.ts:77 · src/react/hooks/useSuspenseFragment.ts:72 — the two spans are one implementation copied and then locally edited — 270 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. — src/react/hooks/useFragment.ts:77
src/cache/core/cache.ts:571 · src/core/ApolloClient.ts:1582 — 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. — src/cache/core/cache.ts:571
eslint-local-rules/forbid-act-in-disabled-act-environment.ts:3 · eslint-local-rules/require-disable-act-environment.ts:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — eslint-local-rules/forbid-act-in-disabled-act-environment.ts:3
src/core/ApolloClient.ts:1509 · src/core/ApolloClient.ts:1666 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/core/ApolloClient.ts:1509
src/testing/matchers/toComplete.ts:8 · src/testing/matchers/toEmitNext.ts:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/testing/matchers/toComplete.ts:8
src/testing/matchers/toEmitError.ts:49 · src/testing/matchers/toEmitTypedValue.ts:57 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/testing/matchers/toEmitError.ts:49
src/testing/internal/multipart/mockDefer20220824.ts:9 · src/testing/internal/multipart/mockDeferStreamGraphql17Alpha9.ts:8 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/testing/internal/multipart/mockDefer20220824.ts:9
src/testing/matchers/toEmitTypedValue.ts:40 · src/testing/matchers/toHaveFragmentWatchesOn.ts:74 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/testing/matchers/toEmitTypedValue.ts:40
src/link/http/BaseHttpLink.ts:366 · src/utilities/subscriptions/relay/index.ts:38 — the two spans are one implementation copied and then locally edited — 116 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. — src/link/http/BaseHttpLink.ts:366
src/core/ApolloClient.ts:354 · src/core/ApolloClient.ts:415 — 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. — src/core/ApolloClient.ts:354
src/core/ApolloClient.ts:665 · src/core/ObservableQuery.ts:148 — the two spans are one implementation copied and then locally edited — 112 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. — src/core/ApolloClient.ts:665
src/local-state/LocalState.ts:381 · src/local-state/LocalState.ts:462 — all 2 copies are in the same file, 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. — src/local-state/LocalState.ts:381
src/core/ApolloClient.ts:462 · src/react/query-preloader/createQueryPreloader.ts:140 — 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. — src/core/ApolloClient.ts:462
src/cache/core/cache.ts:355 · src/cache/inmemory/inMemoryCache.ts:243 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/cache/core/cache.ts:355
src/incremental/handlers/defer20220824.ts:190 · src/incremental/handlers/graphql17Alpha9.ts:398 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/incremental/handlers/defer20220824.ts:190
src/react/internal/cache/FragmentReference.ts:91 · src/react/internal/cache/QueryReference.ts:293 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/react/internal/cache/FragmentReference.ts:91
src/utilities/internal/caches.ts:32 · src/utilities/internal/caches.ts:67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/utilities/internal/caches.ts:32
config/deprecateInternals.ts:6 · config/preserveTsIgnore.ts:23 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — config/deprecateInternals.ts:6
src/cache/core/cache.ts:1004 · src/cache/core/cache.ts:1022 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/cache/core/cache.ts:1004
src/config/jest/areCombinedGraphQLErrorsEqual.ts:1 · src/config/jest/areLocalStateErrorsEqual.ts:1 · src/config/jest/areServerErrorsEqual.ts:1 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/config/jest/areCombinedGraphQLErrorsEqual.ts:1
src/react/internal/cache/FragmentReference.ts:50 · src/react/internal/cache/QueryReference.ts:223 — the two spans are one implementation copied and then locally edited — 92 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. — src/react/internal/cache/FragmentReference.ts:50
src/incremental/handlers/defer20220824.ts:83 · src/incremental/handlers/graphql17Alpha9.ts:346 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/incremental/handlers/defer20220824.ts:83
src/link/batch-http/BaseBatchHttpLink.ts:98 · src/link/http/BaseHttpLink.ts:269 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/link/batch-http/BaseBatchHttpLink.ts:98
scripts/codemods/data-masking/unmask.ts:125 · src/core/QueryManager.ts:1869 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/codemods/data-masking/unmask.ts:125
src/cache/core/cache.ts:531 · src/cache/core/cache.ts:892 · src/core/ApolloClient.ts:1525 · src/core/ApolloClient.ts:1687 — the 4 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/cache/core/cache.ts:531
config/compileTs.ts:64 · config/compileTs.ts:79 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — config/compileTs.ts:64
config/listImports.ts:14 · scripts/codemods/ac3-to-ac4/src/devLoader.js:4 — 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. — config/listImports.ts:14
src/cache/inmemory/readFromStore.ts:827 · src/utilities/internal/coerceScalarFieldsToParsed.ts:98 — the two spans are one implementation copied and then locally edited — 87 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. — src/cache/inmemory/readFromStore.ts:827
src/react/hooks/useQueryRefHandlers.ts:71 · src/react/hooks/useReadQuery.ts:93 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/react/hooks/useQueryRefHandlers.ts:71
src/testing/internal/incremental/executeSchemaGraphQL17Alpha2.ts:24 · src/testing/internal/incremental/executeSchemaGraphQL17Alpha9.ts:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/testing/internal/incremental/executeSchemaGraphQL17Alpha2.ts:24
src/utilities/internal/isDeferredFragment.ts:12 · src/utilities/internal/isStreamField.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/utilities/internal/isDeferredFragment.ts:12
config/compileTs.ts:89 · config/compileTs.ts:100 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — config/compileTs.ts:89
config/deprecateInternals.ts:10 · config/inlineInheritDoc.ts:184 · config/preserveTsIgnore.ts:27 — 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. — config/deprecateInternals.ts:10
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
config/helpers.ts:7 imports @microsoft/api-extractor/lib/generators/ApiModelGenerator, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — config/helpers.ts:7
config/helpers.ts:14 imports @microsoft/api-extractor-model/lib/items/ApiItem, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — config/helpers.ts:14
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 53 and cognitive complexity 52; 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. — integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:1367
(anonymous) has cyclomatic complexity 36 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — integration-tests/type-tests/signatures/modern/useSuspenseQuery.ts:1366
maskSelectionSet has cyclomatic complexity 35 and cognitive complexity 66; 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. — src/masking/maskDefinition.ts:52
resolveClientField has cyclomatic complexity 33 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/local-state/LocalState.ts:672
(anonymous) has cyclomatic complexity 33 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 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. — scripts/codemods/ac3-to-ac4/src/util/findReferences.ts:25
(anonymous) has cyclomatic complexity 32 and cognitive complexity 77; 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. — src/cache/inmemory/readFromStore.ts:517
(anonymous) has cyclomatic complexity 32 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/core/ObservableQuery.ts:2073
collectUsageExamples has cyclomatic complexity 31 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/codemods/ac3-to-ac4/src/util/getAllExports.ts:131
merge has cyclomatic complexity 29 and cognitive complexity 44; 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. — src/utilities/policies/pagination.ts:157
(anonymous) has cyclomatic complexity 29 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/codemods/ac3-to-ac4/src/util/handleIdentiferRename.ts:32
(anonymous) has cyclomatic complexity 29 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts:1168
(top-level) has cyclomatic complexity 25 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 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. — src/incremental/internal/types.ts:1
(anonymous) has cyclomatic complexity 22 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/cache/inmemory/entityStore.ts:257
(anonymous) has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/local-state/LocalState.ts:518
(anonymous) has cyclomatic complexity 21 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. — integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:1107
(anonymous) has cyclomatic complexity 20 and cognitive complexity 38; 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. — src/cache/inmemory/policies.ts:578
diffQueryAgainstStore has cyclomatic complexity 20 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — src/cache/inmemory/readFromStore.ts:318
(anonymous) has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:691
markMutationResult has cyclomatic complexity 19 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 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. — src/core/QueryInfo.ts:315
processSelectionSet has cyclomatic complexity 17 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. — src/cache/inmemory/writeToStore.ts:276
(anonymous) has cyclomatic complexity 17 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 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. (×2) — integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:873, integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:990
fragmentMatches has cyclomatic complexity 16 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/cache/inmemory/policies.ts:807
(anonymous) has cyclomatic complexity 16 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. — src/utilities/internal/equalByQuery.ts:64
(anonymous) has cyclomatic complexity 16 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. — src/cache/inmemory/readFromStore.ts:838
consumeMultipartBody has cyclomatic complexity 15 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:22
merge 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. — src/cache/inmemory/entityStore.ts:123
(anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. (×4) — integration-tests/type-tests/signatures/classic/createQueryPreloader.ts:877, integration-tests/type-tests/signatures/classic/useLoadableQuery.ts:652, integration-tests/type-tests/signatures/modern/useBackgroundQuery.ts:1168, …
identify has cyclomatic complexity 15 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. — src/cache/inmemory/policies.ts:439
mergeObjects 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. — src/cache/inmemory/policies.ts:1279
(anonymous) 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. — src/core/ObservableQuery.ts:510
useSubscription has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/react/hooks/useSubscription.ts:228
applyMerges has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/cache/inmemory/writeToStore.ts:699
(anonymous) has cyclomatic complexity 13 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 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. — src/cache/inmemory/writeToStore.ts:610
connectToDevTools has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/core/ApolloClient.ts:1188
(anonymous) has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts:178, integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts:325
Do you agree with this assessment?
R3 · Large Files5.7 / 10Adequate✓ 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.
integration-tests/type-tests/signatures/modern/useBackgroundQuery.ts has 2388 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/modern/useBackgroundQuery.ts:1
integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts has 2318 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts:1
integration-tests/type-tests/signatures/modern/useSuspenseQuery.ts has 2296 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/modern/useSuspenseQuery.ts:1
integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts has 2193 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:1
src/core/ObservableQuery.ts has 2103 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/ObservableQuery.ts:1
src/core/ApolloClient.ts has 1883 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/ApolloClient.ts:1
src/core/QueryManager.ts has 1703 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/QueryManager.ts:1
integration-tests/type-tests/signatures/modern/useMutation.ts has 1503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/modern/useMutation.ts:1
integration-tests/type-tests/signatures/classic/useMutation.ts has 1304 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/classic/useMutation.ts:1
integration-tests/type-tests/signatures/classic/useMutation.explicit-generics.ts has 1286 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/classic/useMutation.explicit-generics.ts:1
src/cache/inmemory/policies.ts has 1180 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/cache/inmemory/policies.ts:1
integration-tests/type-tests/signatures/modern/createQueryPreloader.ts has 1144 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/modern/createQueryPreloader.ts:1
src/local-state/LocalState.ts has 1072 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/local-state/LocalState.ts:1
src/cache/inmemory/readFromStore.ts has 1035 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/cache/inmemory/readFromStore.ts:1
integration-tests/type-tests/signatures/classic/createQueryPreloader.ts has 1000 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/classic/createQueryPreloader.ts:1
src/cache/core/cache.ts has 985 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/cache/core/cache.ts:1
integration-tests/type-tests/signatures/modern/useLoadableQuery.ts has 925 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/modern/useLoadableQuery.ts:1
src/react/hooks/useBackgroundQuery.ts has 902 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/react/hooks/useBackgroundQuery.ts:1
src/react/hooks/useQuery.ts has 899 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/react/hooks/useQuery.ts:1
src/cache/inmemory/entityStore.ts has 894 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/cache/inmemory/entityStore.ts:1
src/cache/inmemory/writeToStore.ts has 888 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/cache/inmemory/writeToStore.ts:1
scripts/codemods/ac3-to-ac4/src/renames.ts has 836 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/codemods/ac3-to-ac4/src/renames.ts:1
integration-tests/type-tests/signatures/classic/useLoadableQuery.ts has 821 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/classic/useLoadableQuery.ts:1
src/react/hooks/useSuspenseQuery.ts has 818 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/react/hooks/useSuspenseQuery.ts:1
src/cache/inmemory/inMemoryCache.ts has 802 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/cache/inmemory/inMemoryCache.ts:1
codegen/local-state/visitor.ts has 635 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — codegen/local-state/visitor.ts:1
src/v4-migration.ts has 635 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/v4-migration.ts:1
integration-tests/type-tests/signatures/modern/useQuery.ts has 627 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/modern/useQuery.ts:1
src/react/hooks/useLazyQuery.ts has 617 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/react/hooks/useLazyQuery.ts:1
src/core/QueryInfo.ts has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/QueryInfo.ts:1
src/react/hooks/useMutation.ts has 595 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/react/hooks/useMutation.ts:1
integration-tests/type-tests/signatures/modern/useLazyQuery.ts has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/modern/useLazyQuery.ts:1
integration-tests/type-tests/signatures/classic/useQuery.ts has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/classic/useQuery.ts:1
src/react/internal/cache/QueryReference.ts has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/react/internal/cache/QueryReference.ts:1
scripts/codemods/ac3-to-ac4/src/apolloClientInitialization.ts has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/codemods/ac3-to-ac4/src/apolloClientInitialization.ts:1
src/react/hooks/useLoadableQuery.ts has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/react/hooks/useLoadableQuery.ts:1
src/link/persisted-queries/index.ts has 481 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/link/persisted-queries/index.ts:1
integration-tests/type-tests/signatures/classic/useLazyQuery.ts has 465 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration-tests/type-tests/signatures/classic/useLazyQuery.ts:1
src/link/core/ApolloLink.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. — src/link/core/ApolloLink.ts:1
src/react/query-preloader/createQueryPreloader.ts has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/react/query-preloader/createQueryPreloader.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 Coverage9.1 / 10Exemplary✓ 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. (×28) — config/processInvariants.ts:1, scripts/codemods/ac3-to-ac4/src/util/getAllExports.ts:1, config/helpers.ts: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 package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
4 file(s) (~36 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. — integration-tests/browser-esm
2 file(s) (~48 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. — integration-tests/shared
64 file(s) (~34883 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. — integration-tests/type-tests
1 file(s) (~126 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. — scripts/codemods/ac2-to-ac3
1 file(s) (~166 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. — scripts/codemods/data-masking
1 file(s) (~266 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. — scripts/memory
Unreachable from the 106 application, 21 tooling and 369 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (106 application, 21 tooling, 369 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 (×3) — config/prettier/format-jsdoc.js, scripts/codemods/misc/mockLinkRejection.ts, config/prettier/test.ts
Nothing imports this binding — it is safe to review for removal. — config/helpers.ts:28
No runtime consumer imports this binding — the only demand on it comes from a type-position import of its module, which asks for the module's type surface rather than for this name. If the value is genuinely unneeded, remove it; if a consumer needs only its TYPE, export that type (e.g. `export type X = typeof x`) and drop the value. A value export — a const, a function, a class — cannot itself be rewritten as `export type`. — src/masking/PreserveTypes.ts:3
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — eslint-local-rules/require-disable-act-environment.ts:72
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. — config/bundlesize.ts:5
Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — src/config/jest/resolver.ts:4
Declared in the root 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. (×3) — package.json:167, package.json:182, package.json:183
Declared in integration-tests/codegen/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. — integration-tests/codegen/package.json:12
Declared in integration-tests/node/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. — integration-tests/node/package.json:18
Every import is type-only — move it to devDependencies. — src/__tests__/ApolloClient.ts:1
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document1.8 / 10Critical✓ 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.
`merge` is exported and takes `target: any` from its caller, and it calls itself at line 67 (`this.merge`) with a piece of `target` — and nowhere in `merge` 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 `merge` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/utilities/internal/DeepMerger.ts:67
`getSerializableProperties` is exported and takes `obj: unknown` from its caller, and it calls itself at line 18 (`getSerializableProperties`) with a piece of `obj` (and at line 39) — and nowhere in `getSerializableProperties` 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 `getSerializableProperties` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/testing/matchers/utils/getSerializableProperties.ts:18
`maskDefinition` is exported, takes a document from its caller (line 24) and hands it to `maskSelectionSet`, which calls itself at line 69 (`maskSelectionSet`) with a piece of `data` (and at line 106) — and nowhere in `maskSelectionSet` 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 `maskSelectionSet` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/masking/maskDefinition.ts:69
`selectionSetMatchesResult` is exported and takes `result: Record<string, any>` from its caller, and it calls itself at line 104 (`selectionSetMatchesResult`) with a piece of `result` (and at line 112) — and nowhere in `selectionSetMatchesResult` 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 `selectionSetMatchesResult` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/cache/inmemory/helpers.ts:104
`getSpecifierPaths` is exported and takes `spec: KeySpecifier` from its caller, and it calls itself at line 230 (`getSpecifierPaths`) with a piece of `spec` — and nowhere in `getSpecifierPaths` 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 `getSpecifierPaths` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/cache/inmemory/key-extractor.ts:230
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether 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.
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.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×6) — src/utilities/internal/createRejectedPromise.ts:8, src/utilities/internal/preventUnhandledRejection.ts:2, src/react/query-preloader/createQueryPreloader.ts:462, …
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) — src/utilities/internal/globals/maybe.ts:4, src/link/persisted-queries/index.ts:448, src/config/jest/resolver.ts:34, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
14/20 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.
~2.2 `!` null assertions per 1k TypeScript source lines — 117 assertion(s) across the 53484 source line(s) of the 397 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: src/core/ObservableQuery.ts (12), codegen/local-state/visitor.ts (11), config/apiExtractor.ts (8). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
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.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 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 — 59 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 — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (0 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start` in integration-tests/cra5/) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "TS7031: Binding element 'id' implicitly has an 'any' type. / 58 | return data ? / 59 | <ul> / > 60 | {data?.products.map(({ id, title }) => <li key={id}>{title}</li>)} / | ^^ / 61 | </ul> / 62 | : <>loading</>; / 63 | } / ERROR in src/App.tsx:60:36 / TS7031: Binding element 'title' implicitly has an 'any' type. / 58 | return data ? / 59 | <ul> / > 60 | {data?.products.map(({ id, title }) => <li key={id}>{title}</li>)} / | ^^^^^ / 61 | </ul> / 62 | : <>loading</>; / 63 | }" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
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.
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 does not read html yet; not measured.
D22 Internal API Consistency — N/A — too few peer members to establish a convention across 2 exposed TypeScript types.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 40 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D4 Code Duplication — This repository's production source (.cts, .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: the JavaScript/TypeScript half could not be measured — the its own test command under node's V8 coverage suite in integration-tests/node/ ran and not one test passed (# SyntaxError: Unexpected token 'export'), so the coverage report describes the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — `npm outdated` failed (EBADDEVENGINES: The developer of this package has specified the following through devEngines
Invalid engine "runtime"
Invalid semver version ">=24" does not match "v22.13.0" for "runtime") — dependency freshness not measured; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — Not assessed: 406 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — 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
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Banned license: @img/sharp-libvips-darwin-arm64 integration-tests/pnpm-lock.yaml:1941— `@img/sharp-libvips-darwin-arm64` 1.0.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-darwin-x64 integration-tests/pnpm-lock.yaml:1946— `@img/sharp-libvips-darwin-x64` 1.0.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm integration-tests/pnpm-lock.yaml:1957— `@img/sharp-libvips-linux-arm` 1.0.5 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm64 integration-tests/pnpm-lock.yaml:1951— `@img/sharp-libvips-linux-arm64` 1.0.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-s390x integration-tests/pnpm-lock.yaml:1963— `@img/sharp-libvips-linux-s390x` 1.0.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-x64 integration-tests/pnpm-lock.yaml:1969— `@img/sharp-libvips-linux-x64` 1.0.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-arm64 integration-tests/pnpm-lock.yaml:1975— `@img/sharp-libvips-linuxmusl-arm64` 1.0.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-x64 integration-tests/pnpm-lock.yaml:1981— `@img/sharp-libvips-linuxmusl-x64` 1.0.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-wasm32 integration-tests/pnpm-lock.yaml:2029— `@img/sharp-wasm32` 0.33.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later AND MIT`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-ia32 integration-tests/pnpm-lock.yaml:2034— `@img/sharp-win32-ia32` 0.33.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-x64 integration-tests/pnpm-lock.yaml:2040— `@img/sharp-win32-x64` 0.33.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
D10 · Test Quality· No assertions (empty test) · ×5
No assertions (empty test): allows resolvers of anything with no generic src/local-state/__tests__/LocalState/types.test.ts:13— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): narrows context provided to handler per-source src/core/__tests__/RefetchEventManager/types.test.ts:23— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): allows undefined as return value src/cache/core/__tests__/cache.ts:552— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): allows IgnoreModifier as return value when inferring from a TypedDocumentNode mutation src/__tests__/optimistic.ts:1000— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): can refetch no-cache queries src/__tests__/refetchQueries.ts:1093— Test method has an empty body — it asserts nothing and exercises no code.
No assertions: returns string | undefined without fallback src/utilities/internal/__tests__/getOperationName.test.ts:58— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: returns string | undefined with undefined fallback src/utilities/internal/__tests__/getOperationName.test.ts:62— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: returns string with string fallback src/utilities/internal/__tests__/getOperationName.test.ts:68— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: returns string | null with null fallback src/utilities/internal/__tests__/getOperationName.test.ts:72— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not allow values other than string, null, undefined src/utilities/internal/__tests__/getOperationName.test.ts:76— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should not require a result or error when delay equals Infinity src/testing/core/mocking/__tests__/mockLink.ts:36— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: covariant behaviour: `MockLink.MockedResponses<X,Y>` should be assignable to `MockLink.MockedResponse` src/testing/core/mocking/__tests__/mockLink.ts:1803— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: returned 'data' can be any object with untyped response src/testing/core/mocking/__tests__/mockLink.ts:1868— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: can't return output that doesn't match TData src/testing/core/mocking/__tests__/mockLink.ts:1878— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: can't use input variables that don't exist in TVariables src/testing/core/mocking/__tests__/mockLink.ts:1889— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: passing as prop src/react/internal/cache/__tests__/QueryReference.test.tsx:36— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: QueryRef.ForQuery src/react/internal/cache/__tests__/QueryReference.test.tsx:249— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: returns data on first render src/react/hooks/__tests__/useFragment.test.tsx:365— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: NoInfer prevents adding arbitrary additional variables src/react/hooks/__tests__/useFragment.test.tsx:2727— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: variables are optional and can be anything with an untyped DocumentNode src/react/hooks/__tests__/useFragment.test.tsx:2740— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: variables are optional and can be anything with unspecified TVariables on a TypedDocumentNode src/react/hooks/__tests__/useFragment.test.tsx:2749— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: variables are optional and can be anything with OperationVariables on a TypedDocumentNode src/react/hooks/__tests__/useFragment.test.tsx:2758— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: variables are optional when TVariables are empty src/react/hooks/__tests__/useFragment.test.tsx:2770— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: is invalid with TVariables as `never` src/react/hooks/__tests__/useFragment.test.tsx:2782— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: optional variables are optional to useFragment src/react/hooks/__tests__/useFragment.test.tsx:2793— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: enforces required variables when TVariables includes required variables src/react/hooks/__tests__/useFragment.test.tsx:2819— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: requires variables with mixed TVariables src/react/hooks/__tests__/useFragment.test.tsx:2847— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: UseFragmentOptions interface shape src/react/hooks/__tests__/useFragment.test.tsx:2898— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not cause unhandled rejections src/react/hooks/__tests__/useMutation.test.tsx:513— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: refetchQueries should work with BatchHttpLink src/react/hooks/__tests__/useMutation.test.tsx:3842— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
TodoComment src/react/internal/cache/QueryReference.ts:414— // TODO: This can likely be removed once — 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 src/react/hooks/useBackgroundQuery.ts:973— // TODO: The internalQueryRef doesn't have TVariables' type information so we have to cast it here — 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 src/react/hooks/useLoadableQuery.ts:488— // TODO: The internalQueryRef doesn't have TVariables' type information so we have to cast it here — 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 src/react/hooks/useQueryRefHandlers.ts:140— // TODO: The internalQueryRef doesn't have TVariables' type information so we have to cast it here — 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 src/react/hooks/useSuspenseQuery.ts:814— // TODO: The internalQueryRef doesn't have TVariables' type information so we have to cast it here — 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 src/react/hooks/useFragment.ts:91— // TODO: Update this to return `null` when there is no data returned from the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/react/hooks/useLazyQuery.ts:513— // TODO: Revisit after we have RxJS in place. We should be able to use — 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 src/react/hooks/useQuery.ts:609— // TODO: check if we need a similar check in other hooks — 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 src/react/hooks/useQuery.ts:641— // TODO: check if we need a similar check in other hooks — 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 src/react/hooks/useSyncExternalStore.ts:123— // TODO: Because there is no cross-renderer API for batching updates, it's — 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 src/react/hooks/__tests__/useBackgroundQuery.test.tsx:4192— // @ts-ignore TODO: Determine how to handle cache writes with masked — 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 src/react/hooks/__tests__/useBackgroundQuery.test.tsx:4313— // @ts-ignore TODO: Determine how to handle cache writes with masked — 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 src/react/hooks/__tests__/useSuspenseQuery.test.tsx:8887— // @ts-ignore TODO: Determine how to handle cache writes with masked — 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 src/react/hooks/__tests__/useSuspenseQuery.test.tsx:9008— // @ts-ignore TODO: Determine how to handle cache writes with masked — 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 src/react/hooks/__tests__/useBackgroundQuery.test.tsx:5609— // TODO: We should reset the snapshot between renders to better capture — 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 src/react/hooks/__tests__/useFragment.test.tsx:1265— // TODO Figure out why Item:8 is not represented here. Likely because of — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/react/hooks/__tests__/useFragment.test.tsx:1752— // TODO: Update when https://github.com/apollographql/apollo-client/issues/12003 is fixed
TodoComment src/react/hooks/__tests__/useSuspenseFragment.test.tsx:907— // TODO: Update when https://github.com/apollographql/apollo-client/issues/12003 is fixed
TodoComment src/__tests__/dataMasking.ts:1417— // TODO: Update when https://github.com/apollographql/apollo-client/issues/12003 is fixed
TodoComment src/__tests__/dataMasking.ts:1510— // TODO: Update when https://github.com/apollographql/apollo-client/issues/12003 is fixed
TodoComment src/react/hooks/__tests__/useLazyQuery.test.tsx:936— // TODO: Determine if this hook makes sense for polling or if that should be — 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 src/react/hooks/__tests__/useLoadableQuery.test.tsx:3260— // TODO investigate: this test highlights a React render — 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 src/react/hooks/__tests__/useLoadableQuery.test.tsx:3356— // TODO investigate: this test highlights a React render — 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 src/react/hooks/__tests__/useMutation.test.tsx:116— // TODO: Remove error field when there is no error — 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 src/react/hooks/__tests__/useMutation.test.tsx:1048— // TODO: Do we want to keep this variable merge behavior? — 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.
Skipped test: type tests src/utilities/internal/types/__tests__/HTK.test.ts:25— Skipped — switched off by it.skip
Skipped test: type tests src/utilities/caching/__tests__/sizes.test.ts:5— Skipped — switched off by test.skip
Skipped test: type tests src/react/ssr/__tests__/prerenderStatic.test.tsx:825— Skipped — switched off by it.skip
Skipped test: type tests src/react/internal/cache/__tests__/QueryReference.test.tsx:35— Skipped — switched off by test.skip
Skipped test: Does not disable defer with null if argument src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:247— Skipped — switched off by it.skip
Skipped test: Does not execute deferred fragments early when not specified src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:251— Skipped — switched off by it.skip
Skipped test: Does execute deferred fragments early when specified src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:255— Skipped — switched off by it.skip
Skipped test: Can defer a fragment that is also not deferred, deferred fragment is first src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:412— Skipped — switched off by it.skip
Skipped test: Can defer a fragment that is also not deferred, non-deferred fragment is first src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:416— Skipped — switched off by it.skip
Skipped test: Does not emit empty defer fragments src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:468— Skipped — switched off by it.skip
Skipped test: Separately emits defer fragments with different labels with varying subfields that return promises src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:617— Skipped — switched off by it.skip
Skipped test: Cancels deferred fields when initial result exhibits null bubbling src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:1802— Skipped — switched off by it.skip
Skipped test: Deduplicates list fields src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:1864— Skipped — switched off by it.skip
Skipped test: Deduplicates async iterable list fields src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:1868— Skipped — switched off by it.skip
Skipped test: Deduplicates empty async iterable list fields src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:1872— Skipped — switched off by it.skip
Skipped test: Deduplicates list fields that return empty lists src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:1931— Skipped — switched off by it.skip
Skipped test: Deduplicates null object fields src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:1935— Skipped — switched off by it.skip
Skipped test: Deduplicates promise object fields src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:1939— Skipped — switched off by it.skip
Skipped test: Handles non-nullable errors thrown outside deferred fragments src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:2066— Skipped — switched off by it.skip
Skipped test: Returns payloads from synchronous data in correct order src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:2194— Skipped — switched off by it.skip
Skipped test: Filters deferred payloads when a list item returned by an async iterable is nulled src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:2198— Skipped — switched off by it.skip
Skipped test: original execute function throws error if anything is deferred and everything else is sync src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:2202— Skipped — switched off by it.skip
Skipped test: original execute function resolves to error if anything is deferred and something else is async src/incremental/handlers/__tests__/graphql17Alpha9/defer.test.ts:2206— Skipped — switched off by it.skip
Skipped test: Negative values of initialCount throw field errors src/incremental/handlers/__tests__/graphql17Alpha9/stream.test.ts:151— Skipped — switched off by it.skip
Skipped test: Returns label from stream directive src/incremental/handlers/__tests__/graphql17Alpha9/stream.test.ts:155— Skipped — switched off by it.skip
+ 42 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×28
No test reaches this file config/processInvariants.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/codemods/ac3-to-ac4/src/util/getAllExports.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 config/helpers.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 config/inlineInheritDoc.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 config/apiExtractor.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 config/react-compiler.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 config/compileTs.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 config/prettier/format-mdx3.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 eslint-local-rules/canonical-references.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 config/exports.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 config/build.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 config/prettier/format-jsdoc.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 config/prepareDist.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 eslint-local-rules/generics.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 config/verifySourceMaps.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 config/version.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/codemods/ac3-to-ac4/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 config/preserveTsIgnore.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 config/size-limit/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file config/deprecateInternals.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 config/madge.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 config/babel.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 config/listImports.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 config/bundlesize.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/codemods/ac3-to-ac4/src/cli.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.
FileTooLong: core/ObservableQuery.ts src/core/ObservableQuery.ts— FileTooLong — 1272 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: ObservableQuery (324-2253). The bar is 500 significant lines; this is 772 over it, 2.54× 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: core/QueryManager.ts src/core/QueryManager.ts— FileTooLong — 1191 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: QueryManager (165-1826). The bar is 500 significant lines; this is 691 over it, 2.38× 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: core/ApolloClient.ts src/core/ApolloClient.ts— FileTooLong — 978 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 478 over it, 1.96× 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: inmemory/policies.ts src/cache/inmemory/policies.ts— FileTooLong — 737 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 237 over it, 1.47× 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: local-state/LocalState.ts src/local-state/LocalState.ts— FileTooLong — 717 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: LocalState (280-1090). The bar is 500 significant lines; this is 217 over it, 1.43× 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: inmemory/readFromStore.ts src/cache/inmemory/readFromStore.ts— FileTooLong — 709 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: StoreReader (157-1018). The bar is 500 significant lines; this is 209 over it, 1.42× 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: hooks/useQuery.ts src/react/hooks/useQuery.ts— FileTooLong — 634 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 134 over it, 1.27× 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: hooks/useSuspenseQuery.ts src/react/hooks/useSuspenseQuery.ts— FileTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 119 over it, 1.24× 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: hooks/useBackgroundQuery.ts src/react/hooks/useBackgroundQuery.ts— FileTooLong — 616 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 116 over it, 1.23× 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: inmemory/writeToStore.ts src/cache/inmemory/writeToStore.ts— FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded), about 62% of them inside a single declaration: StoreWriter (139-799). The bar is 500 significant lines; this is 102 over it, 1.20× 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: core/cache.ts src/cache/core/cache.ts— FileTooLong — 590 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: ApolloCache (224-1052). The bar is 500 significant lines; this is 90 over it, 1.18× 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: inmemory/entityStore.ts src/cache/inmemory/entityStore.ts— FileTooLong — 548 significant lines (blank, comment-only and punctuation-only lines excluded), about 70% of them inside a single declaration: EntityStore (51-727). The bar is 500 significant lines; this is 48 over it, 1.10× 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/renames.ts scripts/codemods/ac3-to-ac4/src/renames.ts— FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 40 over it, 1.08× 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: inmemory/inMemoryCache.ts src/cache/inmemory/inMemoryCache.ts— FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: InMemoryCache (97-903). The bar is 500 significant lines; this is 16 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: __benches__/types.bench.ts src/masking/__benches__/types.bench.ts— FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 13 over it, 1.03× 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×11
Swallowed exception (empty catch) src/utilities/internal/createRejectedPromise.ts:8— `.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) src/utilities/internal/preventUnhandledRejection.ts:2— `.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) src/utilities/internal/globals/maybe.ts:4— 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) src/react/query-preloader/createQueryPreloader.ts:462— `.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) src/react/internal/cache/QueryReference.ts:482— `.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) src/link/persisted-queries/index.ts:448— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:109— `.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) src/config/jest/resolver.ts:34— 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/codemods/ac3-to-ac4/src/util/getAllExports.ts:341— 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) config/helpers.ts:144— `.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.
XxxComment src/link/http/BaseHttpLink.ts:401— // XXX support canceling this request — 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.
XxxComment src/link/batch-http/BaseBatchHttpLink.ts:209— // XXX support canceling this request — 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.
XxxComment src/link/http/rewriteURIForGET.ts:39— // XXX This assumes that the URI is well-formed and that it doesn't — 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.
XxxComment src/core/ObservableQuery.ts:1146— // XXX the subscription variables are separate from the query variables. — 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.
XxxComment src/core/__tests__/fetchPolicies.ts:202— // XXX currently only no-cache is supported as a fetchPolicy — 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.
XxxComment src/cache/inmemory/__tests__/roundtrip.ts:342— // XXX this test is weird because it assumes the server returned an incorrect result — 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.
XxxComment src/__tests__/optimistic.ts:1262— // XXX this test will uncover a flaw in the design of optimistic responses combined with — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment src/__tests__/optimistic.ts:1674— // XXX this test will uncover a flaw in the design of optimistic responses combined with — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
MethodTooLong: ObservableQuery.fetchMore src/core/ObservableQuery.ts:887— MethodTooLong — fetchMore runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: LocalState.resolveClientField src/local-state/LocalState.ts:672— MethodTooLong — resolveClientField runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StoreReader.execSelectionSetImpl src/cache/inmemory/readFromStore.ts:468— MethodTooLong — execSelectionSetImpl runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PersistedQueryLink.constructor src/link/persisted-queries/index.ts:287— MethodTooLong — constructor 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: StoreWriter.processSelectionSet src/cache/inmemory/writeToStore.ts:276— MethodTooLong — processSelectionSet runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: QueryManager.mutate src/core/QueryManager.ts:278— MethodTooLong — mutate runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: QueryManager.getObservableFromLink src/core/QueryManager.ts:895— MethodTooLong — getObservableFromLink runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Deprecated: next integration-tests/next/package.json:23— next 15.2.1, declared in integration-tests/next/package.json, is marked deprecated by its publisher: "This version has a security vulnerability. Please upgrade to a patched version. See https://nextjs.org/blog/[CVE redacted] for more details.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint integration-tests/vite-swc/package.json:27— eslint 8.57.1, declared in integration-tests/vite-swc/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: eslint integration-tests/vite/package.json:29— eslint 8.57.1, declared in integration-tests/vite/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: eslint package.json:207— eslint 9.31.0, declared in 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: subscriptions-transport-ws package.json:253— subscriptions-transport-ws 0.11.0, declared in package.json, is marked deprecated by its publisher: "The `subscriptions-transport-ws` package is no longer maintained. We recommend you use `graphql-ws` instead. For help migrating Apollo software to `graphql-ws`, see https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscriptions-transport-ws For general help using `graphql-ws`, see https://github.com/enisdenjo/graphql-ws/blob/master/README.md". Replace it with the package or version that message names, or record why this one must stay.
FunctionTooLong: processInvariants.processInvariants config/processInvariants.ts:15— FunctionTooLong — processInvariants runs 222 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 122 over it, 2.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: getAllExports.analyze scripts/codemods/ac3-to-ac4/src/util/getAllExports.ts:18— FunctionTooLong — analyze runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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: removeDirectivesFromDocument.removeDirectivesFromDocument src/utilities/internal/removeDirectivesFromDocument.ts:38— FunctionTooLong — removeDirectivesFromDocument runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: useSubscription.useSubscription src/react/hooks/useSubscription.ts:228— FunctionTooLong — useSubscription 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: handleIdentiferRename.handleIdentiferRename scripts/codemods/ac3-to-ac4/src/util/handleIdentiferRename.ts:16— FunctionTooLong — handleIdentiferRename runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
ClassTooLong: StoreReader src/cache/inmemory/readFromStore.ts:157— ClassTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 101 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: ApolloClient src/core/ApolloClient.ts:1035— ClassTooLong — 474 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 74 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: ApolloCache src/cache/core/cache.ts:224— ClassTooLong — 458 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 58 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Policies src/cache/inmemory/policies.ts:375— ClassTooLong — 428 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 28 over it, 1.07× 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: InMemoryCache src/cache/inmemory/inMemoryCache.ts:97— ClassTooLong — 425 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 25 over it, 1.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (12 lines × 2 locations) config/compileTs.ts:64— config/compileTs.ts:64 · config/compileTs.ts:79 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 2 locations) config/listImports.ts:14— config/listImports.ts:14 · scripts/codemods/ac3-to-ac4/src/devLoader.js:4 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (12 lines × 2 locations) src/react/hooks/useQueryRefHandlers.ts:71— src/react/hooks/useQueryRefHandlers.ts:71 · src/react/hooks/useReadQuery.ts:93 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 2 locations) src/testing/internal/incremental/executeSchemaGraphQL17Alpha2.ts:24— src/testing/internal/incremental/executeSchemaGraphQL17Alpha2.ts:24 · src/testing/internal/incremental/executeSchemaGraphQL17Alpha9.ts:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 2 locations) src/utilities/internal/isDeferredFragment.ts:12— src/utilities/internal/isDeferredFragment.ts:12 · src/utilities/internal/isStreamField.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×5
Recursive walk over a caller-supplied document has no depth cap src/utilities/internal/DeepMerger.ts:67— `merge` is exported and takes `target: any` from its caller, and it calls itself at line 67 (`this.merge`) with a piece of `target` — and nowhere in `merge` 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 `merge` 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 src/testing/matchers/utils/getSerializableProperties.ts:18— `getSerializableProperties` is exported and takes `obj: unknown` from its caller, and it calls itself at line 18 (`getSerializableProperties`) with a piece of `obj` (and at line 39) — and nowhere in `getSerializableProperties` 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 `getSerializableProperties` 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 src/masking/maskDefinition.ts:69— `maskDefinition` is exported, takes a document from its caller (line 24) and hands it to `maskSelectionSet`, which calls itself at line 69 (`maskSelectionSet`) with a piece of `data` (and at line 106) — and nowhere in `maskSelectionSet` 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 `maskSelectionSet` 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 src/cache/inmemory/helpers.ts:104— `selectionSetMatchesResult` is exported and takes `result: Record<string, any>` from its caller, and it calls itself at line 104 (`selectionSetMatchesResult`) with a piece of `result` (and at line 112) — and nowhere in `selectionSetMatchesResult` 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 `selectionSetMatchesResult` 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 src/cache/inmemory/key-extractor.ts:230— `getSpecifierPaths` is exported and takes `spec: KeySpecifier` from its caller, and it calls itself at line 230 (`getSpecifierPaths`) with a piece of `spec` — and nowhere in `getSpecifierPaths` 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 `getSpecifierPaths` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
TooManyMethods: ApolloCache src/cache/core/cache.ts:224— 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: InMemoryCache src/cache/inmemory/inMemoryCache.ts:97— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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: ObservableQuery src/core/ObservableQuery.ts:324— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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: EntityStore src/cache/inmemory/entityStore.ts:51— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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.
Complex function (anonymous) (cyclomatic 15, cognitive 14) integration-tests/type-tests/signatures/classic/createQueryPreloader.ts:877— (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 14) integration-tests/type-tests/signatures/classic/useLoadableQuery.ts:652— (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 14) integration-tests/type-tests/signatures/modern/useBackgroundQuery.ts:1168— (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 14) src/cache/inmemory/writeToStore.ts:350— (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
Hotspot: src/core/QueryInfo.ts src/core/QueryInfo.ts:315— src/core/QueryInfo.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in QueryInfo.markMutationResult at line 315. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 09:42:09 -07:00' --until='2026-11-11 09:42:09 -07:00' --full-history --no-merges -- src/core/QueryInfo.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: src/cache/inmemory/writeToStore.ts src/cache/inmemory/writeToStore.ts:276— src/cache/inmemory/writeToStore.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in StoreWriter.processSelectionSet at line 276. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 09:42:09 -07:00' --until='2026-11-11 09:42:09 -07:00' --full-history --no-merges -- src/cache/inmemory/writeToStore.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: src/cache/inmemory/readFromStore.ts src/cache/inmemory/readFromStore.ts:808— src/cache/inmemory/readFromStore.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in StoreReader.prunePartialBoundariesImpl at line 808. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 09:42:09 -07:00' --until='2026-11-11 09:42:09 -07:00' --full-history --no-merges -- src/cache/inmemory/readFromStore.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.
Duplicated block (32 lines × 2 locations) eslint-local-rules/forbid-act-in-disabled-act-environment.ts:3— eslint-local-rules/forbid-act-in-disabled-act-environment.ts:3 · eslint-local-rules/require-disable-act-environment.ts:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (32 lines × 2 locations) src/core/ApolloClient.ts:1509— src/core/ApolloClient.ts:1509 · src/core/ApolloClient.ts:1666 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (32 lines × 2 locations) src/testing/matchers/toComplete.ts:8— src/testing/matchers/toComplete.ts:8 · src/testing/matchers/toEmitNext.ts:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (20 lines × 2 locations) src/cache/core/cache.ts:355— src/cache/core/cache.ts:355 · src/cache/inmemory/inMemoryCache.ts:243 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 2 locations) src/incremental/handlers/defer20220824.ts:190— src/incremental/handlers/defer20220824.ts:190 · src/incremental/handlers/graphql17Alpha9.ts:398 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 2 locations) src/react/internal/cache/FragmentReference.ts:91— src/react/internal/cache/FragmentReference.ts:91 · src/react/internal/cache/QueryReference.ts:293 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
D10 · Test Quality· Fixed-sleep synchronisation · ×2
Fixed-sleep synchronisation: %s: AbortSignal times out during render - can be resumed with `resumeAndPrerender` src/react/ssr/__tests__/prerenderStatic.test.tsx:301— This test starts work it did not wait for (`promise`, still running when the sleep starts) and then orders itself against it with `wait(10)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: %s: AbortSignal times out during render - stops rerendering, returns partial result src/react/ssr/__tests__/prerenderStatic.test.tsx:445— This test starts work it did not wait for (`promise`, still running when the sleep starts) and then orders itself against it with `wait(10)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
HackComment src/core/ObservableQuery.ts:416— // hack, but it saves us from having to make eviction counting an official — 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.
HackComment src/cache/inmemory/__tests__/entityStore.ts:798— // Hacky way of injecting a stray __ref field into the Will Smith Person — 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.
Change coupling: useSuspenseQuery.ts ↔ SuspenseCache.ts src/react/hooks/useSuspenseQuery.ts:1— `src/react/hooks/useSuspenseQuery.ts` and `src/react/internal/cache/SuspenseCache.ts` change together 75% of the time (9 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `b1a5eb80` Allow queryRefs to be disposed of synchronously (#11738); `aaf8c799` `useSuspenseQuery`: remove `promiseCache` (#11363) (at that commit the file was still `src/react/cache/SuspenseCache.ts`); `c0ca7072` Add suspenseCache as a lazy hidden property on ApolloClient (#11053) (at that commit the file was still `src/react/cache/SuspenseCache.ts`) — run `git show` on any of them.
Change coupling: QueryManager.ts ↔ index.ts src/core/QueryManager.ts:1— `src/core/QueryManager.ts` and `src/utilities/internal/index.ts` change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `e4cde699` Parse scalars for `no-cache` queries (#13372); `7a5164d3` Ensure accurate `dataState` with `@defer` only missing fields on init…; `90e338c3` Disambiguate sibling `@defer` fragments with labels (#13390) — run `git show` on any of them.
Sync-over-async blocking config/processInvariants.ts:77— `fs.writeFileSync` in `processInvariants` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking config/react-compiler.ts:23— `readFileSync` in `transformStep` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Duplicated block (24 lines × 2 locations) src/testing/internal/multipart/mockDefer20220824.ts:9— src/testing/internal/multipart/mockDefer20220824.ts:9 · src/testing/internal/multipart/mockDeferStreamGraphql17Alpha9.ts:8 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) src/testing/matchers/toEmitTypedValue.ts:40— src/testing/matchers/toEmitTypedValue.ts:40 · src/testing/matchers/toHaveFragmentWatchesOn.ts:74 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (22 lines × 2 locations) src/core/ApolloClient.ts:354— src/core/ApolloClient.ts:354 · src/core/ApolloClient.ts:415 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (22 lines × 2 locations) src/local-state/LocalState.ts:381— src/local-state/LocalState.ts:381 · src/local-state/LocalState.ts:462 — all 2 copies are in the same file, 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 (16 lines × 2 locations) src/incremental/handlers/defer20220824.ts:83— src/incremental/handlers/defer20220824.ts:83 · src/incremental/handlers/graphql17Alpha9.ts:346 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (16 lines × 2 locations) src/link/batch-http/BaseBatchHttpLink.ts:98— src/link/batch-http/BaseBatchHttpLink.ts:98 · src/link/http/BaseHttpLink.ts:269 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Boundary violation [package:third-party-deep-import] config/helpers.ts:7— config/helpers.ts:7 imports @microsoft/api-extractor/lib/generators/ApiModelGenerator, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] config/helpers.ts:14— config/helpers.ts:14 imports @microsoft/api-extractor-model/lib/items/ApiItem, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Complex function (anonymous) (cyclomatic 17, cognitive 16) integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:873— (anonymous) has cyclomatic complexity 17 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 16) integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:990— (anonymous) has cyclomatic complexity 17 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 13, cognitive 12) integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts:178— (anonymous) has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 13, cognitive 12) integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts:325— (anonymous) has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×2
JavaScript dependencies are not locked integration-tests/peerdeps-tsc/package.json:12— integration-tests/peerdeps-tsc/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked scripts/codemods/ac2-to-ac3/package.json:3— scripts/codemods/ac2-to-ac3/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
LocalState.resolveClientField (cyclomatic 40) src/local-state/LocalState.ts:672— LocalState.resolveClientField has cyclomatic complexity 40 (threshold 15). Of this number, 32 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StoreReader.execSelectionSetImpl (cyclomatic 39) src/cache/inmemory/readFromStore.ts:468— StoreReader.execSelectionSetImpl has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 7 of the 39 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 517, handleMissing). 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.
findReferences.findReferences (cyclomatic 38) scripts/codemods/ac3-to-ac4/src/util/findReferences.ts:7— findReferences.findReferences has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 3 of the 38 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 25, 125). 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.
QueryInfo.markMutationResult (cyclomatic 38) src/core/QueryInfo.ts:315— QueryInfo.markMutationResult has cyclomatic complexity 38 (threshold 15). Of this number, 19 points are the body's own statements and 19 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
processInvariants.processInvariants (cyclomatic 35) config/processInvariants.ts:15— processInvariants.processInvariants has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 2 of the 35 points are its own statements and the rest belongs to 9 function items inside it that branch (transform, isStringOnly, isIdWithName, …). 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.
maskDefinition.maskSelectionSet (cyclomatic 35) src/masking/maskDefinition.ts:52— maskDefinition.maskSelectionSet has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StoreWriter.processSelectionSet (cyclomatic 34) src/cache/inmemory/writeToStore.ts:276— StoreWriter.processSelectionSet has cyclomatic complexity 34 (threshold 15). Of this number, 17 points are the body's own statements and 17 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.
removeDirectivesFromDocument.removeDirectivesFromDocument (cyclomatic 33) src/utilities/internal/removeDirectivesFromDocument.ts:38— removeDirectivesFromDocument.removeDirectivesFromDocument has cyclomatic complexity 33 (threshold 15). Of this number, 17 points are the body's own statements and 16 belong to 5 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.
getAllExports.analyze::collectUsageExamples (cyclomatic 31) scripts/codemods/ac3-to-ac4/src/util/getAllExports.ts:131— getAllExports.analyze::collectUsageExamples has cyclomatic complexity 31 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
QueryManager.fetchQueryByPolicy (cyclomatic 31) src/core/QueryManager.ts:1558— QueryManager.fetchQueryByPolicy has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 11 of the 31 points are its own statements and the rest belongs to 4 function items inside it that branch (resultsFromCache, a function literal at line 1673, a function literal at line 1804, …). 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.
handleIdentiferRename.handleIdentiferRename (cyclomatic 30) scripts/codemods/ac3-to-ac4/src/util/handleIdentiferRename.ts:16— handleIdentiferRename.handleIdentiferRename has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 32, 172). 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.
pagination.relayStylePagination.merge (cyclomatic 30) src/utilities/policies/pagination.ts:157— pagination.relayStylePagination.merge has cyclomatic complexity 30 (threshold 15). Of this number, 29 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
EntityStore.modify (cyclomatic 29) src/cache/inmemory/entityStore.ts:224— EntityStore.modify has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 5 of the 29 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 257, 242, 285). 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.
ObservableQuery._reobserve (cyclomatic 29) src/core/ObservableQuery.ts:1582— ObservableQuery._reobserve has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Policies.updateTypePolicy (cyclomatic 27) src/cache/inmemory/policies.ts:539— Policies.updateTypePolicy has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 578, setMerge). 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.
PersistedQueryLink.constructor (cyclomatic 27) src/link/persisted-queries/index.ts:287— PersistedQueryLink.constructor has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 8 function items inside it that branch (getQueryHash, a function literal at line 360, a function literal at line 426, …). 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.
IncrementalRequest.handle (cyclomatic 25) src/incremental/handlers/graphql17Alpha9.ts:176— IncrementalRequest.handle has cyclomatic complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useSubscription.useSubscription (cyclomatic 25) src/react/hooks/useSubscription.ts:228— useSubscription.useSubscription has cyclomatic complexity 25 (threshold 15). Of this number, 14 points are the body's own statements and 11 belong to 3 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.
StoreReader.prunePartialBoundariesImpl (cyclomatic 23) src/cache/inmemory/readFromStore.ts:808— StoreReader.prunePartialBoundariesImpl has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 838). 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.
plugin.plugin (cyclomatic 22) codegen/custom-scalars/plugin.ts:53— plugin.plugin 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.
QueryManager.refetchQueries (cyclomatic 22) src/core/QueryManager.ts:1335— QueryManager.refetchQueries has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
coerceScalarFieldsToParsed.coerceScalarFieldsToParsed (cyclomatic 22) src/utilities/internal/coerceScalarFieldsToParsed.ts:18— coerceScalarFieldsToParsed.coerceScalarFieldsToParsed has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 4 function items inside it that branch (coerceField, a function literal at line 108, coerceSelectionSet, …). 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.
compileTs.renameJsFilesToCjs (cyclomatic 21) config/compileTs.ts:47— compileTs.renameJsFilesToCjs has cyclomatic complexity 21 (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.
EntityStore.merge (cyclomatic 21) src/cache/inmemory/entityStore.ts:123— EntityStore.merge has cyclomatic complexity 21 (threshold 15). Of this number, 15 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StoreReader.diffQueryAgainstStore (cyclomatic 21) src/cache/inmemory/readFromStore.ts:318— StoreReader.diffQueryAgainstStore has cyclomatic complexity 21 (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.
Policies.fragmentMatches (cyclomatic 21) src/cache/inmemory/policies.ts:807— Policies.fragmentMatches has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
QueryManager.getObservableQueries (cyclomatic 21) src/core/QueryManager.ts:661— QueryManager.getObservableQueries has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 684, 670, 725). 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.
StoreWriter.applyMerges (cyclomatic 20) src/cache/inmemory/writeToStore.ts:699— StoreWriter.applyMerges has cyclomatic complexity 20 (threshold 15). Of this number, 13 points are the body's own statements and 7 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.
QueryManager.mutate (cyclomatic 20) src/core/QueryManager.ts:278— QueryManager.mutate has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 407, 437, 390, …). 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.
ObservableQuery.notify (cyclomatic 20) src/core/ObservableQuery.ts:1819— ObservableQuery.notify has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LocalState.resolveSelectionSet::execute (cyclomatic 19) src/local-state/LocalState.ts:518— LocalState.resolveSelectionSet::execute has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useMutation.useMutation (cyclomatic 19) src/react/hooks/useMutation.ts:483— useMutation.useMutation 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 4 function literals inside it that branch (lines 566, 602, 524, …). 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.
StoreWriter.flattenFields (cyclomatic 18) src/cache/inmemory/writeToStore.ts:560— StoreWriter.flattenFields 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 3 function literals inside it that branch (lines 610, 621, 593). 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.
ObservableQuery.updatePolling (cyclomatic 18) src/core/ObservableQuery.ts:1468— ObservableQuery.updatePolling has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MockLink.request (cyclomatic 18) src/testing/core/mocking/mockLink.ts:128— MockLink.request has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 2 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.
Policies.identify (cyclomatic 17) src/cache/inmemory/policies.ts:439— Policies.identify has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
ObservableQuery.fetchMore (cyclomatic 17) src/core/ObservableQuery.ts:887— ObservableQuery.fetchMore 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 5 function literals inside it that branch (lines 1038, 987, 1114, …). 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.
BaseHttpLink.constructor (cyclomatic 17) src/link/http/BaseHttpLink.ts:264— BaseHttpLink.constructor has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 290, 359, 379, …). 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.
equalByQuery.equalBySelectionSet (cyclomatic 17) src/utilities/internal/equalByQuery.ts:49— equalByQuery.equalBySelectionSet has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 64). 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.
writeToStore.warnAboutDataLoss (cyclomatic 16) src/cache/inmemory/writeToStore.ts:871— writeToStore.warnAboutDataLoss has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, 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.
QueryInfo.markQueryResult (cyclomatic 16) src/core/QueryInfo.ts:145— QueryInfo.markQueryResult has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 232, 221). 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.
ObservableQuery.initializeObservablesQueue (cyclomatic 16) src/core/ObservableQuery.ts:480— ObservableQuery.initializeObservablesQueue has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 510, 491, 503). 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.
ObservableQuery.resubscribeCache (cyclomatic 16) src/core/ObservableQuery.ts:695— ObservableQuery.resubscribeCache has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to one function literal inside it that branches. 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.
BaseBatchHttpLink.constructor (cyclomatic 16) src/link/batch-http/BaseBatchHttpLink.ts:88— BaseBatchHttpLink.constructor has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (batchHandler, a function literal at line 127, 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.
LocalState.collectQueryDetail (cyclomatic 16) src/local-state/LocalState.ts:955— LocalState.collectQueryDetail has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function items inside it that branch (traverse, a function literal at line 1042, a function literal at line 1051, …). 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.
prerenderStatic.prerenderStatic (cyclomatic 16) src/react/ssr/prerenderStatic.tsx:196— prerenderStatic.prerenderStatic has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function items inside it that branch (consume, process, a function literal at line 227, …). 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.
Floating npm dependency: typescript — `typescript` is declared as `latest` in integration-tests/peerdeps-tsc/package.json, which names no releasable version: `latest` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
EntityStore.modify (cognitive 110) src/cache/inmemory/entityStore.ts:224— EntityStore.modify has cognitive complexity 110 (threshold 15). Drivers by points: if/else 22 (92 pts), loops 1 (7 pts), ternaries 3 (7 pts), boolean chains 4 (nesting depth added 80). Most of this is not in the body itself: 11 of the 110 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 257, 242, 285). 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.
LocalState.resolveClientField (cognitive 74) src/local-state/LocalState.ts:672— LocalState.resolveClientField has cognitive complexity 74 (threshold 15). Drivers by points: if/else 23 (42 pts), ternaries 5 (17 pts), boolean chains 8, loops 2 (6 pts), error handling 1 (nesting depth added 35). Of this number, 58 points are the body's own statements and 16 belong to 3 function items inside it that branch. 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.
StoreReader.execSelectionSetImpl (cognitive 68) src/cache/inmemory/readFromStore.ts:468— StoreReader.execSelectionSetImpl has cognitive complexity 68 (threshold 15). Drivers by points: if/else 24 (49 pts), ternaries 3 (12 pts), boolean chains 7 (nesting depth added 34). Most of this is not in the body itself: 5 of the 68 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 517, handleMissing). 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.
maskDefinition.maskSelectionSet (cognitive 66) src/masking/maskDefinition.ts:52— maskDefinition.maskSelectionSet has cognitive complexity 66 (threshold 15). Drivers by points: if/else 18 (43 pts), boolean chains 10, ternaries 4 (10 pts), loops 2 (3 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IncrementalRequest.handle (cognitive 55) src/incremental/handlers/graphql17Alpha9.ts:176— IncrementalRequest.handle has cognitive complexity 55 (threshold 15). Drivers by points: if/else 18 (42 pts), loops 4 (10 pts), boolean chains 3 (nesting depth added 30). Of this number, 46 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
QueryInfo.markMutationResult (cognitive 49) src/core/QueryInfo.ts:315— QueryInfo.markMutationResult has cognitive complexity 49 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 14, ternaries 3 (5 pts) (nesting depth added 17). Of this number, 16 points are the body's own statements and 33 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Policies.updateTypePolicy (cognitive 44) src/cache/inmemory/policies.ts:539— Policies.updateTypePolicy has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (39 pts), boolean chains 5 (nesting depth added 25). Most of this is not in the body itself: 1 of the 44 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 578, setMerge). 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.
pagination.relayStylePagination.merge (cognitive 44) src/utilities/policies/pagination.ts:157— pagination.relayStylePagination.merge has cognitive complexity 44 (threshold 15). Drivers by points: if/else 19 (35 pts), boolean chains 8, ternaries 1 (nesting depth added 16). Of this number, 42 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreWriter.processSelectionSet (cognitive 42) src/cache/inmemory/writeToStore.ts:276— StoreWriter.processSelectionSet has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 10, ternaries 2 (5 pts), error handling 1 (nesting depth added 12). Of this number, 22 points are the body's own statements and 20 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
plugin.plugin (cognitive 39) codegen/custom-scalars/plugin.ts:53— plugin.plugin has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 6 (10 pts), boolean chains 3 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Policies.fragmentMatches (cognitive 38) src/cache/inmemory/policies.ts:807— Policies.fragmentMatches has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 5, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 19). Of this number, 30 points are the body's own statements and 8 belong to 2 function items inside it that branch. 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.
QueryManager.refetchQueries (cognitive 38) src/core/QueryManager.ts:1335— QueryManager.refetchQueries has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (31 pts), boolean chains 6, ternaries 1 (nesting depth added 17). Of this number, 25 points are the body's own statements and 13 belong to 2 function literals inside it that branch. 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.
removeDirectivesFromDocument.removeDirectivesFromDocument (cognitive 37) src/utilities/internal/removeDirectivesFromDocument.ts:38— removeDirectivesFromDocument.removeDirectivesFromDocument has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (25 pts), boolean chains 10, loops 2 (nesting depth added 6). Of this number, 18 points are the body's own statements and 19 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
handleIdentiferRename.handleIdentiferRename (cognitive 35) scripts/codemods/ac3-to-ac4/src/util/handleIdentiferRename.ts:16— handleIdentiferRename.handleIdentiferRename has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 9, ternaries 4 (5 pts) (nesting depth added 7). None of this is in the body itself: all 35 points belong to 2 function literals inside it that branch (lines 32, 172). 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.
DeferRequest.handle (cognitive 33) src/incremental/handlers/defer20220824.ts:100— DeferRequest.handle has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (22 pts), ternaries 2 (7 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityStore.merge (cognitive 31) src/cache/inmemory/entityStore.ts:123— EntityStore.merge has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 6, ternaries 2 (nesting depth added 13). Of this number, 17 points are the body's own statements and 14 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
QueryManager.fetchQueryByPolicy (cognitive 31) src/core/QueryManager.ts:1558— QueryManager.fetchQueryByPolicy has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 9, ternaries 3 (7 pts), match/switch 1 (nesting depth added 9). Most of this is not in the body itself: 8 of the 31 points are its own statements and the rest belongs to 4 function items inside it that branch (resultsFromCache, a function literal at line 1673, resultsFromCache::toResult, …). 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.
PersistedQueryLink.constructor (cognitive 31) src/link/persisted-queries/index.ts:287— PersistedQueryLink.constructor has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 7, ternaries 2 (3 pts), error handling 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 360, a function literal at line 426, getQueryHash, …). 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.
ObservableQuery.fetchMore (cognitive 30) src/core/ObservableQuery.ts:887— ObservableQuery.fetchMore has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 4 (11 pts), boolean chains 3 (nesting depth added 12). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 1038, 987, 1114, …). 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.
ObservableQuery._reobserve (cognitive 30) src/core/ObservableQuery.ts:1582— ObservableQuery._reobserve has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 10, ternaries 2 (nesting depth added 6). Of this number, 28 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
equalByQuery.equalBySelectionSet (cognitive 30) src/utilities/internal/equalByQuery.ts:49— equalByQuery.equalBySelectionSet has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 13). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to one function literal inside it that branches (line 64). 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.
findReferences.findReferences (cognitive 29) scripts/codemods/ac3-to-ac4/src/util/findReferences.ts:7— findReferences.findReferences has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 14, if/else 13 (14 pts), loops 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 25, 125). 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.
getAllExports.analyze::collectUsageExamples (cognitive 29) scripts/codemods/ac3-to-ac4/src/util/getAllExports.ts:131— getAllExports.analyze::collectUsageExamples has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 8, loops 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreReader.prunePartialBoundariesImpl (cognitive 28) src/cache/inmemory/readFromStore.ts:808— StoreReader.prunePartialBoundariesImpl has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 7, ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 7 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 838). 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.
StoreWriter.applyMerges (cognitive 27) src/cache/inmemory/writeToStore.ts:699— StoreWriter.applyMerges has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 3 (7 pts), boolean chains 6 (nesting depth added 10). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 754, getValue). 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.
QueryManager.getObservableQueries (cognitive 26) src/core/QueryManager.ts:661— QueryManager.getObservableQueries has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 6 (nesting depth added 6). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 684, 670, 725). 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.
StoreWriter.flattenFields (cognitive 25) src/cache/inmemory/writeToStore.ts:560— StoreWriter.flattenFields has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 7 (nesting depth added 7). None of this is in the body itself: all 25 points belong to 3 function literals inside it that branch (lines 610, 621, 593). 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.
LocalState.resolveSelectionSet::execute (cognitive 22) src/local-state/LocalState.ts:518— LocalState.resolveSelectionSet::execute has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 6, ternaries 1 (2 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.
DeepMerger.merge (cognitive 22) src/utilities/internal/DeepMerger.ts:51— DeepMerger.merge has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 3 (nesting depth added 9). Of this number, 12 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
plugin.getInputObjectsWithCustomScalars (cognitive 21) codegen/custom-scalars/plugin.ts:249— plugin.getInputObjectsWithCustomScalars has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 4 (6 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QueryManager.mutate (cognitive 21) src/core/QueryManager.ts:278— QueryManager.mutate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4, ternaries 3 (nesting depth added 3). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 407, 437, 390, …). 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.
ObservableQuery.updatePolling (cognitive 21) src/core/ObservableQuery.ts:1468— ObservableQuery.updatePolling has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 3 function items inside it that branch (maybeFetch, shouldCancelPolling, poll). 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.
ApolloClient.watchQuery (cognitive 21) src/core/ApolloClient.ts:1303— ApolloClient.watchQuery has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 1 (nesting depth added 10). Of this number, 17 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useSubscription.useSubscription (cognitive 21) src/react/hooks/useSubscription.ts:228— useSubscription.useSubscription has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 6, ternaries 3 (nesting depth added 1). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 331, 381, 388). 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.
getStoreKeyName.getStoreKeyName (cognitive 21) src/utilities/internal/getStoreKeyName.ts:27— getStoreKeyName.getStoreKeyName has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 8). Of this number, 15 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
processInvariants.processInvariants::transform (cognitive 20) config/processInvariants.ts:188— processInvariants.processInvariants::transform has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 2 (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.
react-compiler.reactCompiler (cognitive 20) config/react-compiler.ts:12— react-compiler.reactCompiler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
apolloClientInitialization.apolloClientInitializationTransform (cognitive 20) scripts/codemods/ac3-to-ac4/src/apolloClientInitialization.ts:26— apolloClientInitialization.apolloClientInitializationTransform has cognitive complexity 20 (threshold 15). Drivers by points: loops 4 (8 pts), ternaries 3 (6 pts), if/else 2 (5 pts), boolean chains 1 (nesting depth added 10). Of this number, 16 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LocalState.collectQueryDetail (cognitive 20) src/local-state/LocalState.ts:955— LocalState.collectQueryDetail has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4 (nesting depth added 5). None of this is in the body itself: all 20 points belong to 4 function items inside it that branch (traverse, a function literal at line 1042, a function literal at line 1051, …). 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.
useMutation.useMutation (cognitive 20) src/react/hooks/useMutation.ts:483— useMutation.useMutation has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 8, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 20 points belong to 4 function literals inside it that branch (lines 566, 602, 524, …). 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.
MockLink.request (cognitive 20) src/testing/core/mocking/mockLink.ts:128— MockLink.request has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 4 (5 pts), boolean chains 2 (nesting depth added 3). Of this number, 10 points are the body's own statements and 10 belong to 2 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.
exports.addExports (cognitive 19) config/exports.ts:17— exports.addExports has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (5 pts), ternaries 2 (3 pts), boolean chains 1 (nesting depth added 7). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 18, processEntryPoint, writeLegacyExport). 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.
StoreReader.diffQueryAgainstStore (cognitive 19) src/cache/inmemory/readFromStore.ts:318— StoreReader.diffQueryAgainstStore has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (8 pts), ternaries 1 (nesting depth added 1). 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.
ObservableQuery.notify (cognitive 19) src/core/ObservableQuery.ts:1819— ObservableQuery.notify has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 7 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prerenderStatic.prerenderStatic::consume (cognitive 19) src/react/ssr/prerenderStatic.tsx:345— prerenderStatic.prerenderStatic::consume has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts), ternaries 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.
ObservableQuery.initializeObservablesQueue (cognitive 18) src/core/ObservableQuery.ts:480— ObservableQuery.initializeObservablesQueue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 3). None of this is in the body itself: all 18 points belong to 3 function literals inside it that branch (lines 510, 491, 503). 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.
BaseHttpLink.constructor (cognitive 18) src/link/http/BaseHttpLink.ts:264— BaseHttpLink.constructor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 6 (nesting depth added 1). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 290, 359, 379, …). 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.
coerceScalarFieldsToParsed.coerceScalarFieldsToParsed::coerceField (cognitive 18) src/utilities/internal/coerceScalarFieldsToParsed.ts:49— coerceScalarFieldsToParsed.coerceScalarFieldsToParsed::coerceField has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityStore.coerceValue (cognitive 17) src/cache/inmemory/entityStore.ts:475— EntityStore.coerceValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Policies.identify (cognitive 17) src/cache/inmemory/policies.ts:439— Policies.identify has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 4 (5 pts), loops 1, ternaries 1 (nesting depth added 1). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
parseAndCheckHttpResponse.consumeMultipartBody (cognitive 17) REDACTED:22— parseAndCheckHttpResponse.consumeMultipartBody has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (8 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 7). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body 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.
InternalQueryReference.handleNext (cognitive 17) src/react/internal/cache/QueryReference.ts:407— InternalQueryReference.handleNext has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
writeToStore.warnAboutDataLoss (cognitive 16) src/cache/inmemory/writeToStore.ts:871— writeToStore.warnAboutDataLoss has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 4, ternaries 3 (nesting depth added 1). Of this number, 12 points are the body's own statements and 4 belong to 2 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.
Policies.getTypePolicy (cognitive 16) src/cache/inmemory/policies.ts:709— Policies.getTypePolicy has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3 (nesting depth added 7). Of this number, 9 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, 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.
policies.makeMergeObjectsFunction.mergeObjects (cognitive 16) src/cache/inmemory/policies.ts:1279— policies.makeMergeObjectsFunction.mergeObjects has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6 (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.
resolver.sync (cognitive 16) src/config/jest/resolver.ts:8— resolver.sync has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 1 (3 pts), boolean chains 2, loops 1 (2 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.
ApolloClient.connectToDevTools (cognitive 16) src/core/ApolloClient.ts:1188— ApolloClient.connectToDevTools has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3 (nesting depth added 6). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
checkDocument.checkDocument (cognitive 16) src/utilities/internal/checkDocument.ts:28— checkDocument.checkDocument has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 4). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change-coupling hub: index.ts → index.ts, index.ts, index.ts src/testing/index.ts— `src/testing/index.ts` changes together with 3 other files — `src/cache/index.ts`, `src/core/index.ts`, `src/react/index.ts` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the its own test command under node's V8 coverage suite in integration-tests/node/ ran and not one test passed (# SyntaxError: Unexpected token 'export'), so the coverage report describes the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
Fake-async — async method never awaits config/version.ts:44— `verifyVersion` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
No structured logging — No logging call was found in the 475 JavaScript/TypeScript production file(s) this check read across 14 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.
Duplication concentrated across 7 sibling directories (7 clone groups) src/cache/core/cache.ts:571— 7 duplicated blocks under src/ have copies in at least two of the sibling directories cache, core, incremental, link, masking, react (+1 more sibling(s) not listed) — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (410 matched lines × 2 locations) · ×1
Duplicated block with local edits (410 matched lines × 2 locations) src/react/hooks/useBackgroundQuery.ts:60— src/react/hooks/useBackgroundQuery.ts:60 · src/react/hooks/useSuspenseQuery.ts:69 — the two spans are one implementation copied and then locally edited — 1992 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 (156 matched lines × 2 locations) · ×1
Duplicated block with local edits (156 matched lines × 2 locations) src/react/hooks/useLazyQuery.ts:49— src/react/hooks/useLazyQuery.ts:49 · src/react/hooks/useQuery.ts:66 — the two spans are one implementation copied and then locally edited — 800 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 (131 matched lines × 2 locations) · ×1
Duplicated block with local edits (131 matched lines × 2 locations) src/react/hooks/useLazyQuery.ts:245— src/react/hooks/useLazyQuery.ts:245 · src/react/hooks/useLoadableQuery.ts:118 — the two spans are one implementation copied and then locally edited — 568 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 (93 matched lines × 2 locations) · ×1
Duplicated block with local edits (93 matched lines × 2 locations) src/react/hooks/useLoadableQuery.ts:213— src/react/hooks/useLoadableQuery.ts:213 · src/react/hooks/useSuspenseQuery.ts:302 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (52 matched lines × 2 locations) · ×1
Duplicated block with local edits (52 matched lines × 2 locations) src/react/hooks/useQuery.ts:215— src/react/hooks/useQuery.ts:215 · src/react/hooks/useSuspenseQuery.ts:170 — the two spans are one implementation copied and then locally edited — 237 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (51 lines × 2 locations) src/testing/internal/schemas/friendList.graphql17Alpha2.ts:16— src/testing/internal/schemas/friendList.graphql17Alpha2.ts:16 · src/testing/internal/schemas/friendList.graphql17Alpha9.ts:19 — 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 with local edits (49 matched lines × 2 locations) · ×1
Duplicated block with local edits (49 matched lines × 2 locations) src/react/hooks/useFragment.ts:77— src/react/hooks/useFragment.ts:77 · src/react/hooks/useSuspenseFragment.ts:72 — the two spans are one implementation copied and then locally edited — 270 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (33 lines × 2 locations) src/cache/core/cache.ts:571— src/cache/core/cache.ts:571 · src/core/ApolloClient.ts:1582 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (28 lines × 2 locations) src/testing/matchers/toEmitError.ts:49— src/testing/matchers/toEmitError.ts:49 · src/testing/matchers/toEmitTypedValue.ts:57 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (23 matched lines × 2 locations) · ×1
Duplicated block with local edits (23 matched lines × 2 locations) src/link/http/BaseHttpLink.ts:366— src/link/http/BaseHttpLink.ts:366 · src/utilities/subscriptions/relay/index.ts:38 — the two spans are one implementation copied and then locally edited — 116 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 (22 matched lines × 2 locations) · ×1
Duplicated block with local edits (22 matched lines × 2 locations) src/core/ApolloClient.ts:665— src/core/ApolloClient.ts:665 · src/core/ObservableQuery.ts:148 — the two spans are one implementation copied and then locally edited — 112 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (21 lines × 2 locations) src/core/ApolloClient.ts:462— src/core/ApolloClient.ts:462 · src/react/query-preloader/createQueryPreloader.ts:140 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (19 lines × 2 locations) src/utilities/internal/caches.ts:32— src/utilities/internal/caches.ts:32 · src/utilities/internal/caches.ts:67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2 locations) config/deprecateInternals.ts:6— config/deprecateInternals.ts:6 · config/preserveTsIgnore.ts:23 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) src/cache/core/cache.ts:1004— src/cache/core/cache.ts:1004 · src/cache/core/cache.ts:1022 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 3 locations) src/config/jest/areCombinedGraphQLErrorsEqual.ts:1— src/config/jest/areCombinedGraphQLErrorsEqual.ts:1 · src/config/jest/areLocalStateErrorsEqual.ts:1 · src/config/jest/areServerErrorsEqual.ts:1 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (17 matched lines × 2 locations) · ×1
Duplicated block with local edits (17 matched lines × 2 locations) src/react/internal/cache/FragmentReference.ts:50— src/react/internal/cache/FragmentReference.ts:50 · src/react/internal/cache/QueryReference.ts:223 — the two spans are one implementation copied and then locally edited — 92 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (15 lines × 2 locations) scripts/codemods/data-masking/unmask.ts:125— scripts/codemods/data-masking/unmask.ts:125 · src/core/QueryManager.ts:1869 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 4 locations) src/cache/core/cache.ts:531— src/cache/core/cache.ts:531 · src/cache/core/cache.ts:892 · src/core/ApolloClient.ts:1525 · src/core/ApolloClient.ts:1687 — the 4 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (12 matched lines × 2 locations) · ×1
Duplicated block with local edits (12 matched lines × 2 locations) src/cache/inmemory/readFromStore.ts:827— src/cache/inmemory/readFromStore.ts:827 · src/utilities/internal/coerceScalarFieldsToParsed.ts:98 — the two spans are one implementation copied and then locally edited — 87 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (11 lines × 2 locations) config/compileTs.ts:89— config/compileTs.ts:89 · config/compileTs.ts:100 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (11 lines × 3 locations) config/deprecateInternals.ts:10— config/deprecateInternals.ts:10 · config/inlineInheritDoc.ts:184 · config/preserveTsIgnore.ts:27 — 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.
Complex function (anonymous) (cyclomatic 53, cognitive 52) integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:1367— (anonymous) has cyclomatic complexity 53 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 36, cognitive 35) integration-tests/type-tests/signatures/modern/useSuspenseQuery.ts:1366— (anonymous) has cyclomatic complexity 36 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function maskSelectionSet (cyclomatic 35, cognitive 66) src/masking/maskDefinition.ts:52— maskSelectionSet has cyclomatic complexity 35 and cognitive complexity 66; 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 resolveClientField (cyclomatic 33, cognitive 63) src/local-state/LocalState.ts:672— resolveClientField has cyclomatic complexity 33 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 33, cognitive 24) scripts/codemods/ac3-to-ac4/src/util/findReferences.ts:25— (anonymous) has cyclomatic complexity 33 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 32, cognitive 77) src/cache/inmemory/readFromStore.ts:517— (anonymous) has cyclomatic complexity 32 and cognitive complexity 77; 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 32, cognitive 40) src/core/ObservableQuery.ts:2073— (anonymous) has cyclomatic complexity 32 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function collectUsageExamples (cyclomatic 31, cognitive 29) scripts/codemods/ac3-to-ac4/src/util/getAllExports.ts:131— collectUsageExamples has cyclomatic complexity 31 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function merge (cyclomatic 29, cognitive 44) src/utilities/policies/pagination.ts:157— merge has cyclomatic complexity 29 and cognitive complexity 44; 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 29, cognitive 34) scripts/codemods/ac3-to-ac4/src/util/handleIdentiferRename.ts:32— (anonymous) has cyclomatic complexity 29 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 29, cognitive 28) integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts:1168— (anonymous) has cyclomatic complexity 29 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (top-level) (cyclomatic 25, cognitive 24) src/incremental/internal/types.ts:1— (top-level) has cyclomatic complexity 25 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 22, cognitive 75) src/cache/inmemory/entityStore.ts:257— (anonymous) has cyclomatic complexity 22 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 24) src/local-state/LocalState.ts:518— (anonymous) has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 20) integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:1107— (anonymous) has cyclomatic complexity 21 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 20, cognitive 38) src/cache/inmemory/policies.ts:578— (anonymous) has cyclomatic complexity 20 and cognitive complexity 38; 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 diffQueryAgainstStore (cyclomatic 20, cognitive 18) src/cache/inmemory/readFromStore.ts:318— diffQueryAgainstStore has cyclomatic complexity 20 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 18) integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:691— (anonymous) has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function markMutationResult (cyclomatic 19, cognitive 16) src/core/QueryInfo.ts:315— markMutationResult has cyclomatic complexity 19 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function processSelectionSet (cyclomatic 17, cognitive 23) src/cache/inmemory/writeToStore.ts:276— processSelectionSet has cyclomatic complexity 17 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 fragmentMatches (cyclomatic 16, cognitive 30) src/cache/inmemory/policies.ts:807— fragmentMatches has cyclomatic complexity 16 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 16, cognitive 29) src/utilities/internal/equalByQuery.ts:64— (anonymous) has cyclomatic complexity 16 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 (anonymous) (cyclomatic 16, cognitive 24) src/cache/inmemory/readFromStore.ts:838— (anonymous) has cyclomatic complexity 16 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function consumeMultipartBody (cyclomatic 15, cognitive 19) REDACTED:22— consumeMultipartBody has cyclomatic complexity 15 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function merge (cyclomatic 15, cognitive 16) src/cache/inmemory/entityStore.ts:123— merge has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function identify (cyclomatic 15, cognitive 13) src/cache/inmemory/policies.ts:439— identify has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function mergeObjects (cyclomatic 14, cognitive 16) src/cache/inmemory/policies.ts:1279— mergeObjects has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 16) src/core/ObservableQuery.ts:510— (anonymous) has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function useSubscription (cyclomatic 14, cognitive 11) src/react/hooks/useSubscription.ts:228— useSubscription has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function applyMerges (cyclomatic 13, cognitive 19) src/cache/inmemory/writeToStore.ts:699— applyMerges has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 13, cognitive 15) src/cache/inmemory/writeToStore.ts:610— (anonymous) has cyclomatic complexity 13 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 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 connectToDevTools (cyclomatic 13, cognitive 14) src/core/ApolloClient.ts:1188— connectToDevTools has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· integration-tests/type-tests/signatures/modern/useBackgroundQuery.ts · ×1
integration-tests/type-tests/signatures/modern/useBackgroundQuery.ts: 2388 lines of code integration-tests/type-tests/signatures/modern/useBackgroundQuery.ts:1— integration-tests/type-tests/signatures/modern/useBackgroundQuery.ts has 2388 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts · ×1
integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts: 2318 lines of code integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts:1— integration-tests/type-tests/signatures/classic/useBackgroundQuery.ts has 2318 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/modern/useSuspenseQuery.ts · ×1
integration-tests/type-tests/signatures/modern/useSuspenseQuery.ts: 2296 lines of code integration-tests/type-tests/signatures/modern/useSuspenseQuery.ts:1— integration-tests/type-tests/signatures/modern/useSuspenseQuery.ts has 2296 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts · ×1
integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts: 2193 lines of code integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts:1— integration-tests/type-tests/signatures/classic/useSuspenseQuery.ts has 2193 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· src/core/ObservableQuery.ts · ×1
src/core/ObservableQuery.ts: 2103 lines of code src/core/ObservableQuery.ts:1— src/core/ObservableQuery.ts has 2103 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/core/ApolloClient.ts: 1883 lines of code src/core/ApolloClient.ts:1— src/core/ApolloClient.ts has 1883 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/core/QueryManager.ts: 1703 lines of code src/core/QueryManager.ts:1— src/core/QueryManager.ts has 1703 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/modern/useMutation.ts · ×1
integration-tests/type-tests/signatures/modern/useMutation.ts: 1503 lines of code integration-tests/type-tests/signatures/modern/useMutation.ts:1— integration-tests/type-tests/signatures/modern/useMutation.ts has 1503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/classic/useMutation.ts · ×1
integration-tests/type-tests/signatures/classic/useMutation.ts: 1304 lines of code integration-tests/type-tests/signatures/classic/useMutation.ts:1— integration-tests/type-tests/signatures/classic/useMutation.ts has 1304 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/classic/useMutation.explicit-generics.ts · ×1
integration-tests/type-tests/signatures/classic/useMutation.explicit-generics.ts: 1286 lines of code integration-tests/type-tests/signatures/classic/useMutation.explicit-generics.ts:1— integration-tests/type-tests/signatures/classic/useMutation.explicit-generics.ts has 1286 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· src/cache/inmemory/policies.ts · ×1
src/cache/inmemory/policies.ts: 1180 lines of code src/cache/inmemory/policies.ts:1— src/cache/inmemory/policies.ts has 1180 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/modern/createQueryPreloader.ts · ×1
integration-tests/type-tests/signatures/modern/createQueryPreloader.ts: 1144 lines of code integration-tests/type-tests/signatures/modern/createQueryPreloader.ts:1— integration-tests/type-tests/signatures/modern/createQueryPreloader.ts has 1144 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· src/local-state/LocalState.ts · ×1
src/local-state/LocalState.ts: 1072 lines of code src/local-state/LocalState.ts:1— src/local-state/LocalState.ts has 1072 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· src/cache/inmemory/readFromStore.ts · ×1
src/cache/inmemory/readFromStore.ts: 1035 lines of code src/cache/inmemory/readFromStore.ts:1— src/cache/inmemory/readFromStore.ts has 1035 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/classic/createQueryPreloader.ts · ×1
integration-tests/type-tests/signatures/classic/createQueryPreloader.ts: 1000 lines of code integration-tests/type-tests/signatures/classic/createQueryPreloader.ts:1— integration-tests/type-tests/signatures/classic/createQueryPreloader.ts has 1000 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/cache/core/cache.ts: 985 lines of code src/cache/core/cache.ts:1— src/cache/core/cache.ts has 985 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/modern/useLoadableQuery.ts · ×1
integration-tests/type-tests/signatures/modern/useLoadableQuery.ts: 925 lines of code integration-tests/type-tests/signatures/modern/useLoadableQuery.ts:1— integration-tests/type-tests/signatures/modern/useLoadableQuery.ts has 925 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· src/react/hooks/useBackgroundQuery.ts · ×1
src/react/hooks/useBackgroundQuery.ts: 902 lines of code src/react/hooks/useBackgroundQuery.ts:1— src/react/hooks/useBackgroundQuery.ts has 902 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· src/react/hooks/useQuery.ts · ×1
src/react/hooks/useQuery.ts: 899 lines of code src/react/hooks/useQuery.ts:1— src/react/hooks/useQuery.ts has 899 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· src/cache/inmemory/entityStore.ts · ×1
src/cache/inmemory/entityStore.ts: 894 lines of code src/cache/inmemory/entityStore.ts:1— src/cache/inmemory/entityStore.ts has 894 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· src/cache/inmemory/writeToStore.ts · ×1
src/cache/inmemory/writeToStore.ts: 888 lines of code src/cache/inmemory/writeToStore.ts:1— src/cache/inmemory/writeToStore.ts has 888 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· scripts/codemods/ac3-to-ac4/src/renames.ts · ×1
scripts/codemods/ac3-to-ac4/src/renames.ts: 836 lines of code scripts/codemods/ac3-to-ac4/src/renames.ts:1— scripts/codemods/ac3-to-ac4/src/renames.ts has 836 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/classic/useLoadableQuery.ts · ×1
integration-tests/type-tests/signatures/classic/useLoadableQuery.ts: 821 lines of code integration-tests/type-tests/signatures/classic/useLoadableQuery.ts:1— integration-tests/type-tests/signatures/classic/useLoadableQuery.ts has 821 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· src/react/hooks/useSuspenseQuery.ts · ×1
src/react/hooks/useSuspenseQuery.ts: 818 lines of code src/react/hooks/useSuspenseQuery.ts:1— src/react/hooks/useSuspenseQuery.ts has 818 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· src/cache/inmemory/inMemoryCache.ts · ×1
src/cache/inmemory/inMemoryCache.ts: 802 lines of code src/cache/inmemory/inMemoryCache.ts:1— src/cache/inmemory/inMemoryCache.ts has 802 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· codegen/local-state/visitor.ts · ×1
codegen/local-state/visitor.ts: 635 lines of code codegen/local-state/visitor.ts:1— codegen/local-state/visitor.ts has 635 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/v4-migration.ts: 635 lines of code src/v4-migration.ts:1— src/v4-migration.ts has 635 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/modern/useQuery.ts · ×1
integration-tests/type-tests/signatures/modern/useQuery.ts: 627 lines of code integration-tests/type-tests/signatures/modern/useQuery.ts:1— integration-tests/type-tests/signatures/modern/useQuery.ts has 627 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/react/hooks/useLazyQuery.ts · ×1
src/react/hooks/useLazyQuery.ts: 617 lines of code src/react/hooks/useLazyQuery.ts:1— src/react/hooks/useLazyQuery.ts has 617 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/core/QueryInfo.ts: 603 lines of code src/core/QueryInfo.ts:1— src/core/QueryInfo.ts has 603 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· src/react/hooks/useMutation.ts · ×1
src/react/hooks/useMutation.ts: 595 lines of code src/react/hooks/useMutation.ts:1— src/react/hooks/useMutation.ts has 595 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/modern/useLazyQuery.ts · ×1
integration-tests/type-tests/signatures/modern/useLazyQuery.ts: 594 lines of code integration-tests/type-tests/signatures/modern/useLazyQuery.ts:1— integration-tests/type-tests/signatures/modern/useLazyQuery.ts has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/classic/useQuery.ts · ×1
integration-tests/type-tests/signatures/classic/useQuery.ts: 498 lines of code integration-tests/type-tests/signatures/classic/useQuery.ts:1— integration-tests/type-tests/signatures/classic/useQuery.ts has 498 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· src/react/internal/cache/QueryReference.ts · ×1
src/react/internal/cache/QueryReference.ts: 497 lines of code src/react/internal/cache/QueryReference.ts:1— src/react/internal/cache/QueryReference.ts has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· scripts/codemods/ac3-to-ac4/src/apolloClientInitialization.ts · ×1
scripts/codemods/ac3-to-ac4/src/apolloClientInitialization.ts: 482 lines of code scripts/codemods/ac3-to-ac4/src/apolloClientInitialization.ts:1— scripts/codemods/ac3-to-ac4/src/apolloClientInitialization.ts has 482 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· src/react/hooks/useLoadableQuery.ts · ×1
src/react/hooks/useLoadableQuery.ts: 482 lines of code src/react/hooks/useLoadableQuery.ts:1— src/react/hooks/useLoadableQuery.ts has 482 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· src/link/persisted-queries/index.ts · ×1
src/link/persisted-queries/index.ts: 481 lines of code src/link/persisted-queries/index.ts:1— src/link/persisted-queries/index.ts has 481 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· integration-tests/type-tests/signatures/classic/useLazyQuery.ts · ×1
integration-tests/type-tests/signatures/classic/useLazyQuery.ts: 465 lines of code integration-tests/type-tests/signatures/classic/useLazyQuery.ts:1— integration-tests/type-tests/signatures/classic/useLazyQuery.ts has 465 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· src/link/core/ApolloLink.ts · ×1
src/link/core/ApolloLink.ts: 459 lines of code src/link/core/ApolloLink.ts:1— src/link/core/ApolloLink.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· src/react/query-preloader/createQueryPreloader.ts · ×1
src/react/query-preloader/createQueryPreloader.ts: 435 lines of code src/react/query-preloader/createQueryPreloader.ts:1— src/react/query-preloader/createQueryPreloader.ts has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~88 LoC) config/prettier/format-jsdoc.js— no import path from any entry point (106 application, 21 tooling, 369 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 (~39 LoC) scripts/codemods/misc/mockLinkRejection.ts— no import path from any entry point (106 application, 21 tooling, 369 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 (~17 LoC) config/prettier/test.ts— no import path from any entry point (106 application, 21 tooling, 369 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
Unlisted import 'jest-resolve' src/config/jest/resolver.ts:4— Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
Unused dependency '@actions/github-script' package.json:167— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@size-limit/esbuild-why' package.json:182— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@size-limit/preset-small-lib' package.json:183— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@graphql-codegen/add' integration-tests/codegen/package.json:12— Declared in integration-tests/codegen/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'resolve-esm' integration-tests/node/package.json:18— Declared in integration-tests/node/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.
Disabled test src/__tests__/ApolloClient.ts:3153— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/__tests__/client.ts:795— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/__tests__/client.ts:852— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/cache/core/__tests__/cache.ts:389— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/cache/core/__tests__/cache.watchFragment/types.test.ts:12— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/cache/inmemory/__tests__/cache.ts:4538— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/core/__tests__/ApolloClient/general.test.ts:377— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/core/__tests__/ApolloClient/general.test.ts:9314— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/core/__tests__/ApolloClient/multiple-results.test.ts:236— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/core/__tests__/ObservableQuery.ts:5845— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/core/__tests__/ObservableQuery.ts:8010— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/core/__tests__/ObservableQuery.ts:8011— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/core/__tests__/RefetchEventManager/types.test.ts:22— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/core/__tests__/client.watchFragment/types.test.ts:12— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/errors/__tests__/is.test.ts:142— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/incremental/handlers/__tests__/defer20220824/defer.test.ts:182— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/incremental/handlers/__tests__/defer20220824/defer.test.ts:375— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/incremental/handlers/__tests__/defer20220824/defer.test.ts:379— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/incremental/handlers/__tests__/defer20220824/defer.test.ts:503— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/incremental/handlers/__tests__/defer20220824/defer.test.ts:582— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/incremental/handlers/__tests__/defer20220824/defer.test.ts:586— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/incremental/handlers/__tests__/defer20220824/defer.test.ts:590— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/incremental/handlers/__tests__/defer20220824/stream.test.ts:138— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/incremental/handlers/__tests__/defer20220824/stream.test.ts:142— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/incremental/handlers/__tests__/defer20220824/stream.test.ts:146— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Deprecated: glob REDACTED:4051— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:12570— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:13005— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:17180— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-properties integration-tests/pnpm-lock.yaml:582— @babel/plugin-proposal-class-properties 7.18.6 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-nullish-coalescing-operator integration-tests/pnpm-lock.yaml:595— @babel/plugin-proposal-nullish-coalescing-operator 7.18.6 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-numeric-separator integration-tests/pnpm-lock.yaml:602— @babel/plugin-proposal-numeric-separator 7.18.6 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-chaining integration-tests/pnpm-lock.yaml:609— @babel/plugin-proposal-optional-chaining 7.21.0 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-methods integration-tests/pnpm-lock.yaml:616— @babel/plugin-proposal-private-methods 7.18.6 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-property-in-object integration-tests/pnpm-lock.yaml:629— @babel/plugin-proposal-private-property-in-object 7.21.11 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @graphql-tools/prisma-loader integration-tests/pnpm-lock.yaml:1844— @graphql-tools/prisma-loader 8.0.17 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "This package was intended to be used with an older versions of Prisma.\nThe newer versions of Prisma has a different approach to GraphQL integration.\nTherefore, this package is no longer needed and has been deprecated and removed.\nLearn more: https://www.prisma.io/graphql". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array integration-tests/pnpm-lock.yaml:1916— @humanwhocodes/config-array 0.13.0 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema integration-tests/pnpm-lock.yaml:1925— @humanwhocodes/object-schema 2.0.3 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "Use @eslint/object-schema instead". 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 integration-tests/pnpm-lock.yaml:2818— @ungap/structured-clone 1.3.0 is resolved in integration-tests/pnpm-lock.yaml 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: abab integration-tests/pnpm-lock.yaml:2907— abab 2.0.6 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "Use your platform's native atob() and btoa() methods instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: domexception integration-tests/pnpm-lock.yaml:3922— domexception 2.0.1 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob integration-tests/pnpm-lock.yaml:4495— glob 10.4.5 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob integration-tests/pnpm-lock.yaml:4500— glob 7.2.3 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight integration-tests/pnpm-lock.yaml:4777— inflight 1.0.6 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: node-domexception integration-tests/pnpm-lock.yaml:5617— node-domexception 1.0.0 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: q integration-tests/pnpm-lock.yaml:6391— q 1.5.1 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: resolve-url integration-tests/pnpm-lock.yaml:6604— resolve-url 0.2.1 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "https://github.com/lydell/resolve-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf integration-tests/pnpm-lock.yaml:6645— rimraf 3.0.2 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rollup-plugin-terser integration-tests/pnpm-lock.yaml:6650— rollup-plugin-terser 7.0.2 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-resolve integration-tests/pnpm-lock.yaml:6912— source-map-resolve 0.5.3 is resolved in integration-tests/pnpm-lock.yaml and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-resolve#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Duplicated predicate src/cache/inmemory/readFromStore.ts:636— `!fragment && selection.kind === Kind.FRAGMENT_SPREAD` appears character-identically in 2 files — src/cache/inmemory/readFromStore.ts, src/cache/inmemory/writeToStore.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 src/local-state/LocalState.ts:1158— `arg.name.value === "always" && arg.value.kind === "BooleanValue" && arg.value.value === true` appears character-identically in 2 files — src/local-state/LocalState.ts, src/utilities/internal/hasForcedResolvers.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 src/link/http/BaseHttpLink.ts:383— `ctype !== null && /^multipart\/mixed/i.test(ctype)` appears character-identically in 2 files — src/link/http/BaseHttpLink.ts, src/utilities/subscriptions/relay/index.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 eslint-local-rules/forbid-act-in-disabled-act-environment.ts:26— `directCallee?.type === "Identifier" && directCallee.name === "disableActEnvironment"` appears character-identically in 2 files — eslint-local-rules/forbid-act-in-disabled-act-environment.ts, eslint-local-rules/require-disable-act-environment.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 eslint-local-rules/forbid-act-in-disabled-act-environment.ts:13— `disabledDepth !== false && disabledDepth > depth` appears character-identically in 2 files — eslint-local-rules/forbid-act-in-disabled-act-environment.ts, eslint-local-rules/require-disable-act-environment.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 src/testing/matchers/toComplete.ts:24— `error instanceof Error && error.message === "Timeout waiting for next event"` appears character-identically in 5 files — src/testing/matchers/toComplete.ts, src/testing/matchers/toEmitAnything.ts, src/testing/matchers/toEmitError.ts, src/testing/matchers/toEmitNext.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 src/utilities/internal/argumentsObjectFromField.ts:10— `field.arguments && field.arguments.length` appears character-identically in 2 files — src/utilities/internal/argumentsObjectFromField.ts, src/utilities/internal/storeKeyNameFromField.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 src/react/hooks/useLoadableQuery.ts:520— `options.fetchPolicy || client.defaultOptions.watchQuery?.fetchPolicy || "cache-first"` appears character-identically in 2 files — src/react/hooks/useLoadableQuery.ts, src/react/hooks/useSuspenseQuery.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.
Orphaned file src/utilities/policies/pagination.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 src/utilities/internal/canonicalStringify.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 src/cache/core/types/common.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 src/cache/inmemory/reactiveVars.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.
Outdated (npm): @graphql-codegen/add integration-tests/codegen/package.json:12— @graphql-codegen/add is pinned at 5.0.3; registry.npmjs.org publishes 8.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): @graphql-codegen/cli integration-tests/codegen/package.json:13— @graphql-codegen/cli is pinned at 5.0.7; registry.npmjs.org publishes 8.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/node integration-tests/next/package.json:17— @types/node is pinned at 20.3.1; registry.npmjs.org publishes 26.6.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.
redundant comment scripts/codemods/ac3-to-ac4/src/util/getAllExports.ts:23— "Load tsconfig.json from the project root" repeats the code it sits on: 4 of its 5 words (tsconfig, json, project, root) are already in `const configPath = path.join(projectRoot, "tsconfig.json");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/cache/inmemory/policies.ts:1039— "Call read(existing, readOptions) with cacheSlot holding this.cache." repeats the code it sits on: 6 of its 7 words (call, read, existing, options, cache, slot) are already in `return cacheSlot.withValue(this.cache, read, [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/incremental/__benches__/types.bench.ts:345— "query { search { ... on User { id name } ... on Post { id title } } }" repeats the code it sits on: 6 of its 7 words (search, user, id, name, post, title) are already in `type Source = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Fat interface: Classic (18 required operations) src/react/hooks/useSuspenseQuery.ts:308— `Classic` declares 18 required operations under just 1 distinct name(s): `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 1 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: Classic (30 required operations) src/react/hooks/useBackgroundQuery.ts:302— `Classic` declares 30 required operations under just 1 distinct name(s): `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 30 separate responsibilities: a caller binds to 1 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 30 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Silent fallback default in catch src/react/hooks/internal/useRenderGuard.ts:37— `useRenderGuard` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/utilities/invariant/index.ts:104— `stringify` swallows every exception into `return "<non-serializable>"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Mock-dominated test: multiple subscribers will trigger multiple requests src/link/retry/__tests__/retryLink.ts:104— This test sets up 4 test doubles (for example `jest.fn`) against 3 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 23 significant file(s) lose their only recent owner: integration-tests/type-tests/signatures/modern/useMutation.ts, integration-tests/type-tests/signatures/modern/createQueryPreloader.ts, src/react/hooks/useMutation.ts, codegen/custom-scalars/plugin.ts, src/core/RefetchEventManager.ts, integration-tests/type-tests/signatures/modern/mutate.ts, integration-tests/type-tests/customScalars/all-unknown/matchingTypes/index.ts, integration-tests/type-tests/customScalars/all-any/matchingTypes/index.ts (+15 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 (27 single-owned of 189 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; 189 of the 508 production source files in this repository met that bar). They are anonymized user #2 (4 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: config/helpers.ts, src/link/batch-http/BaseBatchHttpLink.ts, config/apiExtractor.ts, config/react-compiler.ts.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion package.json:1— `(repository root)` (43001 LoC, 714 module-visible types across 63 directories) overshoots its size bounds. 1 of 8 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 7.5/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 4 of 189 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; 189 of the 508 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: src/utilities/policies/pagination.ts, src/utilities/internal/canonicalStringify.ts, src/cache/core/types/common.ts, src/cache/inmemory/reactiveVars.ts. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST .github/workflows/api-extractor.yml:2— 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 20 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
Unused export 'reparse' config/helpers.ts:28— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'PreserveTypes' · ×1
Unused export 'PreserveTypes' src/masking/PreserveTypes.ts:3— No runtime consumer imports this binding — the only demand on it comes from a type-position import of its module, which asks for the module's type surface rather than for this name. If the value is genuinely unneeded, remove it; if a consumer needs only its TYPE, export that type (e.g. `export type X = typeof x`) and drop the value. A value export — a const, a function, a class — cannot itself be rewritten as `export type`.
R7 · Dead Code· Unused module-local declaration 'findParentFunction' · ×1
Unused module-local declaration 'findParentFunction' eslint-local-rules/require-disable-act-environment.ts:72— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R8 · Dependency Hygiene· Type-only dependency '@graphql-typed-document-node/core' in production deps · ×1
Type-only dependency '@graphql-typed-document-node/core' in production deps src/__tests__/ApolloClient.ts:1— Every import is type-only — move it to devDependencies.
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 — 14/20 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~2.2 `!` null assertions per 1k TypeScript source lines — 117 assertion(s) across the 53484 source line(s) of the 397 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: src/core/ObservableQuery.ts (12), codegen/local-state/visitor.ts (11), config/apiExtractor.ts (8). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Outdated (npm): @apollo/client-integration-nextjs — @apollo/client-integration-nextjs is pinned at 0.12.0-alpha.1; registry.npmjs.org publishes 0.14.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @graphql-codegen/plugin-helpers — @graphql-codegen/plugin-helpers is pinned at 6.3.0; registry.npmjs.org publishes 8.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): @graphql-codegen/typescript — @graphql-codegen/typescript is pinned at 5.0.10; registry.npmjs.org publishes 7.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @graphql-codegen/visitor-plugin-common — @graphql-codegen/visitor-plugin-common is pinned at 6.3.0; registry.npmjs.org publishes 8.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): @graphql-tools/schema — @graphql-tools/schema is pinned at 10.0.21; registry.npmjs.org publishes 11.0.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @playwright/test — @playwright/test is pinned at 1.62.1; registry.npmjs.org publishes 1.65.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): @types/react — @types/react is pinned at 18.2.14; registry.npmjs.org publishes 19.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/react-dom — @types/react-dom is pinned at 18.2.6; registry.npmjs.org publishes 19.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @wry/caches — @wry/caches is pinned at 1.0.0; registry.npmjs.org publishes 1.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @wry/equality — @wry/equality is pinned at 0.5.6; registry.npmjs.org publishes 0.5.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): expect-type — expect-type is pinned at 1.2.1; registry.npmjs.org publishes 1.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.
Outdated (npm): graphql — graphql is pinned at 16.14.2; registry.npmjs.org publishes 17.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): graphql-tag — graphql-tag is pinned at 2.12.6; registry.npmjs.org publishes 2.12.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): jscodeshift — jscodeshift is pinned at 17.3.0; registry.npmjs.org publishes 17.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.
Outdated (npm): lodash — lodash is pinned at 4.17.21; registry.npmjs.org publishes 4.18.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): next — next is pinned at 15.2.1; registry.npmjs.org publishes 16.4.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): optimism — optimism is pinned at 0.18.0; registry.npmjs.org publishes 0.18.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): prettier — prettier is pinned at 3.1.1; registry.npmjs.org publishes 3.10.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 — react is pinned at 18.3.1; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-dom — react-dom is pinned at 18.3.1; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): tslib — tslib is pinned at 2.8.1; registry.npmjs.org publishes 2.9.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): typescript — typescript is pinned at 5.9.3; registry.npmjs.org publishes 7.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.
doc comments repeat the names src/cache/core/cache.ts:118— 0 of 69 documented parameters and 4 of 641 summaries in `@apollo/client` only repeat the member or parameter name (e.g. "Watched fragment options." for `WatchFragmentOptions`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names codegen/local-state/config.ts:67— 0 of 0 documented parameters and 1 of 17 summaries in `@apollo/client-graphql-codegen` only repeat the member or parameter name (e.g. "The import name for the base schema types." for `baseSchemaTypesImportName`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 40 file(s) — `config/apiExtractor.ts`, `config/babel.ts`, `config/build.ts`, `config/precheck.ts`, `config/version.ts`, … (+35 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e98f-3aa6-7292-a8e6-802e07b8b379 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 67 · Warnings: 655 · Recommendations: 115 · Info: 24 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 12:50 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.