Public report of microsoft/playwright, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 09:43 UTC · Survey ID cd_bb1881a31aae436f89b696458639aa1e
microsoft/playwright
Measured 14 November 2026, 09:41 UTC, at code version 0ca0119
Code coverage is not measured: .NET and JavaScript/TypeScript suite (CouldNotMeasureRepoBuildError, CouldNotMeasureNoRunner).
Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 154,295 lines of product code in 17 projects, tests not counted · Estimated rebuild effort: about 2.8 person-years · Weakest lens: Production Readiness, 54
Findings by how serious they are
97 critical2246 serious176 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
14 November 2026, 09:41 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.
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 ▸
56of 56 dimensions measured by tools.
2501of 2519 findings point to an exact file and line, so you can open each one in the code. The other 18 concern the repository as a whole, such as missing documentation.
56dimensions across 6 lenses, read from 154,295 lines of product code in 17 projects.
microsoft/playwright falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 59 out of 100 and is rated Adequate, and 32 of its 97 critical findings are security problems.
Production Readiness, at 54, is the weakest lens and counts most in the score. The best first step is making the 39 tests that check nothing check their results, worth about 5 points. Adding automated security scanning would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 64.
Nine places in the code run text as code, which an attacker could use. Six settings leave the servers or containers unsafe, and thirteen sets of files in separate parts keep changing together, which points to hidden dependencies. Replacing text run as code with direct calls, correcting the unsafe settings and making the hidden dependencies explicit would close these risks. Limiting each secret to its own step would fix the five secrets exposed to more of the pipeline than needed, and passing outside input through environment variables would deal with the four pipeline steps that put outside input straight into a shell command. The 39 tests that check nothing need to check the result they produce.
The product code is 154,295 lines, about €410,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 54 to 70, the lowest score rated Strong, the score would rise from 59 to about 64.
Code composition: what the lines of code are
Supporting code 0%Tests 100%
New since the last survey: 115 findings
These 115 critical or serious findings weren't in the previous survey, on 26 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Test Quality · Skipped test: (unnamed test) tests/page/page-evaluate-callback.spec.ts
Test Quality · Skipped test: (unnamed test) tests/page/page-evaluate.spec.ts
Test Quality · Skipped test: (unnamed test) tests/page/page-event-popup.spec.ts
Test Quality · Skipped test: (unnamed test) tests/page/page-filechooser.spec.ts
Test Quality · Skipped test: (unnamed test) tests/page/page-goto.spec.ts
Test Quality · Skipped test: (unnamed test) tests/page/page-route.spec.ts
Test Quality · Skipped test: (unnamed test) tests/page/page-screenshot.spec.ts
Test Quality · Skipped test: (unnamed test) tests/mcp/config-resolve.spec.ts
Test Quality · Skipped test: (unnamed test) tests/installation/playwright-cli-install-should-work.spec.ts
Test Quality · No assertions: AR-171 should include inert elements and elements outside of a modal dialog tests/page/page-aria-snapshot.spec.ts
Test Quality · No assertions: PO-029 should load subresources of an about:blank popup when the opener has routes tests/library/popup.spec.ts
Test Quality · No assertions (empty test): HS-002 should close upgrade requests to unknown paths tests/library/unit/http-server.spec.ts
Test Quality · No assertions: attach --extension gives the name and the color of the session to the tab group tests/extension/cli.spec.ts
Test Quality · No assertions: tab dragged out of a group that a client left stays free tests/extension/tab-dragging.spec.ts
Test Quality · No assertions: client sets the title and the color of its tab group tests/extension/tab-grouping.spec.ts
Test Quality · No assertions: tabs that the user picks from two windows go into one group tests/extension/tab-grouping.spec.ts
Test Quality · No assertions: tab that the user closes leaves the client tests/extension/tab-management.spec.ts
Test Quality · No assertions (empty test): debugger attach that is still in progress is released when the client leaves tests/extension/tab-management.spec.ts
Large Files · REDACTED: 1760 lines of code REDACTED
Large Files · packages/playwright-core/src/server/frames.ts: 1729 lines of code packages/playwright-core/src/server/frames.ts
Large Files · browser_patches/firefox/juggler/TargetRegistry.js: 1437 lines of code browser_patches/firefox/juggler/TargetRegistry.js
Large Files · packages/playwright-core/src/tools/cli-daemon/commands.ts: 1324 lines of code packages/playwright-core/src/tools/cli-daemon/commands.ts
Large Files · packages/playwright-core/src/server/registry/index.ts: 1307 lines of code packages/playwright-core/src/server/registry/index.ts
Large Files · packages/injected/src/roleUtils.ts: 1262 lines of code packages/injected/src/roleUtils.ts
Large Files · packages/playwright-core/src/server/webkit/wkPage.ts: 1241 lines of code packages/playwright-core/src/server/webkit/wkPage.ts
Large Files · packages/playwright-core/src/server/webkit/webview/wvPage.ts: 1197 lines of code packages/playwright-core/src/server/webkit/webview/wvPage.ts
Large Files · REDACTED: 1188 lines of code REDACTED
Large Files · browser_patches/firefox/juggler/NetworkObserver.js: 1051 lines of code browser_patches/firefox/juggler/NetworkObserver.js
Large Files · packages/playwright-core/src/server/page.ts: 1039 lines of code packages/playwright-core/src/server/page.ts
Large Files · packages/playwright-core/src/server/dom.ts: 960 lines of code packages/playwright-core/src/server/dom.ts
Large Files · packages/playwright-core/src/client/page.ts: 859 lines of code packages/playwright-core/src/client/page.ts
Large Files · packages/playwright/src/index.ts: 856 lines of code packages/playwright/src/index.ts
Large Files · packages/playwright-core/src/server/trace/recorder/tracing.ts: 845 lines of code packages/playwright-core/src/server/trace/recorder/tracing.ts
Large Files · packages/playwright-core/src/server/network.ts: 839 lines of code packages/playwright-core/src/server/network.ts
Large Files · packages/playwright-core/src/server/fetch.ts: 824 lines of code packages/playwright-core/src/server/fetch.ts
Large Files · utils/doclint/generateDotnetApi.js: 809 lines of code utils/doclint/generateDotnetApi.js
Large Files · packages/injected/src/clock.ts: 803 lines of code packages/injected/src/clock.ts
Large Files · packages/playwright/src/isomorphic/teleReceiver.ts: 789 lines of code packages/playwright/src/isomorphic/teleReceiver.ts
Large Files · REDACTED: 757 lines of code REDACTED
Large Files · packages/playwright-core/src/server/har/harTracer.ts: 734 lines of code packages/playwright-core/src/server/har/harTracer.ts
Large Files · packages/playwright-core/src/server/bidi/bidiPage.ts: 699 lines of code packages/playwright-core/src/server/bidi/bidiPage.ts
Large Files · REDACTED: 669 lines of code REDACTED
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 688 findings
These 688 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one. The first 100 are listed here.
God Classes · ClassTooLong: PageAgent browser_patches/firefox/juggler/content/PageAgent.js
€140,000 to €680,000, for 2,260 to 7,168 hours of work, about 2.8 person-years for 1 to 6 engineers
Difficulty of the problem
Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 154,295 lines of product code
Comment lines
The estimate prices 154,270 lines. Comment lines count towards the size of 154,295 lines but aren't priced as work.
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.
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 39 No assertions (empty test) finding(s) in Test Quality — start with unroute-behavior.spec.ts (5), page-autowaiting-no-hang.spec.ts (4), page-history.spec.ts (3).
Raises the score by about 5 points · Medium effort · Test Quality
2
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.
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.
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 €410,000 to build again, about 2.8 person-years of work. Its weakest lens is Production Readiness, at 54 (Adequate). 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 39 No assertions (empty test) finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort, because it clears the 39 Test Quality 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.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 11% on every change. The history of the code shows how much it changes: about 104,405 lines over the last 90 days, which is about 423,420 lines a year. At that pace, the extra work comes to an estimated 52.9 to 317.3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
416 modules, with 1047 dependencies between them. 8 loops run through 56 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 376 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.
packages.playwright-core.src.client.channelOwner uses packages.playwright-core.src.client.eventEmitter, so a change to packages.playwright-core.src.client.eventEmitter can break packages.playwright-core.src.client.channelOwner, while a change to packages.playwright-core.src.client.channelOwner can't break packages.playwright-core.src.client.eventEmitter.
Position
Below the diagonal: packages.playwright-core.src.client.channelOwner uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.jsHandle uses packages.playwright-core.src.client.channelOwner, so a change to packages.playwright-core.src.client.channelOwner can break packages.playwright-core.src.client.jsHandle, while a change to packages.playwright-core.src.client.jsHandle can't break packages.playwright-core.src.client.channelOwner.
Position
Below the diagonal: packages.playwright-core.src.client.jsHandle uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.network uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.client.network, while a change to packages.playwright-core.src.client.network can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.client.network uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.network uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.client.network, while a change to packages.playwright-core.src.client.network can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.client.network uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.network uses packages.injected.src.webSocketMock, so a change to packages.injected.src.webSocketMock can break packages.playwright-core.src.client.network, while a change to packages.playwright-core.src.client.network can't break packages.injected.src.webSocketMock.
Position
Below the diagonal: packages.playwright-core.src.client.network uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.network uses packages.isomorphic.types, so a change to packages.isomorphic.types can break packages.playwright-core.src.client.network, while a change to packages.playwright-core.src.client.network can't break packages.isomorphic.types.
Position
Below the diagonal: packages.playwright-core.src.client.network uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.network uses packages.playwright-core.src.client.channelOwner, so a change to packages.playwright-core.src.client.channelOwner can break packages.playwright-core.src.client.network, while a change to packages.playwright-core.src.client.network can't break packages.playwright-core.src.client.channelOwner.
Position
Below the diagonal: packages.playwright-core.src.client.network uses a module listed above it, which is the healthy direction.
13→17 packages.playwright-core.src.client.network uses packages.playwright-core.src.client.fetchpart of a loop✕
Connections
1 pair of types, where a type in packages.playwright-core.src.client.network uses a type in packages.playwright-core.src.client.fetch.
packages.playwright-core.src.client.network uses packages.playwright-core.src.client.fetch, so a change to packages.playwright-core.src.client.fetch can break packages.playwright-core.src.client.network, while a change to packages.playwright-core.src.client.network can't break packages.playwright-core.src.client.fetch.
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.
13→18 packages.playwright-core.src.client.network uses packages.playwright-core.src.client.pagepart of a loop✕
Connections
1 pair of types, where a type in packages.playwright-core.src.client.network uses a type in packages.playwright-core.src.client.page.
packages.playwright-core.src.client.network uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.client.network, while a change to packages.playwright-core.src.client.network can't break packages.playwright-core.src.client.page.
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.
packages.playwright-core.src.client.playwright uses packages.injected.src.webSocketMock, so a change to packages.injected.src.webSocketMock can break packages.playwright-core.src.client.playwright, while a change to packages.playwright-core.src.client.playwright can't break packages.injected.src.webSocketMock.
Position
Below the diagonal: packages.playwright-core.src.client.playwright uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.playwright uses packages.playwright-core.src.client.channelOwner, so a change to packages.playwright-core.src.client.channelOwner can break packages.playwright-core.src.client.playwright, while a change to packages.playwright-core.src.client.playwright can't break packages.playwright-core.src.client.channelOwner.
Position
Below the diagonal: packages.playwright-core.src.client.playwright uses a module listed above it, which is the healthy direction.
14→15 packages.playwright-core.src.client.playwright uses packages.playwright-core.src.client.browserTypepart of a loop✕
Connections
1 pair of types, where a type in packages.playwright-core.src.client.playwright uses a type in packages.playwright-core.src.client.browserType.
packages.playwright-core.src.client.playwright uses packages.playwright-core.src.client.browserType, so a change to packages.playwright-core.src.client.browserType can break packages.playwright-core.src.client.playwright, while a change to packages.playwright-core.src.client.playwright can't break packages.playwright-core.src.client.browserType.
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→19 packages.playwright-core.src.client.playwright uses packages.playwright-core.src.client.browserpart of a loop✕
Connections
1 pair of types, where a type in packages.playwright-core.src.client.playwright uses a type in packages.playwright-core.src.client.browser.
packages.playwright-core.src.client.playwright uses packages.playwright-core.src.client.browser, so a change to packages.playwright-core.src.client.browser can break packages.playwright-core.src.client.playwright, while a change to packages.playwright-core.src.client.playwright can't break packages.playwright-core.src.client.browser.
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.
packages.playwright-core.src.client.browserType uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.client.browserType, while a change to packages.playwright-core.src.client.browserType can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.client.browserType uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browserType uses packages.playwright-core.src.client.channelOwner, so a change to packages.playwright-core.src.client.channelOwner can break packages.playwright-core.src.client.browserType, while a change to packages.playwright-core.src.client.browserType can't break packages.playwright-core.src.client.channelOwner.
Position
Below the diagonal: packages.playwright-core.src.client.browserType uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browserType uses packages.playwright-core.src.client.playwright, so a change to packages.playwright-core.src.client.playwright can break packages.playwright-core.src.client.browserType, while a change to packages.playwright-core.src.client.browserType can't break packages.playwright-core.src.client.playwright.
Position
Below the diagonal: packages.playwright-core.src.client.browserType uses a module listed above it, which is the healthy direction.
15→19 packages.playwright-core.src.client.browserType uses packages.playwright-core.src.client.browserpart of a loop✕
Connections
1 pair of types, where a type in packages.playwright-core.src.client.browserType uses a type in packages.playwright-core.src.client.browser.
packages.playwright-core.src.client.browserType uses packages.playwright-core.src.client.browser, so a change to packages.playwright-core.src.client.browser can break packages.playwright-core.src.client.browserType, while a change to packages.playwright-core.src.client.browserType can't break packages.playwright-core.src.client.browser.
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.
packages.playwright-core.src.client.elementHandle uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.client.elementHandle, while a change to packages.playwright-core.src.client.elementHandle can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.client.elementHandle uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.elementHandle uses packages.playwright-core.src.client.channelOwner, so a change to packages.playwright-core.src.client.channelOwner can break packages.playwright-core.src.client.elementHandle, while a change to packages.playwright-core.src.client.elementHandle can't break packages.playwright-core.src.client.channelOwner.
Position
Below the diagonal: packages.playwright-core.src.client.elementHandle uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.elementHandle uses packages.playwright-core.src.client.jsHandle, so a change to packages.playwright-core.src.client.jsHandle can break packages.playwright-core.src.client.elementHandle, while a change to packages.playwright-core.src.client.elementHandle can't break packages.playwright-core.src.client.jsHandle.
Position
Below the diagonal: packages.playwright-core.src.client.elementHandle uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.fetch uses packages.injected.src.webSocketMock, so a change to packages.injected.src.webSocketMock can break packages.playwright-core.src.client.fetch, while a change to packages.playwright-core.src.client.fetch can't break packages.injected.src.webSocketMock.
Position
Below the diagonal: packages.playwright-core.src.client.fetch uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.fetch uses packages.isomorphic.types, so a change to packages.isomorphic.types can break packages.playwright-core.src.client.fetch, while a change to packages.playwright-core.src.client.fetch can't break packages.isomorphic.types.
Position
Below the diagonal: packages.playwright-core.src.client.fetch uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.fetch uses packages.playwright-core.src.client.channelOwner, so a change to packages.playwright-core.src.client.channelOwner can break packages.playwright-core.src.client.fetch, while a change to packages.playwright-core.src.client.fetch can't break packages.playwright-core.src.client.channelOwner.
Position
Below the diagonal: packages.playwright-core.src.client.fetch uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.fetch uses packages.playwright-core.src.client.network, so a change to packages.playwright-core.src.client.network can break packages.playwright-core.src.client.fetch, while a change to packages.playwright-core.src.client.fetch can't break packages.playwright-core.src.client.network.
Position
Below the diagonal: packages.playwright-core.src.client.fetch uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.fetch uses packages.playwright-core.src.client.playwright, so a change to packages.playwright-core.src.client.playwright can break packages.playwright-core.src.client.fetch, while a change to packages.playwright-core.src.client.fetch can't break packages.playwright-core.src.client.playwright.
Position
Below the diagonal: packages.playwright-core.src.client.fetch uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.page uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.client.page, while a change to packages.playwright-core.src.client.page can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.client.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.page uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.client.page, while a change to packages.playwright-core.src.client.page can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.client.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.page uses packages.playwright-core.src.server.types, so a change to packages.playwright-core.src.server.types can break packages.playwright-core.src.client.page, while a change to packages.playwright-core.src.client.page can't break packages.playwright-core.src.server.types.
Position
Below the diagonal: packages.playwright-core.src.client.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.page uses packages.playwright-core.src.client.channelOwner, so a change to packages.playwright-core.src.client.channelOwner can break packages.playwright-core.src.client.page, while a change to packages.playwright-core.src.client.page can't break packages.playwright-core.src.client.channelOwner.
Position
Below the diagonal: packages.playwright-core.src.client.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.page uses packages.playwright-core.src.client.jsHandle, so a change to packages.playwright-core.src.client.jsHandle can break packages.playwright-core.src.client.page, while a change to packages.playwright-core.src.client.page can't break packages.playwright-core.src.client.jsHandle.
Position
Below the diagonal: packages.playwright-core.src.client.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.page uses packages.playwright-core.src.client.network, so a change to packages.playwright-core.src.client.network can break packages.playwright-core.src.client.page, while a change to packages.playwright-core.src.client.page can't break packages.playwright-core.src.client.network.
Position
Below the diagonal: packages.playwright-core.src.client.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.page uses packages.playwright-core.src.client.elementHandle, so a change to packages.playwright-core.src.client.elementHandle can break packages.playwright-core.src.client.page, while a change to packages.playwright-core.src.client.page can't break packages.playwright-core.src.client.elementHandle.
Position
Below the diagonal: packages.playwright-core.src.client.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.page uses packages.playwright-core.src.client.fetch, so a change to packages.playwright-core.src.client.fetch can break packages.playwright-core.src.client.page, while a change to packages.playwright-core.src.client.page can't break packages.playwright-core.src.client.fetch.
Position
Below the diagonal: packages.playwright-core.src.client.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browser uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.client.browser, while a change to packages.playwright-core.src.client.browser can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.client.browser uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browser uses packages.playwright-core.src.client.channelOwner, so a change to packages.playwright-core.src.client.channelOwner can break packages.playwright-core.src.client.browser, while a change to packages.playwright-core.src.client.browser can't break packages.playwright-core.src.client.channelOwner.
Position
Below the diagonal: packages.playwright-core.src.client.browser uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browser uses packages.playwright-core.src.client.browserType, so a change to packages.playwright-core.src.client.browserType can break packages.playwright-core.src.client.browser, while a change to packages.playwright-core.src.client.browser can't break packages.playwright-core.src.client.browserType.
Position
Below the diagonal: packages.playwright-core.src.client.browser uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browser uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.client.browser, while a change to packages.playwright-core.src.client.browser can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.client.browser uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browserContext uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.client.browserContext, while a change to packages.playwright-core.src.client.browserContext can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.client.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browserContext uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.client.browserContext, while a change to packages.playwright-core.src.client.browserContext can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.client.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browserContext uses packages.playwright-core.src.client.channelOwner, so a change to packages.playwright-core.src.client.channelOwner can break packages.playwright-core.src.client.browserContext, while a change to packages.playwright-core.src.client.browserContext can't break packages.playwright-core.src.client.channelOwner.
Position
Below the diagonal: packages.playwright-core.src.client.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browserContext uses packages.playwright-core.src.client.network, so a change to packages.playwright-core.src.client.network can break packages.playwright-core.src.client.browserContext, while a change to packages.playwright-core.src.client.browserContext can't break packages.playwright-core.src.client.network.
Position
Below the diagonal: packages.playwright-core.src.client.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browserContext uses packages.playwright-core.src.client.fetch, so a change to packages.playwright-core.src.client.fetch can break packages.playwright-core.src.client.browserContext, while a change to packages.playwright-core.src.client.browserContext can't break packages.playwright-core.src.client.fetch.
Position
Below the diagonal: packages.playwright-core.src.client.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client.browserContext uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.client.browserContext, while a change to packages.playwright-core.src.client.browserContext can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.client.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.tools.backend.tab uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.tools.backend.tab, while a change to packages.playwright-core.src.tools.backend.tab can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.tools.backend.tab uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.tools.backend.tab uses packages.playwright-core.src.client.eventEmitter, so a change to packages.playwright-core.src.client.eventEmitter can break packages.playwright-core.src.tools.backend.tab, while a change to packages.playwright-core.src.tools.backend.tab can't break packages.playwright-core.src.client.eventEmitter.
Position
Below the diagonal: packages.playwright-core.src.tools.backend.tab uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.tools.backend.tab uses packages.playwright-core.src.client.network, so a change to packages.playwright-core.src.client.network can break packages.playwright-core.src.tools.backend.tab, while a change to packages.playwright-core.src.tools.backend.tab can't break packages.playwright-core.src.client.network.
Position
Below the diagonal: packages.playwright-core.src.tools.backend.tab uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.tools.backend.tab uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.tools.backend.tab, while a change to packages.playwright-core.src.tools.backend.tab can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.tools.backend.tab uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.client, while a change to packages.playwright-core.src.client can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.client uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client uses packages.isomorphic.types, so a change to packages.isomorphic.types can break packages.playwright-core.src.client, while a change to packages.playwright-core.src.client can't break packages.isomorphic.types.
Position
Below the diagonal: packages.playwright-core.src.client uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client uses packages.playwright-core.src.client.eventEmitter, so a change to packages.playwright-core.src.client.eventEmitter can break packages.playwright-core.src.client, while a change to packages.playwright-core.src.client can't break packages.playwright-core.src.client.eventEmitter.
Position
Below the diagonal: packages.playwright-core.src.client uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client uses packages.playwright-core.src.server.types, so a change to packages.playwright-core.src.server.types can break packages.playwright-core.src.client, while a change to packages.playwright-core.src.client can't break packages.playwright-core.src.server.types.
Position
Below the diagonal: packages.playwright-core.src.client uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client uses packages.playwright-core.src.client.channelOwner, so a change to packages.playwright-core.src.client.channelOwner can break packages.playwright-core.src.client, while a change to packages.playwright-core.src.client can't break packages.playwright-core.src.client.channelOwner.
Position
Below the diagonal: packages.playwright-core.src.client uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client uses packages.playwright-core.src.client.playwright, so a change to packages.playwright-core.src.client.playwright can break packages.playwright-core.src.client, while a change to packages.playwright-core.src.client can't break packages.playwright-core.src.client.playwright.
Position
Below the diagonal: packages.playwright-core.src.client uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.client uses packages.playwright-core.src.client.browser, so a change to packages.playwright-core.src.client.browser can break packages.playwright-core.src.client, while a change to packages.playwright-core.src.client can't break packages.playwright-core.src.client.browser.
Position
Below the diagonal: packages.playwright-core.src.client uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.instrumentation uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.server.instrumentation, while a change to packages.playwright-core.src.server.instrumentation can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.server.instrumentation uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.instrumentation uses packages.playwright-core.src.client.eventEmitter, so a change to packages.playwright-core.src.client.eventEmitter can break packages.playwright-core.src.server.instrumentation, while a change to packages.playwright-core.src.server.instrumentation can't break packages.playwright-core.src.client.eventEmitter.
Position
Below the diagonal: packages.playwright-core.src.server.instrumentation uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.instrumentation uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.instrumentation, while a change to packages.playwright-core.src.server.instrumentation can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.instrumentation uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.instrumentation uses packages.playwright-core.src.client.browser, so a change to packages.playwright-core.src.client.browser can break packages.playwright-core.src.server.instrumentation, while a change to packages.playwright-core.src.server.instrumentation can't break packages.playwright-core.src.client.browser.
Position
Below the diagonal: packages.playwright-core.src.server.instrumentation uses a module listed above it, which is the healthy direction.
23→24 packages.playwright-core.src.server.instrumentation uses packages.playwright-core.src.server.progresspart of a loop✕
Connections
2 pairs of types, where a type in packages.playwright-core.src.server.instrumentation uses a type in packages.playwright-core.src.server.progress.
packages.playwright-core.src.server.instrumentation uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.instrumentation, while a change to packages.playwright-core.src.server.instrumentation can't break packages.playwright-core.src.server.progress.
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.
packages.playwright-core.src.server.progress uses packages.playwright-core.src.server.instrumentation, so a change to packages.playwright-core.src.server.instrumentation can break packages.playwright-core.src.server.progress, while a change to packages.playwright-core.src.server.progress can't break packages.playwright-core.src.server.instrumentation.
Position
Below the diagonal: packages.playwright-core.src.server.progress uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses a type in browser_patches.firefox.juggler.TargetRegistry.
packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.server.dispatchers.browserContextDispatcher, while a change to packages.playwright-core.src.server.dispatchers.browserContextDispatcher can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses a type in browser_patches.firefox.juggler.protocol.Dispatcher.
packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses browser_patches.firefox.juggler.protocol.Dispatcher, so a change to browser_patches.firefox.juggler.protocol.Dispatcher can break packages.playwright-core.src.server.dispatchers.browserContextDispatcher, while a change to packages.playwright-core.src.server.dispatchers.browserContextDispatcher can't break browser_patches.firefox.juggler.protocol.Dispatcher.
Position
Below the diagonal: packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses a type in packages.playwright-core.src.client.network.
packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses packages.playwright-core.src.client.network, so a change to packages.playwright-core.src.client.network can break packages.playwright-core.src.server.dispatchers.browserContextDispatcher, while a change to packages.playwright-core.src.server.dispatchers.browserContextDispatcher can't break packages.playwright-core.src.client.network.
Position
Below the diagonal: packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses a type in packages.playwright-core.src.server.progress.
packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.dispatchers.browserContextDispatcher, while a change to packages.playwright-core.src.server.dispatchers.browserContextDispatcher can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.dispatchers.browserContextDispatcher uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.dispatchers.dispatcher uses a type in browser_patches.firefox.juggler.protocol.Dispatcher.
packages.playwright-core.src.server.dispatchers.dispatcher uses browser_patches.firefox.juggler.protocol.Dispatcher, so a change to browser_patches.firefox.juggler.protocol.Dispatcher can break packages.playwright-core.src.server.dispatchers.dispatcher, while a change to packages.playwright-core.src.server.dispatchers.dispatcher can't break browser_patches.firefox.juggler.protocol.Dispatcher.
Position
Below the diagonal: packages.playwright-core.src.server.dispatchers.dispatcher uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.dispatchers.dispatcher uses a type in packages.playwright-core.src.client.eventEmitter.
packages.playwright-core.src.server.dispatchers.dispatcher uses packages.playwright-core.src.client.eventEmitter, so a change to packages.playwright-core.src.client.eventEmitter can break packages.playwright-core.src.server.dispatchers.dispatcher, while a change to packages.playwright-core.src.server.dispatchers.dispatcher can't break packages.playwright-core.src.client.eventEmitter.
Position
Below the diagonal: packages.playwright-core.src.server.dispatchers.dispatcher uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.dispatchers.dispatcher uses a type in packages.playwright-core.src.server.instrumentation.
packages.playwright-core.src.server.dispatchers.dispatcher uses packages.playwright-core.src.server.instrumentation, so a change to packages.playwright-core.src.server.instrumentation can break packages.playwright-core.src.server.dispatchers.dispatcher, while a change to packages.playwright-core.src.server.dispatchers.dispatcher can't break packages.playwright-core.src.server.instrumentation.
Position
Below the diagonal: packages.playwright-core.src.server.dispatchers.dispatcher uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.playwright-core.src.server.dispatchers.dispatcher uses a type in packages.playwright-core.src.server.progress.
packages.playwright-core.src.server.dispatchers.dispatcher uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.dispatchers.dispatcher, while a change to packages.playwright-core.src.server.dispatchers.dispatcher can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.dispatchers.dispatcher uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.dom uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.server.dom, while a change to packages.playwright-core.src.server.dom can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.server.dom uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.dom uses packages.injected.src.injectedScript, so a change to packages.injected.src.injectedScript can break packages.playwright-core.src.server.dom, while a change to packages.playwright-core.src.server.dom can't break packages.injected.src.injectedScript.
Position
Below the diagonal: packages.playwright-core.src.server.dom uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.dom uses packages.playwright-core.src.client.jsHandle, so a change to packages.playwright-core.src.client.jsHandle can break packages.playwright-core.src.server.dom, while a change to packages.playwright-core.src.server.dom can't break packages.playwright-core.src.client.jsHandle.
Position
Below the diagonal: packages.playwright-core.src.server.dom uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.dom uses packages.playwright-core.src.client.elementHandle, so a change to packages.playwright-core.src.client.elementHandle can break packages.playwright-core.src.server.dom, while a change to packages.playwright-core.src.server.dom can't break packages.playwright-core.src.client.elementHandle.
Position
Below the diagonal: packages.playwright-core.src.server.dom uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.dom uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.dom, while a change to packages.playwright-core.src.server.dom can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.dom uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.dom uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.dom, while a change to packages.playwright-core.src.server.dom can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.dom uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.recorder uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.server.recorder, while a change to packages.playwright-core.src.server.recorder can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.server.recorder uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.recorder uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.server.recorder, while a change to packages.playwright-core.src.server.recorder can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.server.recorder uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.recorder uses packages.playwright-core.src.client.eventEmitter, so a change to packages.playwright-core.src.client.eventEmitter can break packages.playwright-core.src.server.recorder, while a change to packages.playwright-core.src.server.recorder can't break packages.playwright-core.src.client.eventEmitter.
Position
Below the diagonal: packages.playwright-core.src.server.recorder uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.recorder uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.recorder, while a change to packages.playwright-core.src.server.recorder can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.recorder uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.recorder uses packages.playwright-core.src.server.instrumentation, so a change to packages.playwright-core.src.server.instrumentation can break packages.playwright-core.src.server.recorder, while a change to packages.playwright-core.src.server.recorder can't break packages.playwright-core.src.server.instrumentation.
Position
Below the diagonal: packages.playwright-core.src.server.recorder uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.recorder uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.recorder, while a change to packages.playwright-core.src.server.recorder can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.recorder uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.transport uses packages.injected.src.webSocketMock, so a change to packages.injected.src.webSocketMock can break packages.playwright-core.src.server.transport, while a change to packages.playwright-core.src.server.transport can't break packages.injected.src.webSocketMock.
Position
Below the diagonal: packages.playwright-core.src.server.transport uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.transport uses packages.isomorphic.types, so a change to packages.isomorphic.types can break packages.playwright-core.src.server.transport, while a change to packages.playwright-core.src.server.transport can't break packages.isomorphic.types.
Position
Below the diagonal: packages.playwright-core.src.server.transport uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.transport uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.transport, while a change to packages.playwright-core.src.server.transport can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.transport uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.server, while a change to packages.playwright-core.src.server can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.server uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server uses browser_patches.firefox.juggler.content.Runtime, so a change to browser_patches.firefox.juggler.content.Runtime can break packages.playwright-core.src.server, while a change to packages.playwright-core.src.server can't break browser_patches.firefox.juggler.content.Runtime.
Position
Below the diagonal: packages.playwright-core.src.server uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server uses packages.isomorphic.types, so a change to packages.isomorphic.types can break packages.playwright-core.src.server, while a change to packages.playwright-core.src.server can't break packages.isomorphic.types.
Position
Below the diagonal: packages.playwright-core.src.server uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server uses packages.playwright-core.src.server.types, so a change to packages.playwright-core.src.server.types can break packages.playwright-core.src.server, while a change to packages.playwright-core.src.server can't break packages.playwright-core.src.server.types.
Position
Below the diagonal: packages.playwright-core.src.server uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server uses packages.playwright-core.src.client.browserType, so a change to packages.playwright-core.src.client.browserType can break packages.playwright-core.src.server, while a change to packages.playwright-core.src.server can't break packages.playwright-core.src.client.browserType.
Position
Below the diagonal: packages.playwright-core.src.server uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server uses packages.playwright-core.src.client.elementHandle, so a change to packages.playwright-core.src.client.elementHandle can break packages.playwright-core.src.server, while a change to packages.playwright-core.src.server can't break packages.playwright-core.src.client.elementHandle.
Position
Below the diagonal: packages.playwright-core.src.server uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server, while a change to packages.playwright-core.src.server can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server uses packages.playwright-core.src.server.instrumentation, so a change to packages.playwright-core.src.server.instrumentation can break packages.playwright-core.src.server, while a change to packages.playwright-core.src.server can't break packages.playwright-core.src.server.instrumentation.
Position
Below the diagonal: packages.playwright-core.src.server uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server, while a change to packages.playwright-core.src.server can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server uses packages.playwright-core.src.server.dom, so a change to packages.playwright-core.src.server.dom can break packages.playwright-core.src.server, while a change to packages.playwright-core.src.server can't break packages.playwright-core.src.server.dom.
Position
Below the diagonal: packages.playwright-core.src.server uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in packages.playwright-core.src.server.chromium.crConnection uses a type in packages.playwright-core.src.server.instrumentation.
packages.playwright-core.src.server.chromium.crConnection uses packages.playwright-core.src.server.instrumentation, so a change to packages.playwright-core.src.server.instrumentation can break packages.playwright-core.src.server.chromium.crConnection, while a change to packages.playwright-core.src.server.chromium.crConnection can't break packages.playwright-core.src.server.instrumentation.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crConnection uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.chromium.crConnection uses a type in packages.playwright-core.src.server.progress.
packages.playwright-core.src.server.chromium.crConnection uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.chromium.crConnection, while a change to packages.playwright-core.src.server.chromium.crConnection can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crConnection uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.chromium.crConnection uses a type in packages.playwright-core.src.server.transport.
packages.playwright-core.src.server.chromium.crConnection uses packages.playwright-core.src.server.transport, so a change to packages.playwright-core.src.server.transport can break packages.playwright-core.src.server.chromium.crConnection, while a change to packages.playwright-core.src.server.chromium.crConnection can't break packages.playwright-core.src.server.transport.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crConnection uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.frames uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.server.frames, while a change to packages.playwright-core.src.server.frames can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.server.frames uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.frames uses packages.playwright-core.src.server.types, so a change to packages.playwright-core.src.server.types can break packages.playwright-core.src.server.frames, while a change to packages.playwright-core.src.server.frames can't break packages.playwright-core.src.server.types.
Position
Below the diagonal: packages.playwright-core.src.server.frames uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.frames uses packages.playwright-core.src.client.jsHandle, so a change to packages.playwright-core.src.client.jsHandle can break packages.playwright-core.src.server.frames, while a change to packages.playwright-core.src.server.frames can't break packages.playwright-core.src.client.jsHandle.
Position
Below the diagonal: packages.playwright-core.src.server.frames uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.frames uses packages.playwright-core.src.client.network, so a change to packages.playwright-core.src.client.network can break packages.playwright-core.src.server.frames, while a change to packages.playwright-core.src.server.frames can't break packages.playwright-core.src.client.network.
Position
Below the diagonal: packages.playwright-core.src.server.frames uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.frames uses packages.playwright-core.src.client.elementHandle, so a change to packages.playwright-core.src.client.elementHandle can break packages.playwright-core.src.server.frames, while a change to packages.playwright-core.src.server.frames can't break packages.playwright-core.src.client.elementHandle.
Position
Below the diagonal: packages.playwright-core.src.server.frames uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.frames uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.frames, while a change to packages.playwright-core.src.server.frames can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.frames uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.frames uses packages.playwright-core.src.server.instrumentation, so a change to packages.playwright-core.src.server.instrumentation can break packages.playwright-core.src.server.frames, while a change to packages.playwright-core.src.server.frames can't break packages.playwright-core.src.server.instrumentation.
Position
Below the diagonal: packages.playwright-core.src.server.frames uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.frames uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.frames, while a change to packages.playwright-core.src.server.frames can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.frames uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.frames uses packages.playwright-core.src.server.dom, so a change to packages.playwright-core.src.server.dom can break packages.playwright-core.src.server.frames, while a change to packages.playwright-core.src.server.frames can't break packages.playwright-core.src.server.dom.
Position
Below the diagonal: packages.playwright-core.src.server.frames uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses browser_patches.firefox.juggler.content.Runtime, so a change to browser_patches.firefox.juggler.content.Runtime can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break browser_patches.firefox.juggler.content.Runtime.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses packages.isomorphic.types, so a change to packages.isomorphic.types can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break packages.isomorphic.types.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses packages.playwright-core.src.server.types, so a change to packages.playwright-core.src.server.types can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break packages.playwright-core.src.server.types.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses packages.playwright-core.src.client.network, so a change to packages.playwright-core.src.client.network can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break packages.playwright-core.src.client.network.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses packages.playwright-core.src.client.elementHandle, so a change to packages.playwright-core.src.client.elementHandle can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break packages.playwright-core.src.client.elementHandle.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses packages.playwright-core.src.server.instrumentation, so a change to packages.playwright-core.src.server.instrumentation can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break packages.playwright-core.src.server.instrumentation.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses packages.playwright-core.src.server.dom, so a change to packages.playwright-core.src.server.dom can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break packages.playwright-core.src.server.dom.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.page uses packages.playwright-core.src.server.frames, so a change to packages.playwright-core.src.server.frames can break packages.playwright-core.src.server.page, while a change to packages.playwright-core.src.server.page can't break packages.playwright-core.src.server.frames.
Position
Below the diagonal: packages.playwright-core.src.server.page uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.bidi.bidiPage uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.server.bidi.bidiPage, while a change to packages.playwright-core.src.server.bidi.bidiPage can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.server.bidi.bidiPage uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in packages.playwright-core.src.server.bidi.bidiPage uses a type in packages.playwright-core.src.server.bidi.third_party.bidiProtocolCore.
packages.playwright-core.src.server.bidi.bidiPage uses packages.playwright-core.src.server.bidi.third_party.bidiProtocolCore, so a change to packages.playwright-core.src.server.bidi.third_party.bidiProtocolCore can break packages.playwright-core.src.server.bidi.bidiPage, while a change to packages.playwright-core.src.server.bidi.bidiPage can't break packages.playwright-core.src.server.bidi.third_party.bidiProtocolCore.
Position
Below the diagonal: packages.playwright-core.src.server.bidi.bidiPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.bidi.bidiPage uses packages.playwright-core.src.client.elementHandle, so a change to packages.playwright-core.src.client.elementHandle can break packages.playwright-core.src.server.bidi.bidiPage, while a change to packages.playwright-core.src.server.bidi.bidiPage can't break packages.playwright-core.src.client.elementHandle.
Position
Below the diagonal: packages.playwright-core.src.server.bidi.bidiPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.bidi.bidiPage uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.bidi.bidiPage, while a change to packages.playwright-core.src.server.bidi.bidiPage can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.bidi.bidiPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.bidi.bidiPage uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.bidi.bidiPage, while a change to packages.playwright-core.src.server.bidi.bidiPage can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.bidi.bidiPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.bidi.bidiPage uses packages.playwright-core.src.server.dom, so a change to packages.playwright-core.src.server.dom can break packages.playwright-core.src.server.bidi.bidiPage, while a change to packages.playwright-core.src.server.bidi.bidiPage can't break packages.playwright-core.src.server.dom.
Position
Below the diagonal: packages.playwright-core.src.server.bidi.bidiPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.bidi.bidiPage uses packages.playwright-core.src.server.page, so a change to packages.playwright-core.src.server.page can break packages.playwright-core.src.server.bidi.bidiPage, while a change to packages.playwright-core.src.server.bidi.bidiPage can't break packages.playwright-core.src.server.page.
Position
Below the diagonal: packages.playwright-core.src.server.bidi.bidiPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.browserContext uses packages.isomorphic.types, so a change to packages.isomorphic.types can break packages.playwright-core.src.server.browserContext, while a change to packages.playwright-core.src.server.browserContext can't break packages.isomorphic.types.
Position
Below the diagonal: packages.playwright-core.src.server.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.browserContext uses packages.playwright-core.src.server.types, so a change to packages.playwright-core.src.server.types can break packages.playwright-core.src.server.browserContext, while a change to packages.playwright-core.src.server.browserContext can't break packages.playwright-core.src.server.types.
Position
Below the diagonal: packages.playwright-core.src.server.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.browserContext uses packages.playwright-core.src.client.network, so a change to packages.playwright-core.src.client.network can break packages.playwright-core.src.server.browserContext, while a change to packages.playwright-core.src.server.browserContext can't break packages.playwright-core.src.client.network.
Position
Below the diagonal: packages.playwright-core.src.server.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.browserContext uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.browserContext, while a change to packages.playwright-core.src.server.browserContext can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.browserContext uses packages.playwright-core.src.client.browser, so a change to packages.playwright-core.src.client.browser can break packages.playwright-core.src.server.browserContext, while a change to packages.playwright-core.src.server.browserContext can't break packages.playwright-core.src.client.browser.
Position
Below the diagonal: packages.playwright-core.src.server.browserContext uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.browserContext uses a type in packages.playwright-core.src.server.instrumentation.
packages.playwright-core.src.server.browserContext uses packages.playwright-core.src.server.instrumentation, so a change to packages.playwright-core.src.server.instrumentation can break packages.playwright-core.src.server.browserContext, while a change to packages.playwright-core.src.server.browserContext can't break packages.playwright-core.src.server.instrumentation.
Position
Below the diagonal: packages.playwright-core.src.server.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.browserContext uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.browserContext, while a change to packages.playwright-core.src.server.browserContext can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.browserContext uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.browserContext uses packages.playwright-core.src.server.page, so a change to packages.playwright-core.src.server.page can break packages.playwright-core.src.server.browserContext, while a change to packages.playwright-core.src.server.browserContext can't break packages.playwright-core.src.server.page.
Position
Below the diagonal: packages.playwright-core.src.server.browserContext uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in packages.playwright-core.src.server.chromium.crPage uses a type in browser_patches.firefox.juggler.content.FrameTree.
packages.playwright-core.src.server.chromium.crPage uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.server.chromium.crPage, while a change to packages.playwright-core.src.server.chromium.crPage can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.chromium.crPage uses packages.playwright-core.src.server.types, so a change to packages.playwright-core.src.server.types can break packages.playwright-core.src.server.chromium.crPage, while a change to packages.playwright-core.src.server.chromium.crPage can't break packages.playwright-core.src.server.types.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crPage uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.playwright-core.src.server.chromium.crPage uses a type in packages.playwright-core.src.client.elementHandle.
packages.playwright-core.src.server.chromium.crPage uses packages.playwright-core.src.client.elementHandle, so a change to packages.playwright-core.src.client.elementHandle can break packages.playwright-core.src.server.chromium.crPage, while a change to packages.playwright-core.src.server.chromium.crPage can't break packages.playwright-core.src.client.elementHandle.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.chromium.crPage uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.chromium.crPage, while a change to packages.playwright-core.src.server.chromium.crPage can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.chromium.crPage uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.chromium.crPage, while a change to packages.playwright-core.src.server.chromium.crPage can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.chromium.crPage uses packages.playwright-core.src.server.dom, so a change to packages.playwright-core.src.server.dom can break packages.playwright-core.src.server.chromium.crPage, while a change to packages.playwright-core.src.server.chromium.crPage can't break packages.playwright-core.src.server.dom.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crPage uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.playwright-core.src.server.chromium.crPage uses a type in packages.playwright-core.src.server.chromium.crConnection.
packages.playwright-core.src.server.chromium.crPage uses packages.playwright-core.src.server.chromium.crConnection, so a change to packages.playwright-core.src.server.chromium.crConnection can break packages.playwright-core.src.server.chromium.crPage, while a change to packages.playwright-core.src.server.chromium.crPage can't break packages.playwright-core.src.server.chromium.crConnection.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.chromium.crPage uses packages.playwright-core.src.server.page, so a change to packages.playwright-core.src.server.page can break packages.playwright-core.src.server.chromium.crPage, while a change to packages.playwright-core.src.server.chromium.crPage can't break packages.playwright-core.src.server.page.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crPage uses a module listed above it, which is the healthy direction.
36→40 packages.playwright-core.src.server.chromium.crPage uses packages.playwright-core.src.server.chromium.crBrowserpart of a loop✕
Connections
1 pair of types, where a type in packages.playwright-core.src.server.chromium.crPage uses a type in packages.playwright-core.src.server.chromium.crBrowser.
packages.playwright-core.src.server.chromium.crPage uses packages.playwright-core.src.server.chromium.crBrowser, so a change to packages.playwright-core.src.server.chromium.crBrowser can break packages.playwright-core.src.server.chromium.crPage, while a change to packages.playwright-core.src.server.chromium.crPage can't break packages.playwright-core.src.server.chromium.crBrowser.
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.
packages.playwright-core.src.server.firefox.ffPage uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.server.firefox.ffPage, while a change to packages.playwright-core.src.server.firefox.ffPage can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.server.firefox.ffPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.firefox.ffPage uses packages.isomorphic.types, so a change to packages.isomorphic.types can break packages.playwright-core.src.server.firefox.ffPage, while a change to packages.playwright-core.src.server.firefox.ffPage can't break packages.isomorphic.types.
Position
Below the diagonal: packages.playwright-core.src.server.firefox.ffPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.firefox.ffPage uses packages.playwright-core.src.client.elementHandle, so a change to packages.playwright-core.src.client.elementHandle can break packages.playwright-core.src.server.firefox.ffPage, while a change to packages.playwright-core.src.server.firefox.ffPage can't break packages.playwright-core.src.client.elementHandle.
Position
Below the diagonal: packages.playwright-core.src.server.firefox.ffPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.firefox.ffPage uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.firefox.ffPage, while a change to packages.playwright-core.src.server.firefox.ffPage can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.firefox.ffPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.firefox.ffPage uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.firefox.ffPage, while a change to packages.playwright-core.src.server.firefox.ffPage can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.firefox.ffPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.firefox.ffPage uses packages.playwright-core.src.server.dom, so a change to packages.playwright-core.src.server.dom can break packages.playwright-core.src.server.firefox.ffPage, while a change to packages.playwright-core.src.server.firefox.ffPage can't break packages.playwright-core.src.server.dom.
Position
Below the diagonal: packages.playwright-core.src.server.firefox.ffPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.firefox.ffPage uses packages.playwright-core.src.server.page, so a change to packages.playwright-core.src.server.page can break packages.playwright-core.src.server.firefox.ffPage, while a change to packages.playwright-core.src.server.firefox.ffPage can't break packages.playwright-core.src.server.page.
Position
Below the diagonal: packages.playwright-core.src.server.firefox.ffPage uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.webkit.webview.wvPage uses a type in browser_patches.firefox.juggler.content.FrameTree.
packages.playwright-core.src.server.webkit.webview.wvPage uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.server.webkit.webview.wvPage, while a change to packages.playwright-core.src.server.webkit.webview.wvPage can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.webview.wvPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.webview.wvPage uses packages.isomorphic.types, so a change to packages.isomorphic.types can break packages.playwright-core.src.server.webkit.webview.wvPage, while a change to packages.playwright-core.src.server.webkit.webview.wvPage can't break packages.isomorphic.types.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.webview.wvPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.webview.wvPage uses packages.playwright-core.src.server.types, so a change to packages.playwright-core.src.server.types can break packages.playwright-core.src.server.webkit.webview.wvPage, while a change to packages.playwright-core.src.server.webkit.webview.wvPage can't break packages.playwright-core.src.server.types.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.webview.wvPage uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.playwright-core.src.server.webkit.webview.wvPage uses a type in packages.playwright-core.src.client.network.
packages.playwright-core.src.server.webkit.webview.wvPage uses packages.playwright-core.src.client.network, so a change to packages.playwright-core.src.client.network can break packages.playwright-core.src.server.webkit.webview.wvPage, while a change to packages.playwright-core.src.server.webkit.webview.wvPage can't break packages.playwright-core.src.client.network.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.webview.wvPage uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.webkit.webview.wvPage uses a type in packages.playwright-core.src.client.elementHandle.
packages.playwright-core.src.server.webkit.webview.wvPage uses packages.playwright-core.src.client.elementHandle, so a change to packages.playwright-core.src.client.elementHandle can break packages.playwright-core.src.server.webkit.webview.wvPage, while a change to packages.playwright-core.src.server.webkit.webview.wvPage can't break packages.playwright-core.src.client.elementHandle.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.webview.wvPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.webview.wvPage uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.webkit.webview.wvPage, while a change to packages.playwright-core.src.server.webkit.webview.wvPage can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.webview.wvPage uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.webkit.webview.wvPage uses a type in packages.playwright-core.src.server.progress.
packages.playwright-core.src.server.webkit.webview.wvPage uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.webkit.webview.wvPage, while a change to packages.playwright-core.src.server.webkit.webview.wvPage can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.webview.wvPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.webview.wvPage uses packages.playwright-core.src.server.dom, so a change to packages.playwright-core.src.server.dom can break packages.playwright-core.src.server.webkit.webview.wvPage, while a change to packages.playwright-core.src.server.webkit.webview.wvPage can't break packages.playwright-core.src.server.dom.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.webview.wvPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.webview.wvPage uses packages.playwright-core.src.server.page, so a change to packages.playwright-core.src.server.page can break packages.playwright-core.src.server.webkit.webview.wvPage, while a change to packages.playwright-core.src.server.webkit.webview.wvPage can't break packages.playwright-core.src.server.page.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.webview.wvPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.wkPage uses browser_patches.firefox.juggler.content.FrameTree, so a change to browser_patches.firefox.juggler.content.FrameTree can break packages.playwright-core.src.server.webkit.wkPage, while a change to packages.playwright-core.src.server.webkit.wkPage can't break browser_patches.firefox.juggler.content.FrameTree.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.wkPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.wkPage uses packages.isomorphic.types, so a change to packages.isomorphic.types can break packages.playwright-core.src.server.webkit.wkPage, while a change to packages.playwright-core.src.server.webkit.wkPage can't break packages.isomorphic.types.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.wkPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.wkPage uses packages.playwright-core.src.server.types, so a change to packages.playwright-core.src.server.types can break packages.playwright-core.src.server.webkit.wkPage, while a change to packages.playwright-core.src.server.webkit.wkPage can't break packages.playwright-core.src.server.types.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.wkPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.wkPage uses packages.playwright-core.src.client.network, so a change to packages.playwright-core.src.client.network can break packages.playwright-core.src.server.webkit.wkPage, while a change to packages.playwright-core.src.server.webkit.wkPage can't break packages.playwright-core.src.client.network.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.wkPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.wkPage uses packages.playwright-core.src.client.elementHandle, so a change to packages.playwright-core.src.client.elementHandle can break packages.playwright-core.src.server.webkit.wkPage, while a change to packages.playwright-core.src.server.webkit.wkPage can't break packages.playwright-core.src.client.elementHandle.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.wkPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.wkPage uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.webkit.wkPage, while a change to packages.playwright-core.src.server.webkit.wkPage can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.wkPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.wkPage uses packages.playwright-core.src.server.progress, so a change to packages.playwright-core.src.server.progress can break packages.playwright-core.src.server.webkit.wkPage, while a change to packages.playwright-core.src.server.webkit.wkPage can't break packages.playwright-core.src.server.progress.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.wkPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.wkPage uses packages.playwright-core.src.server.dom, so a change to packages.playwright-core.src.server.dom can break packages.playwright-core.src.server.webkit.wkPage, while a change to packages.playwright-core.src.server.webkit.wkPage can't break packages.playwright-core.src.server.dom.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.wkPage uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.webkit.wkPage uses packages.playwright-core.src.server.page, so a change to packages.playwright-core.src.server.page can break packages.playwright-core.src.server.webkit.wkPage, while a change to packages.playwright-core.src.server.webkit.wkPage can't break packages.playwright-core.src.server.page.
Position
Below the diagonal: packages.playwright-core.src.server.webkit.wkPage uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.playwright-core.src.server.chromium.crBrowser uses a type in browser_patches.firefox.juggler.TargetRegistry.
packages.playwright-core.src.server.chromium.crBrowser uses browser_patches.firefox.juggler.TargetRegistry, so a change to browser_patches.firefox.juggler.TargetRegistry can break packages.playwright-core.src.server.chromium.crBrowser, while a change to packages.playwright-core.src.server.chromium.crBrowser can't break browser_patches.firefox.juggler.TargetRegistry.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crBrowser uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.chromium.crBrowser uses packages.playwright-core.src.client.page, so a change to packages.playwright-core.src.client.page can break packages.playwright-core.src.server.chromium.crBrowser, while a change to packages.playwright-core.src.server.chromium.crBrowser can't break packages.playwright-core.src.client.page.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crBrowser uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.chromium.crBrowser uses packages.playwright-core.src.client.browser, so a change to packages.playwright-core.src.client.browser can break packages.playwright-core.src.server.chromium.crBrowser, while a change to packages.playwright-core.src.server.chromium.crBrowser can't break packages.playwright-core.src.client.browser.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crBrowser uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.chromium.crBrowser uses a type in packages.playwright-core.src.server.instrumentation.
packages.playwright-core.src.server.chromium.crBrowser uses packages.playwright-core.src.server.instrumentation, so a change to packages.playwright-core.src.server.instrumentation can break packages.playwright-core.src.server.chromium.crBrowser, while a change to packages.playwright-core.src.server.chromium.crBrowser can't break packages.playwright-core.src.server.instrumentation.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crBrowser uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.chromium.crBrowser uses packages.playwright-core.src.server.transport, so a change to packages.playwright-core.src.server.transport can break packages.playwright-core.src.server.chromium.crBrowser, while a change to packages.playwright-core.src.server.chromium.crBrowser can't break packages.playwright-core.src.server.transport.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crBrowser uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.playwright-core.src.server.chromium.crBrowser uses a type in packages.playwright-core.src.server.chromium.crConnection.
packages.playwright-core.src.server.chromium.crBrowser uses packages.playwright-core.src.server.chromium.crConnection, so a change to packages.playwright-core.src.server.chromium.crConnection can break packages.playwright-core.src.server.chromium.crBrowser, while a change to packages.playwright-core.src.server.chromium.crBrowser can't break packages.playwright-core.src.server.chromium.crConnection.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crBrowser uses a module listed above it, which is the healthy direction.
packages.playwright-core.src.server.chromium.crBrowser uses packages.playwright-core.src.server.page, so a change to packages.playwright-core.src.server.page can break packages.playwright-core.src.server.chromium.crBrowser, while a change to packages.playwright-core.src.server.chromium.crBrowser can't break packages.playwright-core.src.server.page.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crBrowser uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.playwright-core.src.server.chromium.crBrowser uses a type in packages.playwright-core.src.server.chromium.crPage.
packages.playwright-core.src.server.chromium.crBrowser uses packages.playwright-core.src.server.chromium.crPage, so a change to packages.playwright-core.src.server.chromium.crPage can break packages.playwright-core.src.server.chromium.crBrowser, while a change to packages.playwright-core.src.server.chromium.crBrowser can't break packages.playwright-core.src.server.chromium.crPage.
Position
Below the diagonal: packages.playwright-core.src.server.chromium.crBrowser uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 66% · 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
A05:2025 — Injection
83
High / Critical
A02:2025 — Security Misconfiguration
24
High / Critical
A03:2025 — Software Supply Chain Failures
12
High / Critical
A07:2025 — Authentication Failures
3
High / Critical
Roadmap
Top priorities: Resolve the 39 No assertions (empty test) finding(s) in Test Quality — start with unroute-behavior.spec.ts (5), page-autowaiting-no-hang.spec.ts (4), page-history.spec.ts (3); Resolve the 645 Skipped test finding(s) in Test Quality — start with page-request-intercept.spec.ts (25), page-goto.spec.ts (18), page-request-fulfill.spec.ts (17); Resolve the 518 No assertions finding(s) in Test Quality — start with locator-parser.spec.ts (37), page-aria-snapshot.spec.ts (32), locator-generator.spec.ts (24).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 39 No assertions (empty test) finding(s) in Test Quality — start with unroute-behavior.spec.ts (5), page-autowaiting-no-hang.spec.ts (4), page-history.spec.ts (3).
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.
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.
Resolve the 645 Skipped test finding(s) in Test Quality — start with page-request-intercept.spec.ts (25), page-goto.spec.ts (18), page-request-fulfill.spec.ts (17).
Resolve the 518 No assertions finding(s) in Test Quality — start with locator-parser.spec.ts (37), page-aria-snapshot.spec.ts (32), locator-generator.spec.ts (24).
Test Quality: No assertions (empty test): NA-077 page.reload during renderer-initiated navigation
tests/library/heap.spec.ts
3.9
Slop
Test Quality: No assertions (empty test): LE-005 test #${i} to request page and context
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
tests/mcp/http.spec.ts
4.0
Mixed
Test Quality: No assertions (empty test): http transport browser sigint
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 — 97
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 — 2246
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 — 176
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 56 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 — 56 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, 2501 of 2519 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 — 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 repository declares 5 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.ts, .js, .mjs, .tsx), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'browser_patches/winldd/PrintDeps.vcxproj' because the file extension '.vcxproj' is not associated with a language.
D17 Explicit Debt — 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. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .ts (117,696 lines, 87% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 81 task marker(s) (TODO/FIXME/HACK/XXX) across 49 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D18 Solution Shape — evaluation did not complete — Dimension evaluation failed — excluded from the score.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — 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. 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D24 Comment Value — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/dashboard/src/sessionSidebar.tsx`, `packages/injected/src/utilityScript.ts`, `packages/isomorphic/trace/trace.ts`, `packages/playwright-core/src/browserServerImpl.ts`, `REDACTED`, … (+10 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXR1 Runtime accessibility — not measured this run — 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`) exited before it served a page. Likely cause (the repository): REDACTED has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
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.
P2 Observability — 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. 28 further occurrence(s) are not listed individually; the score already reflects all 68.
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. 320 further occurrence(s) are not listed individually; the score already reflects all 360.
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. 373 further occurrence(s) are not listed individually; the score already reflects all 413.
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. 52 further occurrence(s) are not listed individually; the score already reflects all 92.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 192 further occurrence(s) are not listed individually; the score already reflects all 232.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
X10 Duplicated predicate — 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. 37 further occurrence(s) are not listed individually; the score already reflects all 77.
X12 Unreachable branch — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
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.
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 REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
246 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was snapshotterInjected.frameSnapshotStreamer at 146. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being bidiDeserializer.deserializeBidiValue at 28 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: REDACTED (bidiDeserializer.deserializeBidiValue at 28), REDACTED (tab.consoleLevelForMessageType at 20), packages/playwright-core/src/server/dispatchers/webSocketRouteDispatcher.ts (WebSocketRouteDispatcher.install at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 204 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with snapshotterInjected.frameSnapshotStreamer (cyclomatic 146), roleUtils.getTextAlternativeInternal (cyclomatic 139), Streamer.captureSnapshot::visitNode (cyclomatic 92). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cyclomatic Complexity from 5.1 to about 6.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 254 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with generate_channels.generateChannels (cognitive 239), roleUtils.getTextAlternativeInternal (cognitive 236), snapshotterInjected.frameSnapshotStreamer (cognitive 179). — 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 3 together lifts Cognitive Complexity from 3.5 to about 4.6/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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 Classes7.5 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 37 TooManyMethods finding(s) in God Classes — start with page.ts (2), frames.ts (2), REDACTED (2). — One of this dimension's main actionable groups (37 warning-level).
Resolve the 30 FileTooLong finding(s) in God Classes — start with page.ts (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (30 warning-level).
Resolve the 29 FunctionTooLong finding(s) in God Classes — start with program.ts (3), snapshotterInjected.ts, uiModeView.tsx. — One of this dimension's main actionable groups (29 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.5 / 10Stronggated by 1 serious finding✓ 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.
17 production modules (Gradle+Maven+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 8 of the 17 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: playwright-core
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 18 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED, output.ts, page.ts. — One of this dimension's main actionable groups (18 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality7.4 / 10Adequategated by 39 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.
648 skipped (3 with a documented reason), 557 zero-assertion, 11 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8394 tests.
No assertions (empty test): LO-093 should wait for frame 2 · ×39tests/page/locator-frame.spec.ts:104
Resolve the 39 No assertions (empty test) finding(s) in Test Quality — start with unroute-behavior.spec.ts (5), page-autowaiting-no-hang.spec.ts (4), page-history.spec.ts (3). — One of this dimension's main actionable groups (39 issue-level).
Resolve the 645 Skipped test finding(s) in Test Quality — start with page-request-intercept.spec.ts (25), page-goto.spec.ts (18), page-request-fulfill.spec.ts (17). — One of this dimension's main actionable groups (645 warning-level).
Resolve the 518 No assertions finding(s) in Test Quality — start with locator-parser.spec.ts (37), page-aria-snapshot.spec.ts (32), locator-generator.spec.ts (24). — One of this dimension's main actionable groups (518 warning-level).
Detailed fixes: d10_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.
0 of 99 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 1 direct `PackageReference`(s), and 98 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares REDACTED, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
Top hotspots: packages/injected/src/roleUtils.ts (12×139=1668); REDACTED (25×40=1000); packages/playwright-core/src/server/fetch.ts (12×64=768) Repeated repair below the complexity floor: REDACTED (12 of 22 changes were fixes); REDACTED (10 of 19 changes were fixes); packages/playwright-core/src/server/chromium/chromiumSwitches.ts (9 of 13 changes were fixes)
Resolve the 44 Hotspot finding(s) in Churn × Complexity Hotspots — start with config.ts (2), program.ts (2), roleUtils.ts. — One of this dimension's main actionable groups (44 warning-level).
Resolve the 28 Repeated repair finding(s) in Churn × Complexity Hotspots — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (28 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 Factor9.6 / 10Exemplary✓ 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.
23 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is browser_patches/firefox/juggler/content/PageAgent.js. Counted over 563 of the 796 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 · ×3
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
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.
0 deducted debt markers + unmeasured dead symbols across 39 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .ts (87% of production source) was not read, and carries at least 81 uncounted task marker(s) in 49 file(s).
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 201 document(s) read across 18 unit(s).
Documentation: no build, run or usage example · ×7packages/playwright-browser-chromium/README.md:1
What to do
Resolve the 7 Documentation finding(s) in Documentation Quality — start with README.md (7). — One of this dimension's main actionable groups (7 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs foundutils/doclint/linting-code-snippets/csharp/linting-code-snippets.csproj:4
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with linting-code-snippets.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
6 naming inconsistencies among 479 declarations measured against a convention their peers follow.
`checkCdpMethod` spells `Cdp` where 21 names in the project spell it `CDP`packages/extension/src/cdpPolicy.ts:33
`AnchorID` spells `ID` where 412 names in the project spell it `Id`packages/html-reporter/src/links.tsx:190
`connectBidiOverCdp` spells `Cdp` where 21 names in the project spell it `CDP`packages/playwright-core/src/server/bidi/bidiOverCdp.ts:29
`_installMSEdgeChannel` spells `MS` where 25 names in the project spell it `Ms`packages/playwright-core/src/server/registry/index.ts:1142
`getFromENV` spells `ENV` where 20 names in the project spell it `Env`packages/utils/env.ts:17
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 `checkCdpMethod` spells `Cdp` where 21 names in the project spell it… finding(s) in Naming Consistency — start with cdpPolicy.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `AnchorID` spells `ID` where 412 names in the project spell it `Id` finding(s) in Naming Consistency — start with links.tsx. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `connectBidiOverCdp` spells `Cdp` where 21 names in the project spell it… finding(s) in Naming Consistency — start with bidiOverCdp.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
83 finding(s): 0 critical, 22 high, 59 medium, 2 low. semgrep hit a parse error in 22 file(s) — `packages/dashboard/src/sessionSidebar.tsx` (line 31), `packages/injected/src/utilityScript.ts` (line 62), `packages/isomorphic/trace/trace.ts` (line 17), `packages/playwright-core/src/browserServerImpl.ts` (line 51), `packages/playwright-core/src/server/android/driver/gradlew` (line 72, line 173), … (+17 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 9 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 14 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (6 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 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 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 18 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (6), REDACTED (6). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 6 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (6 issue-level).
Detailed fixes: d31_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.
16 of 563 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is utils/linux-browser-dependencies/inside_docker/list_dependencies.js. Counted over 563 of the 796 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 13 Boundary-crossing change coupling finding(s) in Change Coupling — start with REDACTED, locatorGenerators.ts, consoleApi.ts. — One of this dimension's main actionable groups (13 issue-level).
Resolve the 26 Change coupling finding(s) in Change Coupling — start with video.ts (2), locator.ts, androidServerImpl.ts. — One of this dimension's main actionable groups (26 warning-level).
Resolve the 4 Change-coupling hub finding(s) in Change Coupling — start with REDACTED, TargetRegistry.js, BrowserHandler.js. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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 3 platform declaration(s) and 3 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.
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 the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. 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.
`DashboardChannel` declares 26 required operations: `selectTab`, `closeTab`, `newTab`, `closeSession`, `setVisible`, `navigate`, `back`, `forward`, `reload`, `mousemove`, `mousedown`, `mouseup`, `wheel`, `keydown`, `keyup`, `startRecording`, `stopRecording`, `readStream`, `screenshot`, `submitAnnotation`, `cancelAnnotation`, `debuggerResume`, `debuggerPause`, `debuggerStep`, `on`, `off`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/dashboard/src/dashboardChannel.ts:77
`PageDelegate` declares 31 required operations: `reload`, `goBack`, `goForward`, `requestGC`, `addInitScript`, `removeInitScripts`, `closePage`, `navigateFrame`, `updateExtraHTTPHeaders`, `updateEmulatedViewportSize`, `updateEmulateMedia`, `updateRequestInterception`, `updateFileChooserInterception`, `bringToFront`, `setBackgroundColor`, `takeScreenshot`, `adoptElementHandle`, `getContentFrame`, `getOwnerFrame`, `getContentQuads`, `setInputFilePaths`, `getBoundingBox`, `getFrameElement`, `scrollRectIntoViewIfNeeded`, `startScreencast`, `stopScreencast`, `rafCountForStablePosition`, `inputActionEpilogue`, `resetForReuse`, `shouldToggleStyleSheetToSyncAnimations`, `setDockTile`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/playwright-core/src/server/page.ts:59
`Output` declares 22 required operations: `version`, `help`, `errorUnknownCommand`, `errorUnknownOption`, `errorTooManyArguments`, `errorAttachConflict`, `errorDetachNotAttached`, `errorBrowserNotOpenForTool`, `errorAttachNoTarget`, `errorInstallGlobalRequiresSkills`, `list`, `closeAll`, `deleteData`, `killAll`, `open`, `attach`, `close`, `detach`, `installed`, `show`, `toolResult`, `installStdio`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/playwright-core/src/tools/cli-client/output.ts:47
`TestServerInterface` declares 16 required operations: `initialize`, `ping`, `watch`, `open`, `resizeTerminal`, `checkBrowsers`, `installBrowsers`, `runGlobalSetup`, `runGlobalTeardown`, `clearCache`, `listFiles`, `listTests`, `runTests`, `findRelatedTestFiles`, `stopTests`, `closeGracefully`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/playwright/src/isomorphic/testServerInterface.ts:25
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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: shipped members still throwing NotImplementedException, and placeholder string literals left in 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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
docs/src/test-runners-csharp.md names .NET 10, but the projects target .NET 8. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/src/test-runners-csharp.md:389
tests/assets/modernizr/README.md links to `modernizr.com`, but `tests/assets/modernizr/modernizr.com` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tests/assets/modernizr/README.md:5
What to do
Reconcile the README with reality: docs/src/test-runners-csharp.md names .NET 10, but the projects target .NET 8; tests/assets/modernizr/README.md links to `modernizr.com`, but `tests/assets/modernizr/modernizr.com` does not exist.
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 · Observability6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 3/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/playwright-chromium`, `packages/playwright-firefox`, `packages/playwright-test`, `packages/playwright-webkit`, `utils/doclint/linting-code-snippets/java` and 1 more.
`utils/check_audit.js` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/check_audit.js:40
`utils/check_audit.js` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/check_audit.js:47
`utils/check_audit.js` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/check_audit.js:52
`utils/generate_chromium_default_font_families.js` reports through `console.*` at line 116 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/generate_chromium_default_font_families.js:116
`utils/video_stress.js` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/video_stress.js:5
`utils/video_stress.js` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/video_stress.js:12
`utils/video_stress.js` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/video_stress.js:14
`utils/protocol-types-generator/update-webview-protocol.js` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/protocol-types-generator/update-webview-protocol.js:56
`utils/protocol-types-generator/update-webview-protocol.js` reports through `console.*` at line 62 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/protocol-types-generator/update-webview-protocol.js:62
`utils/protocol-types-generator/update-webview-protocol.js` reports through `console.*` at line 68 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/protocol-types-generator/update-webview-protocol.js:68
`utils/protocol-types-generator/update-webview-protocol.js` reports through `console.*` at line 72 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/protocol-types-generator/update-webview-protocol.js:72
`utils/protocol-types-generator/update-webview-protocol.js` reports through `console.*` at line 74 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/protocol-types-generator/update-webview-protocol.js:74
`utils/doclint/api_parser.js` reports through `console.*` at line 461 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/doclint/api_parser.js:461
`utils/doclint/api_parser.js` reports through `console.*` at line 462 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/doclint/api_parser.js:462
`utils/doclint/generateApiJson.js` reports through `console.*` at line 36 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — utils/doclint/generateApiJson.js:36
`packages/isomorphic/cssTokenizer.ts` reports through `console.*` at line 117 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/isomorphic/cssTokenizer.ts:117
`packages/isomorphic/cssTokenizer.ts` reports through `console.*` at line 140 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/isomorphic/cssTokenizer.ts:140
`packages/isomorphic/codegen/javascript.ts` reports through `console.*` at line 74 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/isomorphic/codegen/javascript.ts:74
`packages/injected/src/clock.ts` reports through `console.*` at line 252 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/injected/src/clock.ts:252
`packages/injected/src/recorder/pollingRecorder.ts` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/injected/src/recorder/pollingRecorder.ts:48
`browser_patches/firefox/juggler/ChannelEventSink.sys.mjs` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — browser_patches/firefox/juggler/ChannelEventSink.sys.mjs:47
`browser_patches/firefox/juggler/NetworkObserver.js` reports through `console.*` at line 1047 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — browser_patches/firefox/juggler/NetworkObserver.js:1047
`browser_patches/firefox/juggler/NetworkObserver.js` reports through `console.*` at line 1060 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — browser_patches/firefox/juggler/NetworkObserver.js:1060
`browser_patches/firefox/juggler/NetworkObserver.js` reports through `console.*` at line 1069 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — browser_patches/firefox/juggler/NetworkObserver.js:1069
`REDACTED` reports through `console.*` at line 429 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:429
`packages/playwright/src/worker/fixtureRunner.ts` reports through `console.*` at line 164 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/worker/fixtureRunner.ts:164
`packages/playwright/src/runner/testRunner.ts` reports through `console.*` at line 422 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/runner/testRunner.ts:422
`packages/playwright/src/runner/testServer.ts` reports through `console.*` at line 165 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/runner/testServer.ts:165
`packages/playwright/src/runner/testServer.ts` reports through `console.*` at line 319 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/runner/testServer.ts:319
`packages/playwright/src/reporters/json.ts` reports through `console.*` at line 254 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/reporters/json.ts:254
`packages/playwright/src/reporters/junit.ts` reports through `console.*` at line 109 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/reporters/junit.ts:109
`packages/playwright/src/plugins/gitCommitInfoPlugin.ts` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/plugins/gitCommitInfoPlugin.ts:34
`packages/playwright/src/matchers/toMatchAriaSnapshot.ts` reports through `console.*` at line 143 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/matchers/toMatchAriaSnapshot.ts:143
`packages/playwright/src/matchers/toMatchAriaSnapshot.ts` reports through `console.*` at line 148 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/matchers/toMatchAriaSnapshot.ts:148
`packages/playwright/src/matchers/toMatchSnapshot.ts` reports through `console.*` at line 201 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/matchers/toMatchSnapshot.ts:201
`packages/playwright/src/matchers/toMatchSnapshot.ts` reports through `console.*` at line 297 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/matchers/toMatchSnapshot.ts:297
`packages/playwright/src/matchers/toMatchSnapshot.ts` reports through `console.*` at line 307 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/matchers/toMatchSnapshot.ts:307
`packages/playwright/src/matchers/toMatchSnapshot.ts` reports through `console.*` at line 423 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/matchers/toMatchSnapshot.ts:423
`packages/playwright/src/matchers/toMatchSnapshot.ts` reports through `console.*` at line 430 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/playwright/src/matchers/toMatchSnapshot.ts:430
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
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 22 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/agent-review.yml:7
`.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `nuget`, `pip`, `maven`, `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — .github/dependabot.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.
Dependabot is configured but does not watch `nuget`, `pip`, `maven`, `gradle` — add those `package-ecosystem` entries to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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.existsSync` in `openPage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:234
`fs.readFileSync` in `launchBrowserServer` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/cli/driver.ts:93
`fs.unlinkSync` in `listen` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/remote/playwrightPipeServer.ts:44
`fs.existsSync` in `_installDriver` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/server/android/android.ts:189
`fs.existsSync` in `createProfile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/server/bidi/third_party/firefoxPrefs.ts:20
`crypto.generateKeyPairSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/server/credentials.ts:66
`crypto.generateKeyPairSync` in `_handleCreate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/server/credentials.ts:146
`fs.mkdirSync` in `callback to page.exposeBinding` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/server/launchApp.ts:109
`fs.writeFileSync` in `callback to page.exposeBinding` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/server/launchApp.ts:110
`fs.statSync` in `addFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/server/localUtils.ts:51
`fs.existsSync` in `executablesOrSharedLibraries` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/server/registry/dependencies.ts:312
`fs.existsSync` in `callback to browsers.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/server/registry/index.ts:1196
`fs.existsSync` in `serveTraceDataRoute` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/server/trace/viewer/traceViewer.ts:105
`fs.existsSync` in `outputFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:260
`execFileSync` in `killAllDaemons` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/cli-client/program.ts:379
`execSync` in `killAllDaemons` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/cli-client/program.ts:391
`fs.openSync` in `startDaemon` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/cli-client/session.ts:121
`fs.readFileSync` in `child.on("close")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/cli-client/session.ts:184
`fs.existsSync` in `patchGitIgnore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/cli-daemon/program.ts:118
`fs.existsSync` in `ensureConfiguredBrowserInstalled` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/cli-daemon/program.ts:136
`fs.mkdirSync` in `page.exposeBinding("_saveSerializedSettings")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:181
`fs.writeFileSync` in `page.exposeBinding("_saveSerializedSettings")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:182
`fs.unlinkSync` in `client.on("error")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:263
`fs.existsSync` in `resolveCLIConfigForCLI` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/playwright-core/src/tools/mcp/config.ts:167, packages/playwright-core/src/tools/mcp/config.ts:194
`fs.lstatSync` in `loadConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/mcp/config.ts:502
`fs.realpathSync` in `loadConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/mcp/config.ts:502
`fs.existsSync` in `closeTrace` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/trace/traceUtils.ts:63
`fs.existsSync` in `openTrace` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/trace/traceUtils.ts:69
`fs.existsSync` in `loadTrace` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/trace/traceUtils.ts:84
`fs.existsSync` in `installSkills` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright-core/src/tools/utils/installSkills.ts:35
`fs.rmSync` in `killProcessAndCleanup` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:258
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.1 / 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.
75 duplicated blocks under packages/playwright-core/src/server/ have copies in at least two of the sibling directories android, bidi, chromium, dispatchers, electron, firefox (+3 more sibling(s) not listed) — 60 of them are reported below, and 15 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 75 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 75 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 75 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/playwright-core/src/server/firefox/ffBrowser.ts:136
31 duplicated blocks under packages/ have copies in at least two of the sibling directories dashboard, extension, html-reporter, injected, isomorphic, playwright-browser-chromium (+7 more sibling(s) not listed) — 22 of them are reported below, and 9 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 31 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 31 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 31 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. — REDACTED:253
16 duplicated blocks under packages/playwright-core/src/ have copies in at least two of the sibling directories cli, client, remote, server, tools — 8 of them are reported below, and 8 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/playwright-core/src/client/network.ts:248
6 duplicated blocks under the repository root have copies in at least two of the sibling directories browser_patches, packages, utils — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — browser_patches/firefox/juggler/NetworkObserver.js:858
packages/isomorphic/trace/versions/traceV7.ts:30 · packages/isomorphic/trace/versions/traceV8.ts:171 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/isomorphic/trace/versions/traceV7.ts:30
packages/isomorphic/trace/versions/traceV10.ts:21 · packages/isomorphic/trace/versions/traceV9.ts:163 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/isomorphic/trace/versions/traceV10.ts:21
packages/isomorphic/trace/versions/traceV6.ts:17 · packages/isomorphic/trace/versions/traceV7.ts:17 — these 2 files are line-for-line copies of one another — 149 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/isomorphic/trace/versions/traceV6.ts:17
packages/isomorphic/trace/versions/traceV5.ts:18 · packages/isomorphic/trace/versions/traceV6.ts:17 — these 2 files are line-for-line copies of one another — 147 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/isomorphic/trace/versions/traceV5.ts:18
packages/isomorphic/trace/versions/traceV5.ts:18 · packages/isomorphic/trace/versions/traceV7.ts:17 — these 2 files are line-for-line copies of one another — 139 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/isomorphic/trace/versions/traceV5.ts:18
packages/playwright-core/src/server/firefox/ffBrowser.ts:136 · packages/playwright-core/src/server/webkit/wkBrowser.ts:128 — the two spans are one implementation copied and then locally edited — 994 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/playwright-core/src/server/firefox/ffBrowser.ts:136
packages/isomorphic/trace/versions/traceV4.ts:17 · packages/isomorphic/trace/versions/traceV5.ts:18 — these 2 files are line-for-line copies of one another — 130 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/isomorphic/trace/versions/traceV4.ts:17
packages/isomorphic/trace/versions/traceV4.ts:17 · packages/isomorphic/trace/versions/traceV6.ts:17 — these 2 files are line-for-line copies of one another — 129 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/isomorphic/trace/versions/traceV4.ts:17
packages/playwright-core/src/server/webkit/webview/wvPage.ts:1068 · packages/playwright-core/src/server/webkit/wkPage.ts:1096 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/playwright-core/src/server/webkit/webview/wvPage.ts:1068
packages/isomorphic/trace/versions/traceV8.ts:35 · packages/isomorphic/trace/versions/traceV9.ts:38 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/isomorphic/trace/versions/traceV8.ts:35
packages/playwright-core/src/server/webkit/webview/wvInterceptableRequest.ts:18 · packages/playwright-core/src/server/webkit/wkInterceptableRequest.ts:18 — these 2 files are line-for-line copies of one another — 105 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/playwright-core/src/server/webkit/webview/wvInterceptableRequest.ts:18
packages/playwright-core/src/server/webkit/webview/wvConnection.ts:17 · packages/playwright-core/src/server/webkit/wkConnection.ts:18 — these 2 files are line-for-line copies of one another — 87 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/playwright-core/src/server/webkit/webview/wvConnection.ts:17
packages/playwright-core/src/server/webkit/webview/wvExecutionContext.ts:18 · packages/playwright-core/src/server/webkit/wkExecutionContext.ts:18 — these 2 files are line-for-line copies of one another — 86 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/playwright-core/src/server/webkit/webview/wvExecutionContext.ts:18
packages/playwright-core/src/tools/backend/webstorage.ts:26 · packages/playwright-core/src/tools/backend/webstorage.ts:130 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/playwright-core/src/tools/backend/webstorage.ts:26
packages/isomorphic/trace/versions/traceV6.ts:162 · packages/isomorphic/trace/versions/traceV7.ts:183 · packages/isomorphic/trace/versions/traceV8.ts:324 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/isomorphic/trace/versions/traceV6.ts:162
packages/isomorphic/trace/versions/traceV4.ts:19 · packages/isomorphic/trace/versions/traceV5.ts:20 · packages/isomorphic/trace/versions/traceV6.ts:19 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/isomorphic/trace/versions/traceV4.ts:19
packages/playwright-core/src/server/webkit/webview/wvWorkers.ts:17 · packages/playwright-core/src/server/webkit/wkWorkers.ts:17 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/playwright-core/src/server/webkit/webview/wvWorkers.ts:17
packages/isomorphic/locatorGenerators.ts:566 · packages/isomorphic/locatorGenerators.ts:672 — the two spans are one implementation copied and then locally edited — 466 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/isomorphic/locatorGenerators.ts:566
REDACTED:253 · REDACTED:118 — the two spans are one implementation copied and then locally edited — 466 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. — REDACTED:253
packages/playwright-core/src/server/webkit/webview/wvPage.ts:553 · packages/playwright-core/src/server/webkit/wkPage.ts:542 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/playwright-core/src/server/webkit/webview/wvPage.ts:553
packages/playwright-core/src/server/chromium/crBrowser.ts:391 · packages/playwright-core/src/server/webkit/wkBrowser.ts:240 — the two spans are one implementation copied and then locally edited — 427 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/playwright-core/src/server/chromium/crBrowser.ts:391
packages/playwright-core/src/server/bidi/bidiChromium.ts:105 · REDACTED:328 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/playwright-core/src/server/bidi/bidiChromium.ts:105
packages/isomorphic/trace/versions/traceV5.ts:165 · packages/isomorphic/trace/versions/traceV6.ts:171 · packages/isomorphic/trace/versions/traceV7.ts:192 · packages/isomorphic/trace/versions/traceV8.ts:333 — the 4 copies are spread across 4 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/isomorphic/trace/versions/traceV5.ts:165
browser_patches/firefox/juggler/protocol/Protocol.js:19 · browser_patches/firefox/juggler/protocol/Protocol.js:88 — the two spans are one implementation copied and then locally edited — 272 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — browser_patches/firefox/juggler/protocol/Protocol.js:19
browser_patches/firefox/juggler/NetworkObserver.js:858 · packages/playwright-core/src/server/network.ts:81 — 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. — browser_patches/firefox/juggler/NetworkObserver.js:858
packages/trace-viewer/src/ui/filmStrip.tsx:138 · packages/trace-viewer/src/ui/filmStrip.tsx:189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/trace-viewer/src/ui/filmStrip.tsx:138
packages/playwright-core/src/server/webkit/webview/wvPage.ts:1220 · packages/playwright-core/src/server/webkit/wkPage.ts:1304 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/playwright-core/src/server/webkit/webview/wvPage.ts:1220
packages/playwright-core/src/client/browserContext.ts:412 · packages/playwright-core/src/client/page.ts:595 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/playwright-core/src/client/browserContext.ts:412
packages/playwright-core/src/server/bidi/bidiPdf.ts:31 · packages/playwright-core/src/server/chromium/crPdf.ts:32 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/playwright-core/src/server/bidi/bidiPdf.ts:31
packages/isomorphic/locatorGenerators.ts:352 · packages/isomorphic/locatorGenerators.ts:459 · packages/isomorphic/locatorGenerators.ts:677 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/isomorphic/locatorGenerators.ts:352
packages/playwright-core/src/server/firefox/ffPage.ts:504 · packages/playwright-core/src/server/webkit/wkPage.ts:914 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/playwright-core/src/server/firefox/ffPage.ts:504
packages/injected/src/recorder/recorder.ts:609 · packages/injected/src/recorder/recorder.ts:810 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/injected/src/recorder/recorder.ts:609
packages/isomorphic/locatorGenerators.ts:319 · packages/isomorphic/locatorGenerators.ts:422 · packages/isomorphic/locatorGenerators.ts:538 · packages/isomorphic/locatorGenerators.ts:644 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/isomorphic/locatorGenerators.ts:319
packages/playwright-core/src/server/webkit/webview/wvPage.ts:1026 · packages/playwright-core/src/server/webkit/wkPage.ts:1050 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/playwright-core/src/server/webkit/webview/wvPage.ts:1026
packages/playwright-core/src/server/bidi/bidiFirefox.ts:44 · packages/playwright-core/src/server/firefox/firefox.ts:57 — the two spans are one implementation copied and then locally edited — 264 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/playwright-core/src/server/bidi/bidiFirefox.ts:44
packages/playwright-core/src/server/chromium/crExecutionContext.ts:109 · packages/playwright-core/src/server/firefox/ffExecutionContext.ts:111 — the two spans are one implementation copied and then locally edited — 244 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/playwright-core/src/server/chromium/crExecutionContext.ts:109
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.
packages/dashboard/src/annotationZip.ts:18 imports @zip.js/zip.js/lib/zip-no-worker-deflate.js, 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. — packages/dashboard/src/annotationZip.ts:18
packages/dashboard/src/dashboardChannel.ts:17 reaches into another package with a relative path (../../playwright-core/src/tools/cli-client/registry) — import the package by name instead. — packages/dashboard/src/dashboardChannel.ts:17
packages/dashboard/src/dashboardChannel.ts:18 reaches into another package with a relative path (../../playwright-core/src/serverRegistry) — import the package by name instead. — packages/dashboard/src/dashboardChannel.ts:18
packages/dashboard/src/dashboardModel.ts:22 reaches into another package with a relative path (../../playwright-core/src/tools/cli-client/registry) — import the package by name instead. — packages/dashboard/src/dashboardModel.ts:22
packages/dashboard/src/dashboardModel.ts:23 reaches into another package with a relative path (../../playwright-core/src/serverRegistry) — import the package by name instead. — packages/dashboard/src/dashboardModel.ts:23
packages/html-reporter/src/index.tsx:20 imports @zip.js/zip.js/lib/zip-no-worker-inflate.js, 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. — packages/html-reporter/src/index.tsx:20
packages/playwright-client/src/index.ts:17 reaches into another package with a relative path (../../playwright-core/src/client/connection) — import the package by name instead. — packages/playwright-client/src/index.ts:17
packages/playwright-client/src/index.ts:19 reaches into another package with a relative path (../../playwright-core/src/client/browser) — import the package by name instead. — packages/playwright-client/src/index.ts:19
packages/playwright-core/src/server/bidi/bidiOverCdp.ts:35 imports chromium-bidi/lib/cjs/bidiMapper/BidiMapper, 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. — packages/playwright-core/src/server/bidi/bidiOverCdp.ts:35
packages/playwright-core/src/server/bidi/bidiOverCdp.ts:36 imports chromium-bidi/lib/cjs/cdp/CdpConnection, 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. — packages/playwright-core/src/server/bidi/bidiOverCdp.ts:36
packages/trace-viewer/src/sw/traceLoaderBackends.ts:17 imports @zip.js/zip.js/lib/zip-no-worker-inflate.js, 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. — packages/trace-viewer/src/sw/traceLoaderBackends.ts:17
REDACTED:24 reaches into another package with a relative path (../playwright-core/src/bootstrap) — import the package by name instead. — REDACTED:24
tests/extension/extension-fixtures.ts:169 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/lib/tools/cli-client/cli.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/extension/extension-fixtures.ts:169
tests/library/locator-parser.spec.ts:30 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/src/client/locator) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/library/locator-parser.spec.ts:30
tests/mcp/annotate.spec.ts:506 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/lib/tools/cli-client/cli.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/mcp/annotate.spec.ts:506
tests/mcp/cli-fixtures.ts:118 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/lib/tools/cli-client/cli.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/mcp/cli-fixtures.ts:118
tests/mcp/cli-fixtures.ts:137 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/lib/tools/cli-client/cli.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/mcp/cli-fixtures.ts:137
tests/mcp/fixtures.ts:302 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/lib/entry/mcp.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/mcp/fixtures.ts:302
utils/generate_cli_help.js:22 reaches into another package with a relative path (../packages/playwright-core/lib/coreBundle) — import the package by name instead. — utils/generate_cli_help.js:22
utils/roll_browser.js:20 reaches into another package with a relative path (../packages/playwright-core/lib/coreBundle) — import the package by name instead. — utils/roll_browser.js:20
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.
getTextAlternativeInternal has cyclomatic complexity 138 and cognitive complexity 240; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/injected/src/roleUtils.ts:703
(anonymous) has cyclomatic complexity 92 and cognitive complexity 118; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:384
generateChannels has cyclomatic complexity 81 and cognitive complexity 239; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — utils/generate_channels.js:239
validateConfig has cyclomatic complexity 79 and cognitive complexity 96; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/playwright/src/common/configLoader.ts:127
program has cyclomatic complexity 64 and cognitive complexity 78; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/playwright-core/src/tools/cli-client/program.ts:95
expectSingleElement has cyclomatic complexity 58 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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:1536
ansi2html has cyclomatic complexity 56 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/web/src/ansi2html.ts:17
validateProject has cyclomatic complexity 53 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/playwright/src/common/configLoader.ts:257
consumeAToken has cyclomatic complexity 49 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/isomorphic/cssTokenizer.ts:143
innerAsLocators has cyclomatic complexity 46 and cognitive complexity 113; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/isomorphic/locatorGenerators.ts:86
visit has cyclomatic complexity 44 and cognitive complexity 72; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:95
innerRenderMdNode has cyclomatic complexity 44 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — utils/markdown.js:306
innerSerialize has cyclomatic complexity 43 and cognitive complexity 67; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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:253
translateType has cyclomatic complexity 42 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — utils/doclint/generateDotnetApi.js:735
Dashboard has cyclomatic complexity 40 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — REDACTED:67
generateLocator has cyclomatic complexity 40 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/isomorphic/locatorGenerators.ts:526
_innerFetch has cyclomatic complexity 39 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/playwright-core/src/client/fetch.ts:197
generateLocator has cyclomatic complexity 39 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/isomorphic/locatorGenerators.ts:416
_build has cyclomatic complexity 38 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/playwright-core/src/tools/backend/response.ts:269
_onRequest has cyclomatic complexity 37 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/playwright-core/src/server/chromium/crNetworkManager.ts:295
generateLocator has cyclomatic complexity 37 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. (×2) — packages/isomorphic/locatorGenerators.ts:313, packages/isomorphic/locatorGenerators.ts:638
renderPreview has cyclomatic complexity 37 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. — REDACTED:203
matchesNode 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. — REDACTED:381
minimist has cyclomatic complexity 34 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/playwright-core/src/tools/cli-client/minimist.ts:36
_initialize has cyclomatic complexity 34 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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:472
_innerAppendEvent has cyclomatic complexity 34 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/isomorphic/trace/traceModernizer.ts:107
buildTextCandidates has cyclomatic complexity 33 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/injected/src/selectorGenerator.ts:280
run has cyclomatic complexity 33 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — utils/doclint/cli.js:50
calculatePlatform has cyclomatic complexity 33 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/hostPlatform.ts:41
runWatchModeLoop has cyclomatic complexity 32 and cognitive complexity 71; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/playwright/src/runner/watchMode.ts:79
toMatchAriaSnapshot has cyclomatic complexity 31 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/playwright/src/matchers/toMatchAriaSnapshot.ts:41
visit has cyclomatic complexity 31 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:95
(anonymous) has cyclomatic complexity 31 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:472
parseEvaluationResultValue has cyclomatic complexity 30 and cognitive complexity 67; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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:151
traceConsole has cyclomatic complexity 30 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:21
elementState has cyclomatic complexity 30 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:788
convertMap has cyclomatic complexity 30 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/isomorphic/ariaSnapshot.ts:175
match has cyclomatic complexity 30 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. — packages/injected/src/roleSelectorEngine.ts:145
ImageDiffView has cyclomatic complexity 30 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/web/src/shared/imageDiffView.tsx:66
Do you agree with this assessment?
R3 · Large Files5.2 / 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.
REDACTED has 1760 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/playwright-core/src/server/frames.ts has 1729 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/frames.ts:1
packages/injected/src/recorder/recorder.ts has 1609 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/injected/src/recorder/recorder.ts:1
REDACTED has 1502 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
browser_patches/firefox/juggler/TargetRegistry.js has 1437 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — browser_patches/firefox/juggler/TargetRegistry.js:1
packages/playwright-core/src/tools/cli-daemon/commands.ts has 1324 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/tools/cli-daemon/commands.ts:1
packages/playwright-core/src/server/registry/index.ts has 1307 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/registry/index.ts:1
packages/injected/src/roleUtils.ts has 1262 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/injected/src/roleUtils.ts:1
packages/playwright-core/src/server/webkit/wkPage.ts has 1241 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/webkit/wkPage.ts:1
packages/playwright-core/src/server/webkit/webview/wvPage.ts has 1197 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/webkit/webview/wvPage.ts:1
REDACTED has 1188 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
browser_patches/firefox/juggler/NetworkObserver.js has 1051 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — browser_patches/firefox/juggler/NetworkObserver.js:1
packages/playwright-core/src/server/page.ts has 1039 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/page.ts:1
packages/playwright-core/src/server/dom.ts has 960 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/dom.ts:1
utils/doclint/documentation.js has 915 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — utils/doclint/documentation.js:1
packages/isomorphic/cssTokenizer.ts has 875 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/isomorphic/cssTokenizer.ts:1
packages/playwright-core/src/server/chromium/crNetworkManager.ts has 870 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/chromium/crNetworkManager.ts:1
packages/playwright-core/src/client/page.ts has 859 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/client/page.ts:1
packages/playwright/src/index.ts has 856 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright/src/index.ts:1
packages/playwright-core/src/server/trace/recorder/tracing.ts has 845 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/trace/recorder/tracing.ts:1
packages/playwright-core/src/server/network.ts has 839 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/network.ts:1
packages/playwright-core/src/client/network.ts has 835 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/client/network.ts:1
packages/playwright-core/src/server/fetch.ts has 824 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/fetch.ts:1
utils/doclint/generateDotnetApi.js has 809 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — utils/doclint/generateDotnetApi.js:1
packages/injected/src/clock.ts has 803 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/injected/src/clock.ts:1
packages/playwright/src/isomorphic/teleReceiver.ts has 789 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright/src/isomorphic/teleReceiver.ts:1
packages/playwright/src/reporters/html.ts has 773 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright/src/reporters/html.ts:1
REDACTED has 757 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/isomorphic/locatorGenerators.ts has 735 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/isomorphic/locatorGenerators.ts:1
packages/playwright-core/src/server/har/harTracer.ts has 734 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/har/harTracer.ts:1
packages/playwright-core/src/server/bidi/bidiPage.ts has 699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/bidi/bidiPage.ts:1
packages/isomorphic/locatorParser.ts has 694 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/isomorphic/locatorParser.ts:1
packages/playwright-core/src/tools/dashboard/dashboardController.ts has 673 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/tools/dashboard/dashboardController.ts:1
REDACTED has 669 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/playwright/src/worker/testInfo.ts has 658 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright/src/worker/testInfo.ts:1
packages/playwright/src/reporters/base.ts has 651 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright/src/reporters/base.ts:1
packages/playwright/src/runner/dispatcher.ts has 638 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright/src/runner/dispatcher.ts:1
REDACTED has 626 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/playwright/src/reporters/merge.ts has 622 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright/src/reporters/merge.ts:1
packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts has 620 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/playwright-core/src/server/trace/recorder/snapshotterInjected.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 Coverage6.3 / 10Adequate✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — REDACTED:1, packages/injected/src/recorder/recorder.ts:1, browser_patches/firefox/juggler/TargetRegistry.js:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code7.6 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
329 file(s) (~170854 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/playwright-core/src/server/webkit/webview/wvPage.ts imports '../../../generated/webViewInputSource', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/playwright-core
1 file(s) (~49 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an REDACTED script) so reachability can see this package. — tests/playwright-test/current-test-runner
2 file(s) (~34 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: tests/playwright-test/stable-test-runner/index.d.ts imports './node_modules/@playwright/test', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — tests/playwright-test/stable-test-runner
6 file(s) (~703 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an REDACTED script) so reachability can see this package. — utils/test-results-db
Unreachable from the 565 application, 85 tooling and 823 test entry point(s) detected in this repo. Gate removals on `npm run tsc` — an undetected custom entry would make these reachable.
no import path from any entry point (565 application, 85 tooling, 823 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×29) — browser_patches/firefox/juggler/TargetRegistry.js, browser_patches/firefox/juggler/NetworkObserver.js, utils/doclint/generateDotnetApi.js, …
no import path from any entry point (565 application, 85 tooling, 823 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (utils/doclint/generateDotnetApi.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — utils/doclint/dotnetXmlDocumentation.js
no import path from any entry point (565 application, 85 tooling, 823 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/html-reporter/src/testCaseView.story.tsx, packages/html-reporter/src/testFileView.story.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/html-reporter/src/sampleReport.ts
no import path from any entry point (565 application, 85 tooling, 823 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (utils/generate_types/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — utils/doclint/linkUtils.js, utils/generate_types/parseOverrides.js
Nothing imports this binding — it is safe to review for removal. (×2) — packages/dashboard/src/icons.tsx:78, packages/dashboard/src/icons.tsx:85
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 REDACTED — installs work only by hoisting accident. — utils/doclint/cli.js:26
Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED. — packages/playwright/src/runner/loadUtils.ts:30
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
Declared in packages/web/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
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.
Break each cycle by extracting the shared piece into a module both sides can import.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped5.2 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/injected/src/highlight.ts:319
`html` is text this program did not author, and it is written into the text of an element through `document.write` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/playwright-core/src/server/frames.ts:977
`messageInnerHTML` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:213
`html||''` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:25
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
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 — 5 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.
D11 Test Reliability — 5 observation(s) recorded · This repository declares 5 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.ts, .js, .mjs, .tsx), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
P12 CI test-gate honesty — 7 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
SC1 Supply-chain hygiene — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
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`) exited before it served a page. Likely cause (the repository): REDACTED has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D12 Dependency Hygiene — Dependency hygiene not measured
D18 Solution Shape — Dimension evaluation failed
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — This repository is one project, `linting-code-snippets` (39 LoC, 0 public types across 0 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .c, .cpp, .java, .m, .py, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 15 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication. The rest — .cpp, .m, .c (4,123 lines, 3.1% of production source) — is compared by neither card, so duplication there is unmeasured; it is a corner of this repository, not its product.
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 dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — examples/github-api/ (@playwright/test), examples/mock-battery/ (@playwright/test), examples/mock-filesystem/ (@playwright/test) — a gap in the analyzer, not something this repository is missing. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: 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 only 1 of the 3 signals this lens looks for (14 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
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.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 0% of this repository's production lines — typescript (132,342 lines), javascript (17,627 lines), cpp (1,892 lines), objectivec (1,353 lines), c (878 lines), java (96 lines), python (29 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no async method does work a token could cancel
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X25 Inert configuration knob — 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 — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 0% of this repository's production lines — typescript (132,342 lines), javascript (17,627 lines), cpp (1,892 lines), objectivec (1,353 lines), c (878 lines), java (96 lines), python (29 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Critical — 97 finding(s)
D10 · Test Quality· No assertions (empty test) · ×39
No assertions (empty test): LO-093 should wait for frame 2 tests/page/locator-frame.spec.ts:104— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): IS-022 should not register the callback on the global object tests/page/page-add-init-script-callback.spec.ts:113— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): AW-006 should work with noWaitAfter: true tests/page/page-autowaiting-basic.spec.ts:94— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): AW-007 should work with dblclick without noWaitAfter when navigation is stalled tests/page/page-autowaiting-basic.spec.ts:100— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): AW-014 calling window.stop async tests/page/page-autowaiting-no-hang.spec.ts:26— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): AW-017 assigning location to about:blank after non-about:blank tests/page/page-autowaiting-no-hang.spec.ts:46— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): AW-020 clicking in the middle of navigation that aborts tests/page/page-autowaiting-no-hang.spec.ts:69— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): AW-023 goBack in the middle of navigation that commits tests/page/page-autowaiting-no-hang.spec.ts:152— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): CL-078 should click a button that is overlaid by a permission popup tests/page/page-click.spec.ts:1103— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): ER-009 should remove a listener of a non-existing event handler tests/page/page-event-pageerror.spec.ts:192— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): FC-010 should not throw when frame is detached immediately tests/page/page-filechooser.spec.ts:179— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): NA-077 page.reload during renderer-initiated navigation tests/page/page-history.spec.ts:122— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): NA-083 page.goBack during renderer-initiated navigation tests/page/page-history.spec.ts:204— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): NA-084 page.goForward during renderer-initiated navigation tests/page/page-history.spec.ts:225— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): http transport browser sigint tests/mcp/http.spec.ts:132— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should close session when heartbeat ping is not answered tests/mcp/http.spec.ts:650— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): CC-039 should handle rejected certificate in handshake with HTTP/2 tests/library/client-certificates.spec.ts:923— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): DO-036 should convert navigation to a resource with unsupported mime type into download tests/library/download.spec.ts:700— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): LE-005 test #${i} to request page and context tests/library/heap.spec.ts:163— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): LE-006 test to request page and context tests/library/heap.spec.ts:168— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): LE-013 should collect frames tests/library/heap.spec.ts:270— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): PA-039 should close page with active dialog tests/library/page-close.spec.ts:22— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): PA-050 should not throw UnhandledPromiseRejection when page closes tests/library/page-close.spec.ts:130— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): AR-143 wpt accname # tests/library/role-utils.spec.ts:38— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): WS-034 should not throw with empty handler tests/library/route-web-socket.spec.ts:598— Test method has an empty body — it asserts nothing and exercises no code.
Boundary-crossing change coupling: REDACTED ↔ selectors.ts REDACTED:1— `REDACTED` (context injected) and `packages/playwright-core/src/server/selectors.ts` (context playwright-core) sit in DIFFERENT parts of the tree yet change together 90% of the time (19 of the 21 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 19 shared commits counted here, the most recent 3 are `b6e168a9` chore(recorder): render highlights via the shared element highlight (…; `313de29f` feat(locator): introduce locator.describe() (#35969); `807d9066` chore: allow generating aria references (#35132) (at that commit the file was still `packages/playwright-core/src/server/injected/injectedScript.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: locatorGenerators.ts ↔ selectors.ts packages/isomorphic/locatorGenerators.ts:1— `packages/isomorphic/locatorGenerators.ts` (context isomorphic) and `packages/playwright-core/src/server/selectors.ts` (context playwright-core) sit in DIFFERENT parts of the tree yet change together 62% of the time (13 of the 21 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `313de29f` feat(locator): introduce locator.describe() (#35969) (at that commit the file was still `packages/playwright-core/src/utils/isomorphic/locatorGenerators.ts`); `97d55e27` fix(locator): `locator(locator)` method uses `internal:chain` instead… (at that commit the file was still `packages/playwright-core/src/utils/isomorphic/locatorGenerators.ts`); `160888df` feat(locators): reland `locator.and(locator)` (#22850) (at that commit the file was still `packages/playwright-core/src/utils/isomorphic/locatorGenerators.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: consoleApi.ts ↔ selectors.ts packages/injected/src/consoleApi.ts:1— `packages/injected/src/consoleApi.ts` (context injected) and `packages/playwright-core/src/server/selectors.ts` (context playwright-core) sit in DIFFERENT parts of the tree yet change together 62% of the time (13 of the 21 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `807d9066` chore: allow generating aria references (#35132) (at that commit the file was still `packages/playwright-core/src/server/injected/consoleApi.ts`); `bd2fdd0f` chore: land experimental tools (#34503) (at that commit the file was still `packages/playwright-core/src/server/injected/consoleApi.ts`); `160888df` feat(locators): reland `locator.and(locator)` (#22850) (at that commit the file was still `packages/playwright-core/src/server/injected/consoleApi.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: expect.ts ↔ zones.ts packages/playwright/src/matchers/expect.ts:1— `packages/playwright/src/matchers/expect.ts` (context playwright) and `packages/utils/zones.ts` (context utils) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `90ec8383` chore: move zones into platform (#34786) (at that commit the file was still `packages/playwright-core/src/server/utils/zones.ts`); `be6caed8` chore: remove expectZone (#34312) (at that commit the file was still `packages/playwright-core/src/utils/zones.ts`); `3bdbe428` fix(steps): make expect.toPass and expect.poll step containers (#30389) (at that commit the file was still `packages/playwright-core/src/utils/zones.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: REDACTED ↔ snapshotterInjected.ts REDACTED:1— `REDACTED` (context isomorphic) and `packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts` (context playwright-core) sit in DIFFERENT parts of the tree yet change together 57% of the time (12 of the 21 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `da681cf1` chore(trace): track snapshot targets via generation counter (#40766); `395696ea` fix(trace-viewer): block meta refresh and sandbox snapshot iframes (#… (at that commit the file was still `packages/playwright-core/src/utils/isomorphic/trace/snapshotRenderer.ts`); `d7f8595f` fix(tracing): resourceOverrides issues (#38750) (at that commit the file was still `packages/playwright-core/src/utils/isomorphic/trace/snapshotRenderer.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: traceViewer.ts ↔ traceLoaderBackends.ts packages/playwright-core/src/server/trace/viewer/traceViewer.ts:1— `packages/playwright-core/src/server/trace/viewer/traceViewer.ts` (context playwright-core) and `packages/trace-viewer/src/sw/traceLoaderBackends.ts` (context trace-viewer) sit in DIFFERENT parts of the tree yet change together 53% of the time (8 of the 15 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `185bfb7d` fix(trace): operate trace uri, not path (#38566); `47fbd3a5` chore: remove HMR support from trace viewer (#37785) (at that commit the file was still `packages/trace-viewer/src/sw/traceModelBackends.ts`); `8c1002a9` fix(sw): fix UI mode on codespaces by not passing `server` (#33664) (at that commit the file was still `packages/trace-viewer/src/sw/traceModelBackends.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: traceModernizer.ts ↔ testTracing.ts packages/isomorphic/trace/traceModernizer.ts:1— `packages/isomorphic/trace/traceModernizer.ts` (context isomorphic) and `packages/playwright/src/worker/testTracing.ts` (context playwright) sit in DIFFERENT parts of the tree yet 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `87ca8496` chore(trace): use a single id for calls and test runner steps (#42430); `9642f576` feat(trace): attribute requests to service workers and api request co…; `c8fc3bf8` feat(trace-viewer): add "Display Aria" mode (#42211) — run `git show` on any of them.
Boundary-crossing change coupling: entries.ts ↔ tracing.ts packages/isomorphic/trace/entries.ts:1— `packages/isomorphic/trace/entries.ts` (context isomorphic) and `packages/playwright-core/src/server/trace/recorder/tracing.ts` (context playwright-core) sit in DIFFERENT parts of the tree yet change together 50% of the time (10 of the 20 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `c8fc3bf8` feat(trace-viewer): add "Display Aria" mode (#42211); `55eddb8f` chore(trace): show playwright version in metadata (#38158) (at that commit the file was still `packages/trace-viewer/src/types/entries.ts`); `ec40890f` fix(tracing): use page swap timestamp to find closest screenshot (#32… (at that commit the file was still `packages/trace-viewer/src/entries.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: dashboardChannel.ts ↔ REDACTED packages/dashboard/src/dashboardChannel.ts:1— `packages/dashboard/src/dashboardChannel.ts` (context dashboard) and `REDACTED` (context playwright-core) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `a6786ebe` feat(cli): include aria snapshot in annotate output (#40432); `10095c0c` feat(dashboard): cancel CLI annotate on client disconnect (#40347); `e575acda` feat(dashboard): add 'show --annotate' to capture annotations as PNG … — run `git show` on any of them.
Boundary-crossing change coupling: utilityScript.ts ↔ page.ts packages/injected/src/utilityScript.ts:1— `packages/injected/src/utilityScript.ts` (context injected) and `packages/playwright-core/src/server/page.ts` (context playwright-core) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `fd7d249e` chore: cleanup runtimeGuid and other builtins bits (#36035); `6af41232` chore: evaluate `UtilityScript` lazily (#36019); `d57f1946` chore: extract page bindings controller from `UtilityScript` (#35996) — run `git show` on any of them.
Boundary-crossing change coupling: connection.ts ↔ zones.ts packages/playwright-core/src/client/connection.ts:1— `packages/playwright-core/src/client/connection.ts` (context playwright-core) and `packages/utils/zones.ts` (context utils) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `90ec8383` chore: move zones into platform (#34786) (at that commit the file was still `packages/playwright-core/src/server/utils/zones.ts`); `f0a3a15e` chore: explicitly reset apiZone instead of everything (#34265) (at that commit the file was still `packages/playwright-core/src/utils/zones.ts`); `73fce8fb` chore: replace Zones with AsyncLocalStorage (#30381) (at that commit the file was still `packages/playwright-core/src/utils/zones.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: testInfo.ts ↔ zones.ts packages/playwright/src/worker/testInfo.ts:1— `packages/playwright/src/worker/testInfo.ts` (context playwright) and `packages/utils/zones.ts` (context utils) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `90ec8383` chore: move zones into platform (#34786) (at that commit the file was still `packages/playwright-core/src/server/utils/zones.ts`); `be6caed8` chore: remove expectZone (#34312) (at that commit the file was still `packages/playwright-core/src/utils/zones.ts`); `3bdbe428` fix(steps): make expect.toPass and expect.poll step containers (#30389) (at that commit the file was still `packages/playwright-core/src/utils/zones.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: channelOwner.ts ↔ zones.ts packages/playwright-core/src/client/channelOwner.ts:1— `packages/playwright-core/src/client/channelOwner.ts` (context playwright-core) and `packages/utils/zones.ts` (context utils) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `90ec8383` chore: move zones into platform (#34786) (at that commit the file was still `packages/playwright-core/src/server/utils/zones.ts`); `3bdbe428` fix(steps): make expect.toPass and expect.poll step containers (#30389) (at that commit the file was still `packages/playwright-core/src/utils/zones.ts`); `73fce8fb` chore: replace Zones with AsyncLocalStorage (#30381) (at that commit the file was still `packages/playwright-core/src/utils/zones.ts`) — run `git show` on any of them.
D11 · Test Reliability· Test declared unreliable · ×5
Test declared unreliable: tests/library/capabilities.spec.ts tests/library/capabilities.spec.ts:95— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "audio output is unreliable on hosted macOS 15 runners". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: tests/mcp/files.spec.ts tests/mcp/files.spec.ts:196— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "This test is racy". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: tests/page/frame-hierarchy.spec.ts tests/page/frame-hierarchy.spec.ts:40— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "frame.name() is racy with BiDi". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: tests/page/frame-hierarchy.spec.ts tests/page/frame-hierarchy.spec.ts:159— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "frame.name() is racy with BiDi". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: tests/page/page-basic.spec.ts tests/page/page-basic.spec.ts:110— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "page.frame({ name }) is racy with BiDi". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
No assertions: should throw in serial mode if test suites in worker are inconsistent with runner tests/playwright-test/runner.spec.ts:371— 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 respect custom shard weights tests/playwright-test/shard.spec.ts:355— 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: test${i} tests/playwright-test/shuffle.spec.ts:24— 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: test${i} tests/playwright-test/shuffle.spec.ts:71— 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 filter by title tests/playwright-test/ui-mode-test-filters.spec.ts:38— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should filter by explicit tags tests/playwright-test/ui-mode-test-filters.spec.ts:49— 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 hide filtered while running tests/playwright-test/ui-mode-test-filters.spec.ts:223— 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 filter skipped tests/playwright-test/ui-mode-test-filters.spec.ts:253— 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 only show tests selected with --grep tests/playwright-test/ui-mode-test-filters.spec.ts:278— 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 show tests filtered with --grep-invert tests/playwright-test/ui-mode-test-filters.spec.ts:286— 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 filter by only changed files tests/playwright-test/ui-mode-test-filters.spec.ts:294— 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 leak websocket connections tests/playwright-test/ui-mode-test-run.spec.ts:795— 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 run test defined outside of .spec.ts file tests/playwright-test/ui-mode-test-run.spec.ts:818— 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 run test defined outside of testdir tests/playwright-test/ui-mode-test-run.spec.ts:835— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should allow expanding entire subtrees tests/playwright-test/ui-mode-test-tree.spec.ts:483— 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 pick new / deleted files tests/playwright-test/ui-mode-test-update.spec.ts:38— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should pick new / deleted tests tests/playwright-test/ui-mode-test-update.spec.ts:83— 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 pick new / deleted nested tests tests/playwright-test/ui-mode-test-update.spec.ts:162— 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 watch files tests/playwright-test/ui-mode-test-watch.spec.ts:21— 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 watch e2e deps tests/playwright-test/ui-mode-test-watch.spec.ts:61— 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 run added test in watched file tests/playwright-test/ui-mode-test-watch.spec.ts:224— 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 watch test defined outside of .spec.ts file tests/playwright-test/ui-mode-test-watch.spec.ts:357— 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 quit on Q tests/playwright-test/watch.spec.ts:188— 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 print help on H tests/playwright-test/watch.spec.ts:195— 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 run tests on Enter tests/playwright-test/watch.spec.ts:202— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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.
Hotspot: packages/injected/src/roleUtils.ts packages/injected/src/roleUtils.ts:703— packages/injected/src/roleUtils.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 139 in roleUtils.getTextAlternativeInternal at line 703. 12 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/injected/src/roleUtils.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:472— REDACTED changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in FrameSession._initialize at line 472. 19 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright-core/src/server/fetch.ts packages/playwright-core/src/server/fetch.ts:329— packages/playwright-core/src/server/fetch.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in APIRequestContext._sendRequest at line 329. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/fetch.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright-core/src/server/frames.ts packages/playwright-core/src/server/frames.ts:1535— packages/playwright-core/src/server/frames.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in Frame._expectInternal at line 1535. 6 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/frames.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright-core/src/server/dom.ts packages/playwright-core/src/server/dom.ts:400— packages/playwright-core/src/server/dom.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in ElementHandle._performPointerAction at line 400. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/dom.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:788— REDACTED changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in InjectedScript.elementState at line 788. 11 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:326— REDACTED changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in snapshotRenderer.snapshotScript at line 326. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright-core/src/tools/mcp/config.ts packages/playwright-core/src/tools/mcp/config.ts:302— packages/playwright-core/src/tools/mcp/config.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in config.configFromCLIOptions at line 302. 4 of those changes were fix/bug commits, and the other 11 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/tools/mcp/config.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright-core/src/tools/mcp/program.ts packages/playwright-core/src/tools/mcp/program.ts:34— packages/playwright-core/src/tools/mcp/program.ts changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in program.decorateMCPCommand at line 34. 5 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/tools/mcp/program.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright-core/src/tools/backend/response.ts packages/playwright-core/src/tools/backend/response.ts:269— packages/playwright-core/src/tools/backend/response.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in Response._build at line 269. 4 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/tools/backend/response.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright-core/src/tools/cli-client/program.ts packages/playwright-core/src/tools/cli-client/program.ts:95— packages/playwright-core/src/tools/cli-client/program.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in program.program at line 95. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/tools/cli-client/program.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright/src/common/configLoader.ts packages/playwright/src/common/configLoader.ts:257— packages/playwright/src/common/configLoader.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in configLoader.validateProject at line 257. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright/src/common/configLoader.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright/src/common/config.ts packages/playwright/src/common/config.ts:59— packages/playwright/src/common/config.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in FullConfigInternal.constructor at line 59. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright/src/common/config.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/trace-viewer/src/ui/uiModeView.tsx packages/trace-viewer/src/ui/uiModeView.tsx:97— packages/trace-viewer/src/ui/uiModeView.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 88 in uiModeView.UIModeView at line 97. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/trace-viewer/src/ui/uiModeView.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: browser_patches/firefox/juggler/TargetRegistry.js browser_patches/firefox/juggler/TargetRegistry.js:312— browser_patches/firefox/juggler/TargetRegistry.js changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in FilePickerOverride._createPicker at line 312. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- browser_patches/firefox/juggler/TargetRegistry.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/isomorphic/locatorParser.ts packages/isomorphic/locatorParser.ts:69— packages/isomorphic/locatorParser.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in locatorParser.tokenize at line 69. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/isomorphic/locatorParser.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: utils/doclint/generateDotnetApi.js utils/doclint/generateDotnetApi.js:515— utils/doclint/generateDotnetApi.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in generateDotnetApi.renderMethod at line 515. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- utils/doclint/generateDotnetApi.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/isomorphic/locatorGenerators.ts packages/isomorphic/locatorGenerators.ts:86— packages/isomorphic/locatorGenerators.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in locatorGenerators.innerAsLocators at line 86. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/isomorphic/locatorGenerators.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/isomorphic/trace/traceModel.ts packages/isomorphic/trace/traceModel.ts:98— packages/isomorphic/trace/traceModel.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in TraceModel.constructor at line 98. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/isomorphic/trace/traceModel.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright/src/worker/workerMain.ts packages/playwright/src/worker/workerMain.ts:287— packages/playwright/src/worker/workerMain.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in WorkerMain._runTest at line 287. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright/src/worker/workerMain.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:81— REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in ariaSnapshot.generateAriaTree at line 81. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright/src/runner/dispatcher.ts packages/playwright/src/runner/dispatcher.ts:509— packages/playwright/src/runner/dispatcher.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in JobDispatcher._onDone at line 509. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright/src/runner/dispatcher.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/playwright/src/worker/testInfo.ts packages/playwright/src/worker/testInfo.ts:290— packages/playwright/src/worker/testInfo.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in TestInfoImpl._addStep at line 290. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright/src/worker/testInfo.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:253— REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in utilityScriptSerializers.innerSerialize at line 253. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/isomorphic/trace/traceModernizer.ts packages/isomorphic/trace/traceModernizer.ts:107— packages/isomorphic/trace/traceModernizer.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in TraceModernizer._innerAppendEvent at line 107. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/isomorphic/trace/traceModernizer.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.
+ 19 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/injected/src/recorder/recorder.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 browser_patches/firefox/juggler/TargetRegistry.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/injected/src/roleUtils.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 browser_patches/firefox/juggler/NetworkObserver.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 utils/doclint/documentation.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 browser_patches/firefox/juggler/protocol/Protocol.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 utils/doclint/generateDotnetApi.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 browser_patches/firefox/juggler/content/FrameTree.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 REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file utils/generate_types/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 browser_patches/firefox/juggler/content/PageAgent.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 browser_patches/firefox/juggler/content/Runtime.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 REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/trace-viewer/src/ui/networkResourceDetails.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/trace-viewer/src/ui/uiModeView.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/injected/src/highlight.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/injected/src/selectorGenerator.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file utils/doclint/api_parser.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/trace-viewer/src/ui/snapshotTab.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file utils/markdown.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/dashboard/src/annotations.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file utils/generate_channels.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/dashboard/src/dashboardModel.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.
TooManyMethods: Page packages/playwright-core/src/client/page.ts:90— TooManyMethods — 126 methods. The bar is 30 methods; this is 96 over it, 4.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Frame packages/playwright-core/src/server/frames.ts:511— TooManyMethods — 103 methods. The bar is 30 methods; this is 73 over it, 3.43× 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: WKPage packages/playwright-core/src/server/webkit/wkPage.ts:56— TooManyMethods — 92 methods. The bar is 30 methods; this is 62 over it, 3.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.
TooManyMethods: WVPage packages/playwright-core/src/server/webkit/webview/wvPage.ts:54— TooManyMethods — 90 methods. The bar is 30 methods; this is 60 over it, 3.00× 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: Locator packages/playwright-core/src/client/locator.ts:82— TooManyMethods — 80 methods. The bar is 30 methods; this is 50 over it, 2.67× 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: InjectedScript REDACTED:92— TooManyMethods — 77 methods. The bar is 30 methods; this is 47 over it, 2.57× 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: Page packages/playwright-core/src/server/page.ts:166— TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× 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: BrowserContext REDACTED:90— TooManyMethods — 74 methods. The bar is 30 methods; this is 44 over it, 2.47× 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: Frame packages/playwright-core/src/client/frame.ts:56— TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.40× 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: ElementHandle packages/playwright-core/src/server/dom.ts:132— TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.27× 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: PageDispatcher packages/playwright-core/src/server/dispatchers/pageDispatcher.ts:55— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.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: FFPage packages/playwright-core/src/server/firefox/ffPage.ts:43— TooManyMethods — 66 methods. The bar is 30 methods; this is 36 over it, 2.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BidiPage packages/playwright-core/src/server/bidi/bidiPage.ts:45— TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.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.
TooManyMethods: PageTarget browser_patches/firefox/juggler/TargetRegistry.js:665— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× 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: BrowserContext packages/playwright-core/src/client/browserContext.ts:64— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× 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: FrameDispatcher packages/playwright-core/src/server/dispatchers/frameDispatcher.ts:31— TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× 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: FrameSession REDACTED:400— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× 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: Tracing packages/playwright-core/src/server/trace/recorder/tracing.ts:88— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× 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: PageHandler REDACTED:68— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× 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: CRPage REDACTED:68— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× 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: Tab REDACTED:106— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× 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: BrowserHandler browser_patches/firefox/juggler/protocol/BrowserHandler.js:16— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: DashboardModel packages/dashboard/src/dashboardModel.ts:94— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: Recorder packages/playwright-core/src/server/recorder.ts:74— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× 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: BrowserContextDispatcher packages/playwright-core/src/server/dispatchers/browserContextDispatcher.ts:52— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× 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.
Sync-over-async blocking REDACTED:234— `fs.existsSync` in `openPage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/cli/driver.ts:93— `fs.readFileSync` in `launchBrowserServer` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/remote/playwrightPipeServer.ts:44— `fs.unlinkSync` in `listen` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/server/android/android.ts:189— `fs.existsSync` in `_installDriver` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/server/bidi/third_party/firefoxPrefs.ts:20— `fs.existsSync` in `createProfile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/server/credentials.ts:66— `crypto.generateKeyPairSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/server/credentials.ts:146— `crypto.generateKeyPairSync` in `_handleCreate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/server/launchApp.ts:109— `fs.mkdirSync` in `callback to page.exposeBinding` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/server/launchApp.ts:110— `fs.writeFileSync` in `callback to page.exposeBinding` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/server/localUtils.ts:51— `fs.statSync` in `addFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/server/registry/dependencies.ts:312— `fs.existsSync` in `executablesOrSharedLibraries` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/server/registry/index.ts:1196— `fs.existsSync` in `callback to browsers.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/server/trace/viewer/traceViewer.ts:105— `fs.existsSync` in `serveTraceDataRoute` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:260— `fs.existsSync` in `outputFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/tools/cli-client/program.ts:379— `execFileSync` in `killAllDaemons` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/tools/cli-client/program.ts:391— `execSync` in `killAllDaemons` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/tools/cli-client/session.ts:121— `fs.openSync` in `startDaemon` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/tools/cli-client/session.ts:184— `fs.readFileSync` in `child.on("close")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/tools/cli-daemon/program.ts:118— `fs.existsSync` in `patchGitIgnore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/tools/cli-daemon/program.ts:136— `fs.existsSync` in `ensureConfiguredBrowserInstalled` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:181— `fs.mkdirSync` in `page.exposeBinding("_saveSerializedSettings")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:182— `fs.writeFileSync` in `page.exposeBinding("_saveSerializedSettings")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:263— `fs.unlinkSync` in `client.on("error")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/tools/mcp/config.ts:167— `fs.existsSync` in `resolveCLIConfigForCLI` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/playwright-core/src/tools/mcp/config.ts:194— `fs.existsSync` in `resolveCLIConfigForCLI` 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.
FileTooLong: REDACTED REDACTED— FileTooLong — 1359 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: InjectedScript (92-1763). The bar is 500 significant lines; this is 859 over it, 2.72× 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: server/frames.ts packages/playwright-core/src/server/frames.ts— FileTooLong — 1353 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: Frame (511-1875). The bar is 500 significant lines; this is 853 over it, 2.71× 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: recorder/recorder.ts packages/injected/src/recorder/recorder.ts— FileTooLong — 1274 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 774 over it, 2.55× 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: registry/index.ts packages/playwright-core/src/server/registry/index.ts— FileTooLong — 1109 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 609 over it, 2.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: juggler/TargetRegistry.js browser_patches/firefox/juggler/TargetRegistry.js— FileTooLong — 1108 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 608 over it, 2.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: cli-daemon/commands.ts packages/playwright-core/src/tools/cli-daemon/commands.ts— FileTooLong — 1069 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 569 over it, 2.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: webkit/wkPage.ts packages/playwright-core/src/server/webkit/wkPage.ts— FileTooLong — 935 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: WKPage (56-1271). The bar is 500 significant lines; this is 435 over it, 1.87× 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: webview/wvPage.ts packages/playwright-core/src/server/webkit/webview/wvPage.ts— FileTooLong — 932 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: WVPage (54-1221). The bar is 500 significant lines; this is 432 over it, 1.86× 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: REDACTED REDACTED— FileTooLong — 876 significant lines (blank, comment-only and punctuation-only lines excluded), about 66% of them inside a single declaration: FrameSession (400-1249). The bar is 500 significant lines; this is 376 over it, 1.75× 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/roleUtils.ts packages/injected/src/roleUtils.ts— FileTooLong — 872 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 372 over it, 1.74× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: server/page.ts packages/playwright-core/src/server/page.ts— FileTooLong — 818 significant lines (blank, comment-only and punctuation-only lines excluded), about 69% of them inside a single declaration: Page (166-978). The bar is 500 significant lines; this is 318 over it, 1.64× 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: juggler/NetworkObserver.js browser_patches/firefox/juggler/NetworkObserver.js— FileTooLong — 767 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 267 over it, 1.53× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: server/dom.ts packages/playwright-core/src/server/dom.ts— FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: ElementHandle (132-991). The bar is 500 significant lines; this is 246 over it, 1.49× 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: isomorphic/cssTokenizer.ts packages/isomorphic/cssTokenizer.ts— FileTooLong — 697 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 197 over it, 1.39× 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: recorder/tracing.ts packages/playwright-core/src/server/trace/recorder/tracing.ts— FileTooLong — 684 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: Tracing (88-820). The bar is 500 significant lines; this is 184 over it, 1.37× 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: client/page.ts packages/playwright-core/src/client/page.ts— FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: Page (90-954). The bar is 500 significant lines; this is 176 over it, 1.35× 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: server/fetch.ts packages/playwright-core/src/server/fetch.ts— FileTooLong — 651 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: APIRequestContext (104-677). The bar is 500 significant lines; this is 151 over it, 1.30× 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: client/network.ts packages/playwright-core/src/client/network.ts— FileTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 133 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: chromium/crNetworkManager.ts packages/playwright-core/src/server/chromium/crNetworkManager.ts— FileTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 127 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: isomorphic/locatorGenerators.ts packages/isomorphic/locatorGenerators.ts— FileTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 110 over it, 1.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: BrowserContext (90-750). The bar is 500 significant lines; this is 104 over it, 1.21× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/clock.ts packages/injected/src/clock.ts— FileTooLong — 601 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 101 over it, 1.20× 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: har/harTracer.ts packages/playwright-core/src/server/har/harTracer.ts— FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: HarTracer (69-732). The bar is 500 significant lines; this is 99 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: server/network.ts packages/playwright-core/src/server/network.ts— FileTooLong — 594 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 94 over it, 1.19× 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: doclint/documentation.js utils/doclint/documentation.js— FileTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 55 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FunctionTooLong: snapshotterInjected.frameSnapshotStreamer packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:34— FunctionTooLong — frameSnapshotStreamer runs 473 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 373 over it, 4.73× 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: uiModeView.UIModeView packages/trace-viewer/src/ui/uiModeView.tsx:97— FunctionTooLong — UIModeView runs 392 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 292 over it, 3.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: cssTokenizer.tokenize packages/isomorphic/cssTokenizer.ts:77— FunctionTooLong — tokenize runs 377 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 277 over it, 3.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dashboard.Dashboard REDACTED:67— FunctionTooLong — Dashboard runs 305 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 205 over it, 3.05× 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: annotations.Annotations packages/dashboard/src/annotations.tsx:137— FunctionTooLong — Annotations runs 298 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 198 over it, 2.98× 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: workbench.PartitionedWorkbench packages/trace-viewer/src/ui/workbench.tsx:75— FunctionTooLong — PartitionedWorkbench runs 284 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 184 over it, 2.84× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: webSocketMock.inject packages/injected/src/webSocketMock.ts:38— FunctionTooLong — inject runs 231 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: snapshotRenderer.snapshotScript REDACTED:326— FunctionTooLong — snapshotScript runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× 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: recorder.Recorder packages/recorder/src/recorder.tsx:37— FunctionTooLong — Recorder runs 203 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 103 over it, 2.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: roleUtils.getTextAlternativeInternal packages/injected/src/roleUtils.ts:703— FunctionTooLong — getTextAlternativeInternal runs 195 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 95 over it, 1.95× 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: program.decorateProgram packages/playwright-core/src/cli/program.ts:36— FunctionTooLong — decorateProgram runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: cli.run utils/doclint/cli.js:50— FunctionTooLong — run runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: program.program packages/playwright-core/src/tools/cli-client/program.ts:95— FunctionTooLong — program runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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: check_deps.innerCheckDeps utils/check_deps.js:65— FunctionTooLong — innerCheckDeps runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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: playbackControl.usePlayback packages/trace-viewer/src/ui/playbackControl.tsx:48— FunctionTooLong — usePlayback runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: cssParser.parseCSS packages/isomorphic/cssParser.ts:39— FunctionTooLong — parseCSS runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: selectorParser.parseAttributeSelector packages/isomorphic/selectorParser.ts:276— FunctionTooLong — parseAttributeSelector runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: gantt.GanttChart packages/html-reporter/src/gantt.tsx:35— FunctionTooLong — GanttChart runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: program.decorateMCPCommand packages/playwright-core/src/tools/mcp/program.ts:34— FunctionTooLong — decorateMCPCommand runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× 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: generateDotnetApi.renderMethod utils/doclint/generateDotnetApi.js:515— FunctionTooLong — renderMethod runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: webAuthn.inject packages/injected/src/webAuthn.ts:59— FunctionTooLong — inject runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: generate_channels.generateChannels utils/generate_channels.js:239— FunctionTooLong — generateChannels runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: treeView.TreeView packages/web/src/components/treeView.tsx:53— FunctionTooLong — TreeView runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: codeMirrorWrapper.CodeMirrorWrapper packages/web/src/components/codeMirrorWrapper.tsx:52— FunctionTooLong — CodeMirrorWrapper runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ariaSnapshot.parseAriaSnapshot packages/isomorphic/ariaSnapshot.ts:131— FunctionTooLong — parseAriaSnapshot 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.
Repeated repair: REDACTED REDACTED:791— REDACTED changed 22 times in last 90 days and 12 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is browserContext.verifyClientCertificates at line 791), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Revert "feat(locator): add a context-wide visibility default" (#43888)”; “fix: do not send proxy credentials to website auth challenges (#43482)”; “Revert "fix: do not send proxy credentials to website auth challenges (#43342)" (#43406)”; “fix: do not send proxy credentials to website auth challenges (#43342)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: REDACTED REDACTED:741— REDACTED changed 19 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is tab.tabHeaderEquals at line 741), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(cli): use ordinal filenames for repeated downloads (#44011)”; “fix(mcp): report one-based console source lines (#43975)”; “fix(mcp): bound settle waits when page timers cannot run (#43767)”; “fix(mcp): report event listener exceptions as console errors (#43686)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/playwright-core/src/server/chromium/chromiumSwitches.ts packages/playwright-core/src/server/chromium/chromiumSwitches.ts:56— packages/playwright-core/src/server/chromium/chromiumSwitches.ts changed 13 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is chromiumSwitches.enabledFeatures at line 56), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chromium): skip on-device model performance measurement (#44014)”; “fix(chromium): preserve HTTP navigations across HTTPS upgrade modes (#43877)”; “fix(chromium): disable TCP port randomization on Windows (#43605)”; “fix(electron): enable SwiftShader fallback for WebGL (#43615)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/chromium/chromiumSwitches.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.
Repeated repair: packages/injected/src/clock.ts packages/injected/src/clock.ts:301— packages/injected/src/clock.ts changed 8 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is ClockController.addTimer at line 301), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(clock): advance zero-delay intervals between callbacks (#43948)”; “fix(clock): cancel real-time timer when replay ends paused (#43873)”; “fix(clock): preserve long fast-forward durations (#43789)”; “fix(clock): make fake Intl.DateTimeFormat create native instances (#43523)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/injected/src/clock.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.
Repeated repair: packages/injected/src/domUtils.ts packages/injected/src/domUtils.ts:68— packages/injected/src/domUtils.ts changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is domUtils.getAssociatedLabels at line 68), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(selectors): support labels for form-associated custom elements (#43900)”; “chore: revert "fix(a11y): treat inert elements and content outside of modal dialogs as hidden" (#43850)”; “fix(a11y): treat inert elements and content outside of modal dialogs as hidden (#43211)”; “fix(injected): reuse a single range in isVisibleTextNode (#43076)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/injected/src/domUtils.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.
Repeated repair: packages/playwright-core/src/server/network.ts packages/playwright-core/src/server/network.ts:443— packages/playwright-core/src/server/network.ts changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is Route.fulfill at line 443), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chromium): fail inflight requests when the document goes away (#43730)”; “fix(cookies): follow RFC 6265 domain and path matching in cookies(urls) (#43148)”; “fix(network): treat loopback addresses as secure for cookies (#43136)”; “fix(cookies): clearCookies({ name: '' }) should only remove nameless cookies (#43129)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/network.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.
Repeated repair: packages/playwright/src/transform/esmLoaderSync.ts packages/playwright/src/transform/esmLoaderSync.ts:67— packages/playwright/src/transform/esmLoaderSync.ts changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is esmLoaderSync.load at line 67), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Revert "fix(test): resolve aliases in dynamically imported CommonJS on Node 22" (#43974)”; “fix(test): resolve aliases in dynamically imported CommonJS on Node 22 (#43943)”; “fix(test runner): track shared ESM dependencies for only-changed (#43837)”; “fix(test): let registered loaders load files with unknown extensions (#43305)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright/src/transform/esmLoaderSync.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.
Repeated repair: packages/playwright-core/src/server/bidi/bidiBrowser.ts packages/playwright-core/src/server/bidi/bidiBrowser.ts:236— packages/playwright-core/src/server/bidi/bidiBrowser.ts changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is BidiBrowserContext.initialize at line 236), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: do not send proxy credentials to website auth challenges (#43482)”; “Revert "fix: do not send proxy credentials to website auth challenges (#43342)" (#43406)”; “fix: do not send proxy credentials to website auth challenges (#43342)”; “fix(bidi): authenticate against proxies in Chromium (#43232)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/bidi/bidiBrowser.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.
Repeated repair: packages/playwright-core/src/server/chromium/crServiceWorker.ts packages/playwright-core/src/server/chromium/crServiceWorker.ts:35— packages/playwright-core/src/server/chromium/crServiceWorker.ts changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is CRServiceWorker.constructor at line 35), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chromium): apply timezone to service workers (#44021)”; “fix: do not send proxy credentials to website auth challenges (#43482)”; “Revert "fix: do not send proxy credentials to website auth challenges (#43342)" (#43406)”; “fix: do not send proxy credentials to website auth challenges (#43342)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/chromium/crServiceWorker.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.
Repeated repair: packages/playwright-core/src/tools/backend/route.ts packages/playwright-core/src/tools/backend/route.ts:110— packages/playwright-core/src/tools/backend/route.ts changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is handle at line 110), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(mcp): preserve origin filters when modifying request headers (#43637)”; “fix(mcp): pass custom headers to route.fulfill when mocking response (#43244)”; “fix(mcp): match browser_route header names case-insensitively (#43227)”; “fix(mcp): keep upload modal, skip short secrets and bad headers (#42713)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/tools/backend/route.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.
Repeated repair: packages/playwright-core/src/server/socksClientCertificatesInterceptor.ts packages/playwright-core/src/server/socksClientCertificatesInterceptor.ts:425— packages/playwright-core/src/server/socksClientCertificatesInterceptor.ts changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is socksClientCertificatesInterceptor.parseALPNFromClientHello at line 425), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(client-certificates): finish browser TLS handshake before closing on server close (#43133)”; “Revert "fix(client-certificates): reestablish a way to explicitly send no client certificate for an origin" (#43074)”; “fix(client-certificates): respect launch proxy and proxy.bypass (#42873)”; “fix(client-certificates): reestablish a way to explicitly send no client certificate for an origin (#42547)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/socksClientCertificatesInterceptor.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.
Repeated repair: packages/playwright-core/src/tools/cli-daemon/daemon.ts packages/playwright-core/src/tools/cli-daemon/daemon.ts:72— packages/playwright-core/src/tools/cli-daemon/daemon.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is daemon.startCliDaemonServer at line 72), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(cli): use CLI command names in error messages (#43932)”; “fix(cli): do not force-kill the browser on close (#43229)”; “fix(cli): stop daemon when socket disappears (#42454)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/tools/cli-daemon/daemon.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.
Repeated repair: packages/playwright-core/src/server/highlightController.ts packages/playwright-core/src/server/highlightController.ts:105— packages/playwright-core/src/server/highlightController.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is HighlightController._resolve at line 105), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(recorder): coalesce highlight resolutions and update highlights atomically (#43897)”; “fix(highlight): resolve highlights relative to the frame of the locator (#42868)”; “fix(highlight): highlight in the world the selector resolves in (#42864)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/highlightController.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.
Repeated repair: packages/playwright-core/src/server/bidi/bidiPage.ts packages/playwright-core/src/server/bidi/bidiPage.ts:291— packages/playwright-core/src/server/bidi/bidiPage.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is BidiPage._onLogEntryAdded at line 291), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: do not send proxy credentials to website auth challenges (#43482)”; “Revert "fix: do not send proxy credentials to website auth challenges (#43342)" (#43406)”; “fix: do not send proxy credentials to website auth challenges (#43342)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/bidi/bidiPage.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.
Repeated repair: packages/playwright-core/src/tools/backend/cookies.ts packages/playwright-core/src/tools/backend/cookies.ts:178— packages/playwright-core/src/tools/backend/cookies.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is cookies.pathMatches at line 178), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(mcp): do not match sibling paths in cookie-list path filter (#43368)”; “fix(mcp): match cookie list domain filter on domain boundaries (#43316)”; “fix(mcp): ask for a cookie domain when the page has no host (#43318)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/tools/backend/cookies.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.
Repeated repair: packages/playwright-core/src/server/recorder/recorderApp.ts packages/playwright-core/src/server/recorder/recorderApp.ts:197— packages/playwright-core/src/server/recorder/recorderApp.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is RecorderApp._show at line 197), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(recorder): do not deliver buffered action to a recording started after it (#43289)”; “fix(recorder): split showRecorder and startRecording, deliver events per client (#42627)”; “fix(recorder): support re-enabling recorder on the same context (#42383)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/recorder/recorderApp.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.
Repeated repair: packages/playwright-core/src/client/jsHandle.ts packages/playwright-core/src/client/jsHandle.ts:141— packages/playwright-core/src/client/jsHandle.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is jsHandle.assertEvaluateOptions at line 141), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Revert "feat(evaluate): add "world" option to evaluate methods" (#43040)”; “chore: revert "feat(evaluate): opt in to Map and Set serialization" (#43029)”; “fix(evaluate): reject exposeFunctions in the utility world (#42860)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/client/jsHandle.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.
Repeated repair: packages/playwright-core/src/tools/backend/runCode.ts packages/playwright-core/src/tools/backend/runCode.ts:47— packages/playwright-core/src/tools/backend/runCode.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is handle at line 47), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(mcp): validate run-code input (#44087)”; “fix(cli): report run-code route handler exception once and verbatim (#43203)”; “fix(cli): expose benign globals in run-code vm context (#42975)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/tools/backend/runCode.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.
Repeated repair: packages/playwright/src/reporters/blob.ts packages/playwright/src/reporters/blob.ts:71— packages/playwright/src/reporters/blob.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is BlobReporter.onEnd at line 71), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(zip): never write through a symlink when extracting (#43910)”; “Revert "fix(blob): do not remove existing reports from output dir" (#43163)”; “fix(blob): do not remove existing reports from output dir (#43056)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright/src/reporters/blob.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.
Repeated repair: packages/playwright-core/src/tools/backend/screenshot.ts packages/playwright-core/src/tools/backend/screenshot.ts:36— packages/playwright-core/src/tools/backend/screenshot.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is screenshot.inferTypeFromFilename at line 36), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(mcp): clarify screenshot actions with vision tools (#43857)”; “fix(mcp): create parent directories for explicitly named files (#42540)”; “fix(mcp): preserve screenshot image resolution (#42406)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/tools/backend/screenshot.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.
Repeated repair: packages/playwright-core/src/server/chromium/crConnection.ts packages/playwright-core/src/server/chromium/crConnection.ts:162— packages/playwright-core/src/server/chromium/crConnection.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is CRSession._onMessage at line 162), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chromium): reject pending commands on all sessions when connection closes (#43221)”; “fix(chromium): dispose child session upon Target.detachedFromTarget (#43017)”; “fix(chromium): do not hang on pages without a renderer when connecting over CDP (#42936)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/chromium/crConnection.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.
Repeated repair: packages/playwright-core/src/tools/mcp/index.ts packages/playwright-core/src/tools/mcp/index.ts:29— packages/playwright-core/src/tools/mcp/index.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is index.createConnection at line 29), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(mcp): connect each client to the shared browser separately (#42622)”; “Revert "fix(mcp): drop the backend after browser_close with a shared browser" (#42492)”; “fix(mcp): drop the backend after browser_close with a shared browser (#42365)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/tools/mcp/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/injected/src/utilityScript.ts packages/injected/src/utilityScript.ts:68— packages/injected/src/utilityScript.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is UtilityScript.evaluate at line 68), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(evaluate): await page-overridden Promise in evaluateHandle and waitForFunction (#43436)”; “chore: revert "feat(evaluate): opt in to Map and Set serialization" (#43029)”; “fix(clock): make Temporal.Now follow page.clock (#42838)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/injected/src/utilityScript.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.
Repeated repair: packages/playwright-core/src/server/browser.ts packages/playwright-core/src/server/browser.ts:107— packages/playwright-core/src/server/browser.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is Browser.newContext at line 107), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(electron): do not drop windows that have not navigated while connecting (#43250)”; “fix(client-certificates): respect launch proxy and proxy.bypass (#42873)”; “fix(chromium): replay execution contexts when connecting to Android WebView (#42447)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/browser.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.
Repeated repair: packages/playwright-core/src/server/android/android.ts packages/playwright-core/src/server/android/android.ts:419— packages/playwright-core/src/server/android/android.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is AndroidDevice._refreshWebViews at line 419), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(android): pass the call timeout to the driver (#43228)”; “fix(chromium): replay execution contexts when connecting to Android WebView (#42447)”; “fix(android): match webview process by exact pid (#42410)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:30:07 -08:00' --until='2026-11-13 15:30:07 -08:00' --full-history --no-merges -- packages/playwright-core/src/server/android/android.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.
Change coupling: locator.ts ↔ selectors.ts packages/playwright-core/src/client/locator.ts:1— `packages/playwright-core/src/client/locator.ts` and `packages/playwright-core/src/server/selectors.ts` change together 81% of the time (17 of the 21 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 17 shared commits counted here, the most recent 3 are `313de29f` feat(locator): introduce locator.describe() (#35969); `807d9066` chore: allow generating aria references (#35132); `bd2fdd0f` chore: land experimental tools (#34503) — run `git show` on any of them.
Change coupling: androidServerImpl.ts ↔ browserServerImpl.ts packages/playwright-core/src/androidServerImpl.ts:1— `packages/playwright-core/src/androidServerImpl.ts` and `packages/playwright-core/src/browserServerImpl.ts` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `c8a1674b` chore: move slowmo and logging to dispatcher from server core (#36966); `a7599ad5` feat(api): add host option in launchServer options (#30999); `14a1eaa4` chore: add Playwright to attribution (#23447) — run `git show` on any of them.
Change coupling: REDACTED ↔ dashboardChannel.ts REDACTED:1— `REDACTED` and `packages/dashboard/src/dashboardChannel.ts` change together 79% of the time (11 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `c28b53e6` feat(dashboard): add a debugger actions panel (#41711); `83584954` chore(dashboard): remove browser_pick_locator remnants (#40351); `10095c0c` feat(dashboard): cancel CLI annotate on client disconnect (#40347) — run `git show` on any of them.
Change coupling: index.ts ↔ tasks.ts packages/playwright/src/plugins/index.ts:1— `packages/playwright/src/plugins/index.ts` and `packages/playwright/src/runner/tasks.ts` change together 73% of the time (11 of the 15 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 11 shared commits counted here, the most recent 3 are `10c9602c` chore: cleanup more ct remnants (#42200); `ae106c05` Revert "feat(test): support per-project webServer configuration (#408…; `ed918508` feat(test): support per-project webServer configuration (#40869) — run `git show` on any of them.
Change coupling: crExecutionContext.ts ↔ wkExecutionContext.ts packages/playwright-core/src/server/chromium/crExecutionContext.ts:1— `packages/playwright-core/src/server/chromium/crExecutionContext.ts` and `packages/playwright-core/src/server/webkit/wkExecutionContext.ts` change together 73% of the time (8 of the 11 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 8 shared commits counted here, the most recent 3 are `7b545099` chore(bidi): fix error messages from the utility world (#40275); `e38099ef` chore: getProperties can use context stored in JSHandle (#34893); `962a7528` chore: contain remote objects to browser-specific code (#34890) — run `git show` on any of them.
Change coupling: program.ts ↔ lastRun.ts packages/playwright/src/program.ts:1— `packages/playwright/src/program.ts` and `packages/playwright/src/runner/lastRun.ts` change together 70% of the time (7 of the 10 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 7 shared commits counted here, the most recent 3 are `45b43ff3` Revert "feat(test-runner): read last failed tests from --last-failed=…; `3456aa7d` feat(test-runner): read last failed tests from --last-failed=<file> (…; `561bb37a` feat: Allow configuring last-run output file location (#40806) — run `git show` on any of them.
Change coupling: loaderMain.ts ↔ loaderHost.ts packages/playwright/src/loader/loaderMain.ts:1— `packages/playwright/src/loader/loaderMain.ts` and `packages/playwright/src/runner/loaderHost.ts` change together 69% of the time (9 of the 13 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 `c758b150` fix(test): use synchronous module customization hooks (#40891); `0a51cf8e` feat(test runner): config.tag for a global tag (#37846); `342bae6c` chore: support esm loader on Node 20 (#23269) (at that commit the files were still `packages/playwright-test/src/loader/loaderMain.ts` and `packages/playwright-test/src/runner/loaderHost.ts`) — run `git show` on any of them.
Change coupling: REDACTED ↔ ffPage.ts REDACTED:1— `REDACTED` and `packages/playwright-core/src/server/firefox/ffPage.ts` change together 66% of the time (44 of the 67 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 44 shared commits counted here, the most recent 3 are `974edd3f` feat(dialog): add dialogclosed event (#42014); `bc97a130` fix(screencast): acknowledge frames after callbacks (#41898); `6949e055` feat: Add `location()` to `WebError` (#39767) — run `git show` on any of them.
Change coupling: REDACTED ↔ browserTypeDispatcher.ts REDACTED:1— `REDACTED` and `packages/playwright-core/src/server/dispatchers/browserTypeDispatcher.ts` change together 64% of the time (9 of the 14 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 `45387e54` chore: remove chromium._connectToWorker (#44097); `4afdd64a` chore(browserType): merge connectOverCDP and connectOverCDPTransport …; `8f503225` feat(browserType): allow passing a ConnectionTransport to connectOver… — run `git show` on any of them.
Change coupling: testServerConnection.ts ↔ testServer.ts packages/playwright/src/isomorphic/testServerConnection.ts:1— `packages/playwright/src/isomorphic/testServerConnection.ts` and `packages/playwright/src/runner/testServer.ts` change together 64% of the time (14 of the 22 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 14 shared commits counted here, the most recent 3 are `783b664f` chore: cleanup test root folder (#40100); `a6fb4676` chore(testRunner): expose pauseAtEnd/pauseOnError (#37923); `d669fcde` chore: step error recovery framework (#36996) — run `git show` on any of them.
Change coupling: electron.ts ↔ loader.ts packages/playwright-core/src/server/electron/electron.ts:1— `packages/playwright-core/src/server/electron/electron.ts` and `packages/playwright-core/src/server/electron/loader.ts` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `5df6a4e9` Revert "fix(electron): pass port via switches not args" (#39710); `c86a0724` fix(electron): pass port via switches not args (#39012); `ad6e4053` fix(electron): make sure user arguments go first (#29204) — run `git show` on any of them.
Change coupling: filmStrip.tsx ↔ workbench.tsx packages/trace-viewer/src/ui/filmStrip.tsx:1— `packages/trace-viewer/src/ui/filmStrip.tsx` and `packages/trace-viewer/src/ui/workbench.tsx` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `0ee695b5` feat(trace-viewer): show screencast frames during playback (#42751); `51023b42` chore(trace-viewer): show only the screencast frame on timeline hover…; `0494a0ab` chore: tv playback teaser (#39634) — run `git show` on any of them.
Change coupling: reporterV2.ts ↔ dispatcher.ts packages/playwright/src/reporters/reporterV2.ts:1— `packages/playwright/src/reporters/reporterV2.ts` and `packages/playwright/src/runner/dispatcher.ts` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 6 shared commits counted here, the most recent 3 are `b592dfc7` feat(test-runner): add Reporter.preprocessSuite() hook for test filte…; `33f4ee71` feat(reporter): expose worker info on fixture teardown errors (#40444); `aa35f26b` chore: simplify reporter `onTestPaused` (#38679) — run `git show` on any of them.
Change coupling: video.ts ↔ screencast.ts packages/playwright-core/src/client/video.ts:1— `packages/playwright-core/src/client/video.ts` and `packages/playwright-core/src/server/screencast.ts` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 6 shared commits counted here, the most recent 3 are `d0d1240e` feat(api): add annotate option for video and screencast (#39783); `9335d41a` feat(video): add screencast mode to Video.start for JPEG frame events…; `2864540c` chore: follow up to video api changes (#39085) — run `git show` on any of them.
Change coupling: traceModel.ts ↔ traceModernizer.ts packages/isomorphic/trace/traceModel.ts:1— `packages/isomorphic/trace/traceModel.ts` and `packages/isomorphic/trace/traceModernizer.ts` change together 58% of the time (11 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 between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `87ca8496` chore(trace): use a single id for calls and test runner steps (#42430); `9642f576` feat(trace): attribute requests to service workers and api request co…; `0d864018` feat(trace-viewer): webm-based film strip (#42319) — run `git show` on any of them.
Change coupling: networkFilters.tsx ↔ tabbedPane.tsx packages/trace-viewer/src/ui/networkFilters.tsx:1— `packages/trace-viewer/src/ui/networkFilters.tsx` and `packages/web/src/components/tabbedPane.tsx` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 6 shared commits counted here, the most recent 3 are `c47f96a5` chore: revert bogus keyboard navigability attempts (#41432); `3d8f1e93` fix(trace-viewer): add keyboard navigation to `NetworkFilters` compon…; `e25d5719` Revert "fix(trace-viewer): add keyboard navigation to `NetworkFilters… — run `git show` on any of them.
Change coupling: crNetworkManager.ts ↔ wkInterceptableRequest.ts packages/playwright-core/src/server/chromium/crNetworkManager.ts:1— `packages/playwright-core/src/server/chromium/crNetworkManager.ts` and `packages/playwright-core/src/server/webkit/wkInterceptableRequest.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 6 shared commits counted here, the most recent 3 are `83df35ae` feat(har): use engine timestamps instead of server `Date` (#41082); `1ac9a570` feat(har): include `WebSocket` in `.har` (#41015); `73f6cf9a` chore: normalize resource types (#38480) — run `git show` on any of them.
Change coupling: pdf.ts ↔ response.ts packages/playwright-core/src/tools/backend/pdf.ts:1— `packages/playwright-core/src/tools/backend/pdf.ts` and `packages/playwright-core/src/tools/backend/response.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `648a67c7` fix(mcp): create parent directories for explicitly named files (#42540); `d620c45c` chore: revert file output to server-based (#39038) (at that commit the files were still `packages/playwright/src/mcp/browser/tools/pdf.ts` and `packages/playwright/src/mcp/browser/response.ts`); `2307bf37` feat(mcp): add storage state tools (#39007) (at that commit the files were still `packages/playwright/src/mcp/browser/tools/pdf.ts` and `packages/playwright/src/mcp/browser/response.ts`) — run `git show` on any of them.
Change coupling: index.tsx ↔ uiModeView.tsx packages/trace-viewer/src/index.tsx:1— `packages/trace-viewer/src/index.tsx` and `packages/trace-viewer/src/ui/uiModeView.tsx` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 6 shared commits counted here, the most recent 3 are `9707e978` chore: revert #33228 - it needs a proper review (#33284); `3641e598` chore: HMR for Trace Viewer (#33228); `c8cc4f9c` chore(ui): update to react 18 (#32079) — run `git show` on any of them.
Change coupling: workerHost.ts ↔ workerMain.ts packages/playwright/src/runner/workerHost.ts:1— `packages/playwright/src/runner/workerHost.ts` and `packages/playwright/src/worker/workerMain.ts` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 11 shared commits counted here, the most recent 3 are `86b465c0` chore: merge agent cache from workers (#38500); `3ad540dc` feat: `onTestPaused` (#38475); `34a09f37` chore: remove mdb, replace by `sendMessage` ipc into test worker (#38… — run `git show` on any of them.
Change coupling: NetworkObserver.js ↔ main.js browser_patches/firefox/juggler/NetworkObserver.js:1— `browser_patches/firefox/juggler/NetworkObserver.js` and `browser_patches/firefox/juggler/content/main.js` change together 50% of the time (8 of the 16 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 8 shared commits counted here, the most recent 3 are `bba16283` chore: roll browser patches from upstream (#39944); `d0b1fc27` chore: roll browser patches (#38909); `01103405` chore: update browser patches to 09195c9 (#32877) — run `git show` on any of them.
Change coupling: workbench.tsx ↔ theme.ts packages/trace-viewer/src/ui/workbench.tsx:1— `packages/trace-viewer/src/ui/workbench.tsx` and `packages/web/src/theme.ts` change together 50% of the time (6 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 6 shared commits counted here, the most recent 3 are `888da0f8` chore(html): add html settings dialog (#37565); `d7393f99` chore: simplify settings management in UI mode (#32440); `a41cebc1` feat(ui mode): introduce Testing Options and Settings (#31841) — run `git show` on any of them.
Change coupling: video.ts ↔ pageDispatcher.ts packages/playwright-core/src/client/video.ts:1— `packages/playwright-core/src/client/video.ts` and `packages/playwright-core/src/server/dispatchers/pageDispatcher.ts` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 5 shared commits counted here, the most recent 3 are `d0d1240e` feat(api): add annotate option for video and screencast (#39783); `9335d41a` feat(video): add screencast mode to Video.start for JPEG frame events…; `d039c403` chore: update video api and implementation (#39054) — run `git show` on any of them.
Change coupling: lastRun.ts ↔ tasks.ts packages/playwright/src/runner/lastRun.ts:1— `packages/playwright/src/runner/lastRun.ts` and `packages/playwright/src/runner/tasks.ts` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `45b43ff3` Revert "feat(test-runner): read last failed tests from --last-failed=…; `3456aa7d` feat(test-runner): read last failed tests from --last-failed=<file> (…; `d50dde82` fix(runner): --last-failed should run nothing when previous run had n… — run `git show` on any of them.
Change coupling: ipc.ts ↔ reporterV2.ts packages/playwright/src/common/ipc.ts:1— `packages/playwright/src/common/ipc.ts` and `packages/playwright/src/reporters/reporterV2.ts` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 5 shared commits counted here, the most recent 3 are `b592dfc7` feat(test-runner): add Reporter.preprocessSuite() hook for test filte…; `aa35f26b` chore: simplify reporter `onTestPaused` (#38679); `3ad540dc` feat: `onTestPaused` (#38475) — run `git show` on any of them.
Boundary violation [package:third-party-deep-import] packages/dashboard/src/annotationZip.ts:18— packages/dashboard/src/annotationZip.ts:18 imports @zip.js/zip.js/lib/zip-no-worker-deflate.js, 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:relative-cross-package] packages/dashboard/src/dashboardChannel.ts:17— packages/dashboard/src/dashboardChannel.ts:17 reaches into another package with a relative path (../../playwright-core/src/tools/cli-client/registry) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/dashboard/src/dashboardChannel.ts:18— packages/dashboard/src/dashboardChannel.ts:18 reaches into another package with a relative path (../../playwright-core/src/serverRegistry) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/dashboard/src/dashboardModel.ts:22— packages/dashboard/src/dashboardModel.ts:22 reaches into another package with a relative path (../../playwright-core/src/tools/cli-client/registry) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/dashboard/src/dashboardModel.ts:23— packages/dashboard/src/dashboardModel.ts:23 reaches into another package with a relative path (../../playwright-core/src/serverRegistry) — import the package by name instead.
Boundary violation [package:third-party-deep-import] packages/html-reporter/src/index.tsx:20— packages/html-reporter/src/index.tsx:20 imports @zip.js/zip.js/lib/zip-no-worker-inflate.js, 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:relative-cross-package] packages/playwright-client/src/index.ts:17— packages/playwright-client/src/index.ts:17 reaches into another package with a relative path (../../playwright-core/src/client/connection) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/playwright-client/src/index.ts:19— packages/playwright-client/src/index.ts:19 reaches into another package with a relative path (../../playwright-core/src/client/browser) — import the package by name instead.
Boundary violation [package:third-party-deep-import] packages/playwright-core/src/server/bidi/bidiOverCdp.ts:35— packages/playwright-core/src/server/bidi/bidiOverCdp.ts:35 imports chromium-bidi/lib/cjs/bidiMapper/BidiMapper, 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] packages/playwright-core/src/server/bidi/bidiOverCdp.ts:36— packages/playwright-core/src/server/bidi/bidiOverCdp.ts:36 imports chromium-bidi/lib/cjs/cdp/CdpConnection, 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] packages/trace-viewer/src/sw/traceLoaderBackends.ts:17— packages/trace-viewer/src/sw/traceLoaderBackends.ts:17 imports @zip.js/zip.js/lib/zip-no-worker-inflate.js, 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:relative-cross-package] REDACTED:24— REDACTED:24 reaches into another package with a relative path (../playwright-core/src/bootstrap) — import the package by name instead.
Boundary violation [package:test-cross-package-internals] tests/extension/extension-fixtures.ts:169— tests/extension/extension-fixtures.ts:169 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/lib/tools/cli-client/cli.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] tests/library/locator-parser.spec.ts:30— tests/library/locator-parser.spec.ts:30 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/src/client/locator) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] tests/mcp/annotate.spec.ts:506— tests/mcp/annotate.spec.ts:506 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/lib/tools/cli-client/cli.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] tests/mcp/cli-fixtures.ts:118— tests/mcp/cli-fixtures.ts:118 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/lib/tools/cli-client/cli.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] tests/mcp/cli-fixtures.ts:137— tests/mcp/cli-fixtures.ts:137 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/lib/tools/cli-client/cli.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] tests/mcp/fixtures.ts:302— tests/mcp/fixtures.ts:302 reaches past another workspace package's public entry into its internals with a relative path (../../packages/playwright-core/lib/entry/mcp.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:relative-cross-package] utils/generate_cli_help.js:22— utils/generate_cli_help.js:22 reaches into another package with a relative path (../packages/playwright-core/lib/coreBundle) — import the package by name instead.
Boundary violation [package:relative-cross-package] utils/roll_browser.js:20— utils/roll_browser.js:20 reaches into another package with a relative path (../packages/playwright-core/lib/coreBundle) — import the package by name instead.
Low cohesion: BrowserContext (LCOM4 16) packages/playwright-core/src/client/browserContext.ts:64— BrowserContext's methods fall into 16 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 16 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TextOutput (LCOM4 16) packages/playwright-core/src/tools/cli-client/output.ts:77— TextOutput's methods fall into 16 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 16 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Page (LCOM4 10) packages/playwright-core/src/client/page.ts:90— Page's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: InjectedScript (LCOM4 9) REDACTED:92— InjectedScript's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TraceModernizer (LCOM4 8) packages/isomorphic/trace/traceModernizer.ts:43— TraceModernizer's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Registry (LCOM4 8) packages/playwright-core/src/server/registry/index.ts:507— Registry's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Chromium (LCOM4 7) REDACTED:56— Chromium's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ElectronApplication (LCOM4 5) packages/playwright-core/src/client/electron.ts:77— ElectronApplication's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Browser (LCOM4 5) packages/playwright-core/src/client/browser.ts:34— Browser's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Streamer (LCOM4 5) packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:88— Streamer's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BidiPage (LCOM4 5) packages/playwright-core/src/server/bidi/bidiPage.ts:45— BidiPage's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AndroidDevice (LCOM4 5) packages/playwright-core/src/client/android.ts:102— AndroidDevice's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TestTypeImpl (LCOM4 5) packages/playwright/src/common/testType.ts:36— TestTypeImpl's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Highlight (LCOM4 4) packages/injected/src/highlight.ts:49— Highlight's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CRBrowser (LCOM4 4) packages/playwright-core/src/server/chromium/crBrowser.ts:44— CRBrowser's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BrowserContextDispatcher (LCOM4 4) packages/playwright-core/src/server/dispatchers/browserContextDispatcher.ts:52— BrowserContextDispatcher's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Suite (LCOM4 4) packages/playwright/src/common/test.ts:46— Suite's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LineReporter (LCOM4 4) packages/playwright/src/reporters/line.ts:25— LineReporter's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
ClassTooLong: InjectedScript REDACTED:92— ClassTooLong — 1169 significant lines (blank, comment-only and punctuation-only lines excluded), 77 methods. The bar is 400 significant lines; this is 769 over it, 2.92× 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: Frame packages/playwright-core/src/server/frames.ts:511— ClassTooLong — 973 significant lines (blank, comment-only and punctuation-only lines excluded), 103 methods. The bar is 400 significant lines; this is 573 over it, 2.43× 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: WKPage packages/playwright-core/src/server/webkit/wkPage.ts:56— ClassTooLong — 851 significant lines (blank, comment-only and punctuation-only lines excluded), 92 methods. The bar is 400 significant lines; this is 451 over it, 2.13× 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: WVPage packages/playwright-core/src/server/webkit/webview/wvPage.ts:54— ClassTooLong — 822 significant lines (blank, comment-only and punctuation-only lines excluded), 90 methods. The bar is 400 significant lines; this is 422 over it, 2.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.
ClassTooLong: Registry packages/playwright-core/src/server/registry/index.ts:507— ClassTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 239 over it, 1.60× 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: ElementHandle packages/playwright-core/src/server/dom.ts:132— ClassTooLong — 614 significant lines (blank, comment-only and punctuation-only lines excluded), 68 methods. The bar is 400 significant lines; this is 214 over it, 1.54× 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: FrameSession REDACTED:400— ClassTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 400 significant lines; this is 179 over it, 1.45× 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: Page packages/playwright-core/src/client/page.ts:90— ClassTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded), 126 methods. The bar is 400 significant lines; this is 175 over it, 1.44× 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: Page packages/playwright-core/src/server/page.ts:166— ClassTooLong — 561 significant lines (blank, comment-only and punctuation-only lines excluded), 75 methods. The bar is 400 significant lines; this is 161 over it, 1.40× 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: Tracing packages/playwright-core/src/server/trace/recorder/tracing.ts:88— ClassTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 133 over it, 1.33× 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: BidiPage packages/playwright-core/src/server/bidi/bidiPage.ts:45— ClassTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded), 61 methods. The bar is 400 significant lines; this is 102 over it, 1.26× 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: HarTracer packages/playwright-core/src/server/har/harTracer.ts:69— ClassTooLong — 485 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 85 over it, 1.21× 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: BrowserContext REDACTED:90— ClassTooLong — 457 significant lines (blank, comment-only and punctuation-only lines excluded), 74 methods. The bar is 400 significant lines; this is 57 over it, 1.14× 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: APIRequestContext packages/playwright-core/src/server/fetch.ts:104— ClassTooLong — 407 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 7 over it, 1.02× 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.
D10 · Test Quality· Fixed-sleep synchronisation · ×11
Fixed-sleep synchronisation: NA-063 should return from goto if new navigation is started tests/page/page-goto.spec.ts:882— This test starts work it did not wait for (`navigation`, still running when the sleep starts) and then orders itself against it with `new Promise(r => setTimeout(r, 500))` — 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: SO-030 should wait for select to be enabled tests/page/page-select-option.spec.ts:330— This test starts work it did not wait for (`selectPromise`, still running when the sleep starts) and then orders itself against it with `new Promise(f => setTimeout(f, 1000))` — 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: SO-031 should wait for option to be enabled tests/page/page-select-option.spec.ts:356— This test starts work it did not wait for (`selectPromise`, still running when the sleep starts) and then orders itself against it with `new Promise(f => setTimeout(f, 1000))` — 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: SO-032 should wait for optgroup to be enabled tests/page/page-select-option.spec.ts:386— This test starts work it did not wait for (`selectPromise`, still running when the sleep starts) and then orders itself against it with `new Promise(f => setTimeout(f, 1000))` — 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: SO-033 should wait for select to be swapped tests/page/page-select-option.spec.ts:418— This test starts work it did not wait for (`selectPromise`, still running when the sleep starts) and then orders itself against it with `new Promise(f => setTimeout(f, 1000))` — 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: should not reap session of a client without the event stream tests/mcp/http.spec.ts:669— This test starts work it did not wait for (`post`, still running when the sleep starts) and then orders itself against it with `new Promise(f => setTimeout(f, 1000))` — 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: test_run should stop when aborted tests/mcp/test-run.spec.ts:126— This test starts work it did not wait for (`runPromise`, still running when the sleep starts) and then orders itself against it with `new Promise(resolve => setTimeout(resolve, 2000))` — 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: RO-188 context.unrouteAll should wait for pending handlers to complete tests/library/unroute-behavior.spec.ts:60— This test starts work it did not wait for (`navigationPromise`, still running when the sleep starts) and then orders itself against it with `new Promise(f => setTimeout(f, 500))` — 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: RO-189 context.unrouteAll should not wait for pending handlers to complete if behavior is ignoreErrors tests/library/unroute-behavior.spec.ts:90— This test starts work it did not wait for (`navigationPromise`, still running when the sleep starts) and then orders itself against it with `new Promise(f => setTimeout(f, 500))` — 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: RO-194 page.unrouteAll should wait for pending handlers to complete tests/library/unroute-behavior.spec.ts:188— This test starts work it did not wait for (`navigationPromise`, still running when the sleep starts) and then orders itself against it with `new Promise(f => setTimeout(f, 500))` — 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: RO-195 page.unrouteAll should not wait for pending handlers to complete if behavior is ignoreErrors tests/library/unroute-behavior.spec.ts:218— This test starts work it did not wait for (`navigationPromise`, still running when the sleep starts) and then orders itself against it with `new Promise(f => setTimeout(f, 500))` — 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.
MethodTooLong: Registry.constructor packages/playwright-core/src/server/registry/index.ts:510— MethodTooLong — constructor runs 259 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× 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: APIRequestContext._sendRequest packages/playwright-core/src/server/fetch.ts:329— MethodTooLong — _sendRequest runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Streamer.captureSnapshot packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:367— MethodTooLong — captureSnapshot runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× 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: InjectedScript.expectSingleElement REDACTED:1536— MethodTooLong — expectSingleElement runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InjectedScript.constructor REDACTED:139— MethodTooLong — constructor runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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: Electron.launch packages/playwright-core/src/server/electron/electron.ts:180— MethodTooLong — launch runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TraceModernizer._innerAppendEvent packages/isomorphic/trace/traceModernizer.ts:107— MethodTooLong — _innerAppendEvent runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×7
JavaScript dependencies are not locked examples/github-api/REDACTED:10— examples/github-api/REDACTED 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 examples/mock-battery/REDACTED:13— examples/mock-battery/REDACTED 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 examples/mock-filesystem/REDACTED:13— examples/mock-filesystem/REDACTED 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 examples/svgomg/REDACTED:13— examples/svgomg/REDACTED 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 examples/todomvc/REDACTED:13— examples/todomvc/REDACTED 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 tests/installation/playwright-test-plugin/REDACTED:9— tests/installation/playwright-test-plugin/REDACTED 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 tests/playwright-test/current-test-runner/REDACTED:3— tests/playwright-test/current-test-runner/REDACTED 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.
P12 · CI test-gate honesty· Pull-request path filter skips the test gate for source changes · ×5
Pull-request path filter skips the test gate for source changes .github/workflows/tests_mcp.yml:10— `paths-ignore: browser_patches/**` matches compiled source (`browser_patches/firefox/juggler/ChannelEventSink.sys.mjs`, `browser_patches/firefox/juggler/Helper.js`, `browser_patches/firefox/juggler/NetworkObserver.js`) — a pull request that changes only those files merges without running the tests. Ignore only documentation and other files no build reads.
Pull-request path filter skips the test gate for source changes .github/workflows/tests_mcp.yml:12— `paths-ignore: packages/extension/**` matches compiled source (`packages/extension/vite.config.mts`, `packages/extension/src/background.ts`, `packages/extension/src/cdpPolicy.ts`) — a pull request that changes only those files merges without running the tests. Ignore only documentation and other files no build reads.
Pull-request path filter skips the test gate for source changes .github/workflows/tests_mcp.yml:13— `paths-ignore: packages/playwright-core/src/server/bidi/**` matches compiled source (`packages/playwright-core/src/server/bidi/bidiBrowser.ts`, `packages/playwright-core/src/server/bidi/bidiChromium.ts`, `packages/playwright-core/src/server/bidi/bidiConnection.ts`) — a pull request that changes only those files merges without running the tests. Ignore only documentation and other files no build reads.
Pull-request path filter skips the test gate for source changes .github/workflows/tests_mcp.yml:14— `paths-ignore: tests/bidi/**` matches compiled source (`tests/bidi/csvReporter.ts`, `tests/bidi/playwright.config.ts`) — a pull request that changes only those files merges without running the tests. Ignore only documentation and other files no build reads.
Pull-request path filter skips the test gate for source changes .github/workflows/tests_mcp.yml:15— `paths-ignore: tests/extension/**` matches compiled source (`tests/extension/chrome-stub.js`, `tests/extension/cli.spec.ts`, `tests/extension/client-lifecycle.spec.ts`) — a pull request that changes only those files merges without running the tests. Ignore only documentation and other files no build reads.
Dead file (~21 LoC) packages/html-reporter/src/testFileView.story.tsx— no import path from any entry point (565 application, 85 tooling, 823 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 (~21 LoC) packages/playwright-client/src/nodeStubs/colors.ts— no import path from any entry point (565 application, 85 tooling, 823 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 (~21 LoC) packages/playwright-client/src/nodeStubs/events.ts— no import path from any entry point (565 application, 85 tooling, 823 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 (~21 LoC) packages/playwright-client/src/nodeStubs/inspector.ts— no import path from any entry point (565 application, 85 tooling, 823 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 (~21 LoC) packages/playwright-client/src/nodeStubs/util.ts— no import path from any entry point (565 application, 85 tooling, 823 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
Change-coupling hub: REDACTED → FrameTree.js, main.js, Protocol.js REDACTED— `REDACTED` changes together with 3 other files — `browser_patches/firefox/juggler/content/FrameTree.js`, `browser_patches/firefox/juggler/content/main.js`, `browser_patches/firefox/juggler/protocol/Protocol.js` — 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.
Change-coupling hub: TargetRegistry.js → FrameTree.js, PageAgent.js, Runtime.js, main.js, Protocol.js browser_patches/firefox/juggler/TargetRegistry.js— `browser_patches/firefox/juggler/TargetRegistry.js` changes together with 5 other files — `browser_patches/firefox/juggler/content/FrameTree.js`, `browser_patches/firefox/juggler/content/PageAgent.js`, `browser_patches/firefox/juggler/content/Runtime.js`, `browser_patches/firefox/juggler/content/main.js`, `browser_patches/firefox/juggler/protocol/Protocol.js` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 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 5.
Change-coupling hub: BrowserHandler.js → NetworkObserver.js, PageAgent.js, main.js, Protocol.js browser_patches/firefox/juggler/protocol/BrowserHandler.js— `browser_patches/firefox/juggler/protocol/BrowserHandler.js` changes together with 4 other files — `browser_patches/firefox/juggler/NetworkObserver.js`, `browser_patches/firefox/juggler/content/PageAgent.js`, `browser_patches/firefox/juggler/content/main.js`, `browser_patches/firefox/juggler/protocol/Protocol.js` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 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 4.
Change-coupling hub: REDACTED → console.ts, navigate.ts, snapshot.ts REDACTED— `REDACTED` changes together with 3 other files — `packages/playwright-core/src/tools/backend/console.ts`, `packages/playwright-core/src/tools/backend/navigate.ts`, `packages/playwright-core/src/tools/backend/snapshot.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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×4
Untrusted text written into markup unescaped packages/injected/src/highlight.ts:319— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/playwright-core/src/server/frames.ts:977— `html` is text this program did not author, and it is written into the text of an element through `document.write` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:213— `messageInnerHTML` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:25— `html||''` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
cssTokenizer.tokenize::consumeAToken (cyclomatic 49) packages/isomorphic/cssTokenizer.ts:143— cssTokenizer.tokenize::consumeAToken has cyclomatic complexity 49 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: 2 other methods here (cssTokenizer.tokenize::consumeAURLToken, cssTokenizer.tokenize::consumeANumber) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
cssTokenizer.tokenize::consumeANumber (cyclomatic 17) packages/isomorphic/cssTokenizer.ts:470— cssTokenizer.tokenize::consumeANumber has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This shape REPEATS in the file: 2 other methods here (cssTokenizer.tokenize::consumeAToken, cssTokenizer.tokenize::consumeAURLToken) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
cssTokenizer.tokenize::consumeAURLToken (cyclomatic 16) packages/isomorphic/cssTokenizer.ts:342— cssTokenizer.tokenize::consumeAURLToken has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (cssTokenizer.tokenize::consumeAToken, cssTokenizer.tokenize::consumeANumber) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
cssTokenizer.tokenize::consumeAToken (cognitive 75) packages/isomorphic/cssTokenizer.ts:143— cssTokenizer.tokenize::consumeAToken has cognitive complexity 75 (threshold 15). Drivers by points: if/else 56 (70 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: 2 other methods here (cssTokenizer.tokenize::consumeAURLToken, cssTokenizer.tokenize::consumeANumber) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
cssTokenizer.tokenize::consumeAURLToken (cognitive 23) packages/isomorphic/cssTokenizer.ts:342— cssTokenizer.tokenize::consumeAURLToken has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 3 (5 pts), boolean chains 3 (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. This shape REPEATS in the file: 2 other methods here (cssTokenizer.tokenize::consumeAToken, cssTokenizer.tokenize::consumeANumber) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
cssTokenizer.tokenize::consumeANumber (cognitive 18) packages/isomorphic/cssTokenizer.ts:470— cssTokenizer.tokenize::consumeANumber has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, loops 4 (7 pts), if/else 4 (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. This shape REPEATS in the file: 2 other methods here (cssTokenizer.tokenize::consumeAToken, cssTokenizer.tokenize::consumeAURLToken) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
check_deps.innerCheckDeps::visit (cognitive 54) utils/check_deps.js:137— check_deps.innerCheckDeps::visit has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (46 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 3 other methods here (check_deps.innerCheckDeps, check_deps.innerCheckDeps::calculateDeps, check_deps.innerCheckDeps::allowImport) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
check_deps.innerCheckDeps::calculateDeps (cognitive 18) utils/check_deps.js:210— check_deps.innerCheckDeps::calculateDeps has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (check_deps.innerCheckDeps, check_deps.innerCheckDeps::visit, check_deps.innerCheckDeps::allowImport) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
check_deps.innerCheckDeps::allowImport (cognitive 17) utils/check_deps.js:247— check_deps.innerCheckDeps::allowImport has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (check_deps.innerCheckDeps, check_deps.innerCheckDeps::visit, check_deps.innerCheckDeps::calculateDeps) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Dead file (~24 LoC) packages/playwright-client/src/nodeStubs/crypto.ts— no import path from any entry point (565 application, 85 tooling, 823 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 (~24 LoC) packages/playwright-client/src/nodeStubs/stream.ts— no import path from any entry point (565 application, 85 tooling, 823 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 (~24 LoC) utils/video_stress.js— no import path from any entry point (565 application, 85 tooling, 823 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
ariaSnapshot.generateAriaTree::visit (cyclomatic 31) REDACTED:95— ariaSnapshot.generateAriaTree::visit has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (ariaSnapshot.generateAriaTree::processElement) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ariaSnapshot.generateAriaTree::processElement (cyclomatic 23) REDACTED:168— ariaSnapshot.generateAriaTree::processElement has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ariaSnapshot.generateAriaTree::visit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ariaSnapshotRenderer.renderAriaSnapshotAsYaml::createKey (cyclomatic 22) packages/isomorphic/ariaSnapshotRenderer.ts:38— ariaSnapshotRenderer.renderAriaSnapshotAsYaml::createKey has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ariaSnapshotRenderer.renderAriaSnapshotAsYaml::visit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ariaSnapshotRenderer.renderAriaSnapshotAsYaml::visit (cyclomatic 18) packages/isomorphic/ariaSnapshotRenderer.ts:83— ariaSnapshotRenderer.renderAriaSnapshotAsYaml::visit has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (ariaSnapshotRenderer.renderAriaSnapshotAsYaml::createKey) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ariaSnapshot.generateAriaTree::visit (cognitive 42) REDACTED:95— ariaSnapshot.generateAriaTree::visit has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 10, loops 2 (4 pts), ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ariaSnapshot.generateAriaTree::processElement) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ariaSnapshot.generateAriaTree::processElement (cognitive 29) REDACTED:168— ariaSnapshot.generateAriaTree::processElement has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 4 (8 pts), boolean chains 7, ternaries 2 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (ariaSnapshot.generateAriaTree::visit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
snapshotRenderer.snapshotScript::applyPlaywrightAttributes::visit (cognitive 41) REDACTED:361— snapshotRenderer.snapshotScript::applyPlaywrightAttributes::visit has cognitive complexity 41 (threshold 15). Drivers by points: loops 16 (19 pts), if/else 9 (14 pts), error handling 2 (4 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (snapshotRenderer.snapshotScript::applyPlaywrightAttributes::onLoad) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
snapshotRenderer.snapshotScript::applyPlaywrightAttributes::onLoad (cognitive 17) REDACTED:477— snapshotRenderer.snapshotScript::applyPlaywrightAttributes::onLoad has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 5, loops 2, ternaries 1 (2 pts) (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. This shape REPEATS in the file: one other method here (snapshotRenderer.snapshotScript::applyPlaywrightAttributes::visit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ariaSnapshotRenderer.renderAriaSnapshotAsYaml::visit (cognitive 34) packages/isomorphic/ariaSnapshotRenderer.ts:83— ariaSnapshotRenderer.renderAriaSnapshotAsYaml::visit has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 2 (8 pts), loops 2 (5 pts), boolean chains 4 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ariaSnapshotRenderer.renderAriaSnapshotAsYaml::createKey) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ariaSnapshotRenderer.renderAriaSnapshotAsYaml::createKey (cognitive 22) packages/isomorphic/ariaSnapshotRenderer.ts:38— ariaSnapshotRenderer.renderAriaSnapshotAsYaml::createKey has cognitive complexity 22 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: one other method here (ariaSnapshotRenderer.renderAriaSnapshotAsYaml::visit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
selectorParser.parseAttributeSelector::readAttribute (cognitive 31) packages/isomorphic/selectorParser.ts:390— selectorParser.parseAttributeSelector::readAttribute has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 6, loops 2 (3 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. This shape REPEATS in the file: one other method here (selectorParser.parseAttributeSelector::readRegularExpression) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
selectorParser.parseAttributeSelector::readRegularExpression (cognitive 17) packages/isomorphic/selectorParser.ts:333— selectorParser.parseAttributeSelector::readRegularExpression has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 2, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (selectorParser.parseAttributeSelector::readAttribute) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
P12 · CI test-gate honesty· Changed-file filter skips the test gate for code the tests depend on · ×2
Changed-file filter skips the test gate for code the tests depend on REDACTED:19— `paths` runs `npm run test-extension` (the tests of `examples/github-api`) only when a change touches `packages/playwright-core/src/tools/**`, `!packages/playwright-core/src/tools/dashboard/**`, `!packages/playwright-core/src/tools/trace/**`, `packages/extension/**`, `tests/extension/**`, `REDACTED`, but those tests also depend on `examples/github-api`, `packages/playwright`, `packages/playwright-core`, `packages/playwright-test` (e.g. `examples/github-api/playwright.config.ts`, `packages/playwright/cli.js`) — a change there merges with them not run, and no unfiltered gate runs them. List the package's tests and its workspace dependencies in the filter, or drop it.
Changed-file filter skips the test gate for code the tests depend on REDACTED:6— `paths` runs `npx playwright test --config tests/webview/playwright.config.ts --shard=${{ matrix.shard }}/4` (the tests of `examples/github-api`) only when a change touches `tests/webview/**`, `packages/playwright-core/src/server/webkit/webview/**`, `REDACTED`, but those tests also depend on `examples/github-api`, `packages/playwright`, `packages/playwright-core`, `packages/playwright-test` (e.g. `examples/github-api/playwright.config.ts`, `packages/playwright/cli.js`) — a change there merges with them not run, and no unfiltered gate runs them. List the package's tests and its workspace dependencies in the filter, or drop it.
Duplicated block (40 lines × 2 locations) browser_patches/firefox/juggler/NetworkObserver.js:858— browser_patches/firefox/juggler/NetworkObserver.js:858 · packages/playwright-core/src/server/network.ts:81 — 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 (40 lines × 2 locations) packages/trace-viewer/src/ui/filmStrip.tsx:138— packages/trace-viewer/src/ui/filmStrip.tsx:138 · packages/trace-viewer/src/ui/filmStrip.tsx:189 — 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 (37 lines × 2 locations) packages/playwright-core/src/client/browserContext.ts:412— packages/playwright-core/src/client/browserContext.ts:412 · packages/playwright-core/src/client/page.ts:595 — 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 (37 lines × 2 locations) packages/playwright-core/src/server/bidi/bidiPdf.ts:31— packages/playwright-core/src/server/bidi/bidiPdf.ts:31 · packages/playwright-core/src/server/chromium/crPdf.ts:32 — 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 (31 lines × 2 locations) packages/injected/src/recorder/recorder.ts:609— packages/injected/src/recorder/recorder.ts:609 · packages/injected/src/recorder/recorder.ts:810 — 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 (31 lines × 2 locations) packages/playwright-core/src/server/webkit/webview/wvPage.ts:1026— packages/playwright-core/src/server/webkit/webview/wvPage.ts:1026 · packages/playwright-core/src/server/webkit/wkPage.ts:1050 — 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 (30 matched lines × 2 locations) · ×2
Duplicated block with local edits (30 matched lines × 2 locations) packages/playwright-core/src/server/bidi/bidiFirefox.ts:44— packages/playwright-core/src/server/bidi/bidiFirefox.ts:44 · packages/playwright-core/src/server/firefox/firefox.ts:57 — the two spans are one implementation copied and then locally edited — 264 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (30 matched lines × 2 locations) packages/playwright-core/src/server/chromium/crExecutionContext.ts:109— packages/playwright-core/src/server/chromium/crExecutionContext.ts:109 · packages/playwright-core/src/server/firefox/ffExecutionContext.ts:111 — the two spans are one implementation copied and then locally edited — 244 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.
Complex function generateLocator (cyclomatic 37, cognitive 24) packages/isomorphic/locatorGenerators.ts:313— generateLocator has cyclomatic complexity 37 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 generateLocator (cyclomatic 37, cognitive 24) packages/isomorphic/locatorGenerators.ts:638— generateLocator has cyclomatic complexity 37 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.
snapshotterInjected.frameSnapshotStreamer (cyclomatic 146) packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:34— snapshotterInjected.frameSnapshotStreamer has cyclomatic complexity 146 (threshold 15). Of this number, 37 points are the body's own statements and 109 belong to 14 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.
roleUtils.getTextAlternativeInternal (cyclomatic 139) packages/injected/src/roleUtils.ts:703— roleUtils.getTextAlternativeInternal has cyclomatic complexity 139 (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.
Streamer.captureSnapshot::visitNode (cyclomatic 92) packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:384— Streamer.captureSnapshot::visitNode has cyclomatic complexity 92 (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.
uiModeView.UIModeView (cyclomatic 88) packages/trace-viewer/src/ui/uiModeView.tsx:97— uiModeView.UIModeView has cyclomatic complexity 88 (threshold 15). Of this number, 23 points are the body's own statements and 65 belong to 19 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.
generate_channels.generateChannels (cyclomatic 81) utils/generate_channels.js:239— generate_channels.generateChannels has cyclomatic complexity 81 (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.
dashboard.Dashboard (cyclomatic 68) REDACTED:67— dashboard.Dashboard has cyclomatic complexity 68 (threshold 15). Of this number, 37 points are the body's own statements and 31 belong to 22 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.
APIRequestContext._sendRequest (cyclomatic 64) packages/playwright-core/src/server/fetch.ts:329— APIRequestContext._sendRequest has cyclomatic complexity 64 (threshold 15). Most of this is not in the body itself: 4 of the 64 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 390, 394, 351, …). 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.
webSocketMock.inject (cyclomatic 61) packages/injected/src/webSocketMock.ts:38— webSocketMock.inject has cyclomatic complexity 61 (threshold 15). Of this number, 44 points are the body's own statements and 17 belong to 7 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.
InjectedScript.expectSingleElement (cyclomatic 57) REDACTED:1536— InjectedScript.expectSingleElement has cyclomatic complexity 57 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ansi2html.ansi2html (cyclomatic 56) packages/web/src/ansi2html.ts:17— ansi2html.ansi2html has cyclomatic complexity 56 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
program.program (cyclomatic 55) packages/playwright-core/src/tools/cli-client/program.ts:95— program.program has cyclomatic complexity 55 (threshold 15). Of this number, 53 points are the body's own statements and 2 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.
cli.run (cyclomatic 47) utils/doclint/cli.js:50— cli.run has cyclomatic complexity 47 (threshold 15). Of this number, 34 points are the body's own statements and 13 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
innerRenderMdNode (cyclomatic 47) utils/markdown.js:306— innerRenderMdNode has cyclomatic complexity 47 (threshold 15). Of this number, 44 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
locatorGenerators.innerAsLocators (cyclomatic 46) packages/isomorphic/locatorGenerators.ts:86— locatorGenerators.innerAsLocators has cyclomatic complexity 46 (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.
recorder.Recorder (cyclomatic 46) packages/recorder/src/recorder.tsx:37— recorder.Recorder has cyclomatic complexity 46 (threshold 15). Of this number, 19 points are the body's own statements and 27 belong to 13 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SnapshotRenderer.render::visit (cyclomatic 45) REDACTED:95— SnapshotRenderer.render::visit has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
workbench.PartitionedWorkbench (cyclomatic 45) packages/trace-viewer/src/ui/workbench.tsx:75— workbench.PartitionedWorkbench has cyclomatic complexity 45 (threshold 15). Of this number, 25 points are the body's own statements and 20 belong to 10 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.
utilityScriptSerializers.innerSerialize (cyclomatic 43) REDACTED:253— utilityScriptSerializers.innerSerialize has cyclomatic complexity 43 (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.
generateDotnetApi.translateType (cyclomatic 42) utils/doclint/generateDotnetApi.js:735— generateDotnetApi.translateType has cyclomatic complexity 42 (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.
JavaLocatorFactory.generateLocator (cyclomatic 40) packages/isomorphic/locatorGenerators.ts:526— JavaLocatorFactory.generateLocator has cyclomatic complexity 40 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
FrameSession._initialize (cyclomatic 40) REDACTED:472— FrameSession._initialize has cyclomatic complexity 40 (threshold 15). Of this number, 34 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.
PythonLocatorFactory.generateLocator (cyclomatic 39) packages/isomorphic/locatorGenerators.ts:416— PythonLocatorFactory.generateLocator has cyclomatic complexity 39 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
APIRequestContext._innerFetch (cyclomatic 39) packages/playwright-core/src/client/fetch.ts:197— APIRequestContext._innerFetch has cyclomatic complexity 39 (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.
codeMirrorWrapper.CodeMirrorWrapper (cyclomatic 39) packages/web/src/components/codeMirrorWrapper.tsx:52— codeMirrorWrapper.CodeMirrorWrapper has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 131, 79, 126, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
minimist.minimist (cyclomatic 38) packages/playwright-core/src/tools/cli-client/minimist.ts:36— minimist.minimist has cyclomatic complexity 38 (threshold 15). Of this number, 34 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JavaScriptLocatorFactory.generateLocator (cyclomatic 37) packages/isomorphic/locatorGenerators.ts:313— JavaScriptLocatorFactory.generateLocator has cyclomatic complexity 37 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (CSharpLocatorFactory.generateLocator) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CSharpLocatorFactory.generateLocator (cyclomatic 37) packages/isomorphic/locatorGenerators.ts:638— CSharpLocatorFactory.generateLocator has cyclomatic complexity 37 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (JavaScriptLocatorFactory.generateLocator) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CRNetworkManager._onRequest (cyclomatic 37) packages/playwright-core/src/server/chromium/crNetworkManager.ts:295— CRNetworkManager._onRequest has cyclomatic complexity 37 (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.
bidiExecutionContext.renderPreview (cyclomatic 37) REDACTED:203— bidiExecutionContext.renderPreview has cyclomatic complexity 37 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
workbenchLoader.WorkbenchLoader (cyclomatic 37) REDACTED:27— workbenchLoader.WorkbenchLoader has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 15 of the 37 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 103, 147, 56, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
treeView.TreeView (cyclomatic 37) packages/web/src/components/treeView.tsx:53— treeView.TreeView has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 5 of the 37 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 143, 107, 94, …). 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.
ariaSnapshot.matchesNode (cyclomatic 36) REDACTED:381— ariaSnapshot.matchesNode has cyclomatic complexity 36 (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.
ElementHandle._performPointerAction (cyclomatic 36) packages/playwright-core/src/server/dom.ts:400— ElementHandle._performPointerAction has cyclomatic complexity 36 (threshold 15). Of this number, 23 points are the body's own statements and 13 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.
Response._build (cyclomatic 35) packages/playwright-core/src/tools/backend/response.ts:269— Response._build 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.
consoleTab.useConsoleTabModel (cyclomatic 35) REDACTED:64— consoleTab.useConsoleTabModel has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 1 of the 35 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 65, 70, 68, …). 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.
locatorParser.tokenize (cyclomatic 34) packages/isomorphic/locatorParser.ts:69— locatorParser.tokenize has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 15 of the 34 points are its own statements and the rest belongs to 3 function items inside it that branch (readString, readVerbatimString, match). 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.
TraceModernizer._innerAppendEvent (cyclomatic 34) packages/isomorphic/trace/traceModernizer.ts:107— TraceModernizer._innerAppendEvent has cyclomatic complexity 34 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
splitView.SplitView (cyclomatic 34) packages/web/src/components/splitView.tsx:35— splitView.SplitView has cyclomatic complexity 34 (threshold 15). Of this number, 27 points are the body's own statements and 7 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.
selectorGenerator.buildTextCandidates (cyclomatic 33) packages/injected/src/selectorGenerator.ts:280— selectorGenerator.buildTextCandidates has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
hostPlatform.calculatePlatform (cyclomatic 33) packages/utils/hostPlatform.ts:41— hostPlatform.calculatePlatform has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ariaSnapshot.renderAriaTreeAsJSON::visit (cyclomatic 32) REDACTED:472— ariaSnapshot.renderAriaTreeAsJSON::visit has cyclomatic complexity 32 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
webAuthn.inject (cyclomatic 32) packages/injected/src/webAuthn.ts:59— webAuthn.inject has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 15 of the 32 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 201, toBase64Url, fromBase64Url, …). 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.
Page.expectScreenshot (cyclomatic 32) packages/playwright-core/src/server/page.ts:718— Page.expectScreenshot has cyclomatic complexity 32 (threshold 15). Of this number, 24 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
timeline.Timeline (cyclomatic 32) packages/trace-viewer/src/ui/timeline.tsx:37— timeline.Timeline has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 5 of the 32 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 66, 90, 43, …). 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.
imageDiffView.ImageDiffView (cyclomatic 32) packages/web/src/shared/imageDiffView.tsx:66— imageDiffView.ImageDiffView has cyclomatic complexity 32 (threshold 15). Of this number, 30 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
reportView.ReportView (cyclomatic 31) packages/html-reporter/src/reportView.tsx:49— reportView.ReportView has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 8 of the 31 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 89, 62, 72, …). 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.
selectorGenerator.generateSelectorFor (cyclomatic 31) packages/injected/src/selectorGenerator.ts:121— selectorGenerator.generateSelectorFor has cyclomatic complexity 31 (threshold 15). Of this number, 28 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
roleSelectorEngine.queryRole::match (cyclomatic 30) packages/injected/src/roleSelectorEngine.ts:145— roleSelectorEngine.queryRole::match has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InjectedScript.elementState (cyclomatic 30) REDACTED:788— InjectedScript.elementState has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
utilityScriptSerializers.parseEvaluationResultValue (cyclomatic 30) REDACTED:151— utilityScriptSerializers.parseEvaluationResultValue has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Frame._expectInternal (cyclomatic 30) packages/playwright-core/src/server/frames.ts:1535— Frame._expectInternal has cyclomatic complexity 30 (threshold 15). Of this number, 26 points are the body's own statements and 4 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.
traceConsole.traceConsole (cyclomatic 30) REDACTED:21— traceConsole.traceConsole has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExecutionContext._createRemoteObject (cyclomatic 29) browser_patches/firefox/juggler/content/Runtime.js:459— ExecutionContext._createRemoteObject has cyclomatic complexity 29 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
selectorGenerator.buildNoTextCandidates (cyclomatic 29) packages/injected/src/selectorGenerator.ts:204— selectorGenerator.buildNoTextCandidates has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ariaSnapshot.parseAriaSnapshot::convertMap (cyclomatic 29) packages/isomorphic/ariaSnapshot.ts:175— ariaSnapshot.parseAriaSnapshot::convertMap has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
snapshotRenderer.snapshotScript::applyPlaywrightAttributes::visit (cyclomatic 29) REDACTED:361— snapshotRenderer.snapshotScript::applyPlaywrightAttributes::visit has cyclomatic complexity 29 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
browserActions.launchContext (cyclomatic 29) REDACTED:66— browserActions.launchContext has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
generateNameDefault (cyclomatic 29) utils/doclint/generateDotnetApi.js:417— generateNameDefault has cyclomatic complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 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.
FilePickerOverride._createPicker (cyclomatic 28) browser_patches/firefox/juggler/TargetRegistry.js:312— FilePickerOverride._createPicker has cyclomatic complexity 28 (threshold 15). Of this number, 24 points are the body's own statements and 4 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.
selectorParser.parseSelectorString (cyclomatic 28) packages/isomorphic/selectorParser.ts:184— selectorParser.parseSelectorString has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 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.
JavaScriptLanguageGenerator._generateActionCall (cyclomatic 28) packages/isomorphic/codegen/javascript.ts:97— JavaScriptLanguageGenerator._generateActionCall has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
jsonSchema.validate (cyclomatic 28) REDACTED:29— jsonSchema.validate has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TraceModel.constructor (cyclomatic 28) packages/isomorphic/trace/traceModel.ts:98— TraceModel.constructor has cyclomatic complexity 28 (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.
screenshotter.inPagePrepareForScreenshots (cyclomatic 28) packages/playwright-core/src/server/screenshotter.ts:49— screenshotter.inPagePrepareForScreenshots has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 5 function items inside it that branch (handleAnimations, collectRoots, a function literal at line 148, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
traceRequests.traceRequest (cyclomatic 28) REDACTED:75— traceRequests.traceRequest has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
main.doFetch (cyclomatic 28) REDACTED:138— main.doFetch has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
listView.ListView (cyclomatic 28) packages/web/src/components/listView.tsx:43— listView.ListView has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 5 of the 28 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 89, 124, 80, …). 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.
roleSelectorEngine.validateAttributes (cyclomatic 27) packages/injected/src/roleSelectorEngine.ts:61— roleSelectorEngine.validateAttributes has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WVPage._onConsoleMessage (cyclomatic 27) packages/playwright-core/src/server/webkit/webview/wvPage.ts:532— WVPage._onConsoleMessage has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
check_deps.innerCheckDeps::visit (cyclomatic 27) utils/check_deps.js:137— check_deps.innerCheckDeps::visit has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (check_deps.innerCheckDeps) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TargetRegistry.constructor (cyclomatic 26) browser_patches/firefox/juggler/TargetRegistry.js:373— TargetRegistry.constructor has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (onOpenWindow, onTabOpenListener, onCloseWindow, …). 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.
ariaSnapshot.toAriaNode (cyclomatic 26) REDACTED:239— ariaSnapshot.toAriaNode has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
KeyParser._applyAttribute (cyclomatic 26) packages/isomorphic/ariaSnapshot.ts:486— KeyParser._applyAttribute has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Frame.waitForSelector (cyclomatic 26) packages/playwright-core/src/server/frames.ts:837— Frame.waitForSelector has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 848, 855). 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.
PlaywrightServer.constructor (cyclomatic 26) packages/playwright-core/src/remote/playwrightServer.ts:55— PlaywrightServer.constructor has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 94, 70, 81, …). 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.
roleUtils.innerAccumulatedElementText (cyclomatic 25) packages/injected/src/roleUtils.ts:1046— roleUtils.innerAccumulatedElementText has cyclomatic complexity 25 (threshold 15). Of this number, 13 points are the body's own statements and 12 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
InjectedScript.dispatchEvent (cyclomatic 25) REDACTED:1223— InjectedScript.dispatchEvent has cyclomatic complexity 25 (threshold 15). Of this number, 13 points are the body's own statements and 12 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cookieStore.parseRawCookie (cyclomatic 25) packages/playwright-core/src/server/cookieStore.ts:135— cookieStore.parseRawCookie has cyclomatic complexity 25 (threshold 15). Of this number, 24 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.
serializers.innerParseSerializedValue (cyclomatic 25) REDACTED:35— serializers.innerParseSerializedValue has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
markdown.buildTree (cyclomatic 25) utils/markdown.js:116— markdown.buildTree has cyclomatic complexity 25 (threshold 15). Of this number, 20 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.jsonToTS (cyclomatic 25) utils/protocol-types-generator/index.js:40— index.jsonToTS has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 12 function literals inside it that branch (lines 43, 47, 69, …). 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.
Filter.matches (cyclomatic 24) packages/html-reporter/src/filter.ts:119— Filter.matches has cyclomatic complexity 24 (threshold 15). Of this number, 12 points are the body's own statements and 12 belong to 5 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.
injectedScript.createTextMatcher (cyclomatic 24) REDACTED:1798— injectedScript.createTextMatcher has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function item 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.
JavaLanguageGenerator._generateActionCall (cyclomatic 24) packages/isomorphic/codegen/java.ts:114— JavaLanguageGenerator._generateActionCall has cyclomatic complexity 24 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
BrowserContextDispatcher.constructor (cyclomatic 24) packages/playwright-core/src/server/dispatchers/browserContextDispatcher.ts:71— BrowserContextDispatcher.constructor has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 7 of the 24 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 155, 124, 179, …). 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.
config.configFromCLIOptions (cyclomatic 24) packages/playwright-core/src/tools/mcp/config.ts:302— config.configFromCLIOptions has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
serializers.innerSerializeValue (cyclomatic 24) REDACTED:118— serializers.innerSerializeValue has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
debuggerPanel.DebuggerPanel (cyclomatic 23) packages/dashboard/src/debuggerPanel.tsx:33— debuggerPanel.DebuggerPanel has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 89, 50, 44, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SelectorEvaluatorImpl._matchesParents (cyclomatic 23) REDACTED:265— SelectorEvaluatorImpl._matchesParents has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 268). 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.
InjectedScript.expectHitTarget (cyclomatic 23) REDACTED:1037— InjectedScript.expectHitTarget has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
injectedScript.deepEquals (cyclomatic 23) REDACTED:1895— injectedScript.deepEquals has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
selectorParser.parseSelector (cyclomatic 23) packages/isomorphic/selectorParser.ts:44— selectorParser.parseSelector has cyclomatic complexity 23 (threshold 15). Of this number, 22 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.
CSharpLanguageGenerator._generateActionCall (cyclomatic 23) packages/isomorphic/codegen/csharp.ts:129— CSharpLanguageGenerator._generateActionCall has cyclomatic complexity 23 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PythonLanguageGenerator._generateActionCall (cyclomatic 23) packages/isomorphic/codegen/python.ts:107— PythonLanguageGenerator._generateActionCall has cyclomatic complexity 23 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TraceModernizer._modernize_8_to_9 (cyclomatic 23) packages/isomorphic/trace/traceModernizer.ts:487— TraceModernizer._modernize_8_to_9 has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TraceLoader.load (cyclomatic 23) packages/isomorphic/trace/traceLoader.ts:39— TraceLoader.load has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FrameSelectors._callOnSelectorInternal (cyclomatic 23) packages/playwright-core/src/server/frameSelectors.ts:233— FrameSelectors._callOnSelectorInternal 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 3 function items inside it that branch (a function literal at line 250, getResult, a function literal at line 274). 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.
HarTracer._onRequestFinished (cyclomatic 23) packages/playwright-core/src/server/har/harTracer.ts:330— HarTracer._onRequestFinished has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HarTracer._onWebSocket (cyclomatic 23) packages/playwright-core/src/server/har/harTracer.ts:445— HarTracer._onWebSocket has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (recordMessage, updateTime, a function literal at line 512, …). 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.
HarBackend._harFindResponse (cyclomatic 23) packages/playwright-core/src/server/harBackend.ts:96— HarBackend._harFindResponse has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Response.serialize (cyclomatic 23) packages/playwright-core/src/tools/backend/response.ts:174— Response.serialize has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generateDotnetApi.renderMethod (cyclomatic 23) utils/doclint/generateDotnetApi.js:515— generateDotnetApi.renderMethod has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (generateDotnetApi.renderMethod::processArg) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
selectorParser.parseAttributeSelector::readAttribute (cyclomatic 22) packages/isomorphic/selectorParser.ts:390— selectorParser.parseAttributeSelector::readAttribute 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.
Registry.constructor (cyclomatic 22) packages/playwright-core/src/server/registry/index.ts:510— Registry.constructor has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (executablePathOrDie, a function literal at line 747, findExecutablePath, …). 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.
Chromium.launchWithSeleniumHub (cyclomatic 22) REDACTED:213— Chromium.launchWithSeleniumHub 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.
APIRequestContext.fetch (cyclomatic 22) packages/playwright-core/src/server/fetch.ts:197— APIRequestContext.fetch has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
consoleTab.format (cyclomatic 22) REDACTED:221— consoleTab.format 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.
stackTrace.parseStackFrame (cyclomatic 22) packages/utils/stackTrace.ts:45— stackTrace.parseStackFrame 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.
(anonymous) (cyclomatic 22) utils/roll_browser.js:47— (anonymous) has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs 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.
parseMember (cyclomatic 22) utils/doclint/api_parser.js:91— parseMember has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
selectorGenerator.cssEscapeCharacter (cyclomatic 21) packages/injected/src/selectorGenerator.ts:550— selectorGenerator.cssEscapeCharacter 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.
cssParser.parseCSS::consumeSimpleSelector (cyclomatic 21) packages/isomorphic/cssParser.ts:172— cssParser.parseCSS::consumeSimpleSelector has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebKit.defaultArgs (cyclomatic 21) packages/playwright-core/src/server/webkit/webkit.ts:101— WebKit.defaultArgs has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TextOutput.list (cyclomatic 21) packages/playwright-core/src/tools/cli-client/output.ts:143— TextOutput.list has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
callTab.propertyToString (cyclomatic 21) REDACTED:102— callTab.propertyToString 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.
resizeView.ResizeView (cyclomatic 21) packages/web/src/shared/resizeView.tsx:36— resizeView.ResizeView has cyclomatic complexity 21 (threshold 15). Of this number, 13 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.
markdown.flattenWrappedLines (cyclomatic 21) utils/markdown.js:77— markdown.flattenWrappedLines 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.
parseOverrides.parseOverrides (cyclomatic 21) utils/generate_types/parseOverrides.js:26— parseOverrides.parseOverrides has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (visit, serializeClass, visitProperties, …). 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.
TypesGenerator.stringifySimpleType (cyclomatic 21) utils/generate_types/index.js:420— TypesGenerator.stringifySimpleType has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
patchLinksInText (cyclomatic 21) utils/doclint/documentation.js:755— patchLinksInText has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 756, 807, 787, …). 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.
(anonymous) (cyclomatic 21) utils/linux-browser-dependencies/inside_docker/list_dependencies.js:27— (anonymous) has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
sessionSidebar.SessionSidebar (cyclomatic 20) packages/dashboard/src/sessionSidebar.tsx:79— sessionSidebar.SessionSidebar has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 103, 150, 83, …). 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.
RecordActionTool._shouldGenerateKeyPressFor (cyclomatic 20) packages/injected/src/recorder/recorder.ts:609— RecordActionTool._shouldGenerateKeyPressFor has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (JsonRecordActionTool._shouldGenerateKeyPressFor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
JsonRecordActionTool._shouldGenerateKeyPressFor (cyclomatic 20) packages/injected/src/recorder/recorder.ts:810— JsonRecordActionTool._shouldGenerateKeyPressFor has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (RecordActionTool._shouldGenerateKeyPressFor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
istanbulCoverage.mergeIstanbulCoverage (cyclomatic 20) packages/isomorphic/istanbulCoverage.ts:72— istanbulCoverage.mergeIstanbulCoverage has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Frame.expect (cyclomatic 20) packages/playwright-core/src/server/frames.ts:1473— Frame.expect has cyclomatic complexity 20 (threshold 15). Of this number, 19 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.
ElementHandle._setInputFiles (cyclomatic 20) packages/playwright-core/src/server/dom.ts:746— ElementHandle._setInputFiles has cyclomatic complexity 20 (threshold 15). Of this number, 11 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
config.validateBrowserConfig (cyclomatic 20) packages/playwright-core/src/tools/mcp/config.ts:226— config.validateBrowserConfig 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.
program.decorateMCPCommand (cyclomatic 20) packages/playwright-core/src/tools/mcp/program.ts:34— program.decorateMCPCommand has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 120, 175, 94, …). 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.
actionList.renderAction (cyclomatic 20) packages/trace-viewer/src/ui/actionList.tsx:135— actionList.renderAction has cyclomatic complexity 20 (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.
ariaModeView.AriaModeView (cyclomatic 20) packages/trace-viewer/src/ui/ariaModeView.tsx:148— ariaModeView.AriaModeView has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 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.
sourceTab.useSources (cyclomatic 20) packages/trace-viewer/src/ui/sourceTab.tsx:37— sourceTab.useSources has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to one function literal inside it that branches (line 39). 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.
build_deps_true.collectImports (cyclomatic 20) utils/build_deps_true.js:114— build_deps_true.collectImports 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.
TypesGenerator.classBody (cyclomatic 20) utils/generate_types/index.js:261— TypesGenerator.classBody has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 281). 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.
Helper.getNetworkErrorStatusText (cyclomatic 19) browser_patches/firefox/juggler/Helper.js:109— Helper.getNetworkErrorStatusText has cyclomatic complexity 19 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
InjectedScript.selectOptions (cyclomatic 19) REDACTED:856— InjectedScript.selectOptions has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (filter, filter::matchesLabel). 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.
urlMatch.resolveGlobBase (cyclomatic 19) REDACTED:214— urlMatch.resolveGlobBase has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 232, mapToken). 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.
BidiConnection._dispatchMessage (cyclomatic 19) packages/playwright-core/src/server/bidi/bidiConnection.ts:70— BidiConnection._dispatchMessage 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.
BidiNetworkManager._onBeforeRequestSent (cyclomatic 19) packages/playwright-core/src/server/bidi/bidiNetworkManager.ts:62— BidiNetworkManager._onBeforeRequestSent 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. This is NOT this file's highest cyclomatic complexity: bidiNetworkManager.resourceTypeFromBidi (cyclomatic 23) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
FFBrowserContext.initialize (cyclomatic 19) packages/playwright-core/src/server/firefox/ffBrowser.ts:172— FFBrowserContext.initialize has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ElementHandle._retryAction (cyclomatic 19) packages/playwright-core/src/server/dom.ts:328— ElementHandle._retryAction 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.
config.resolveCLIConfigForCLI (cyclomatic 19) packages/playwright-core/src/tools/mcp/config.ts:163— config.resolveCLIConfigForCLI has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
attachmentsTab.AttachmentsTab (cyclomatic 19) packages/trace-viewer/src/ui/attachmentsTab.tsx:95— attachmentsTab.AttachmentsTab has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 97, 125, 145). 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.
_innerRenderNodes (cyclomatic 19) utils/doclint/dotnetXmlDocumentation.js:36— _innerRenderNodes 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 2 function items inside it that branch (a function literal at line 48, handleListItem). 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.
selectorGenerator.cssFallback (cyclomatic 18) packages/injected/src/selectorGenerator.ts:359— selectorGenerator.cssFallback has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InjectedScript.setupHitTargetInterceptor (cyclomatic 18) REDACTED:1153— InjectedScript.setupHitTargetInterceptor has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (listener, stop). 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.
Overlay.setUIState (cyclomatic 18) packages/injected/src/recorder/recorder.ts:1184— Overlay.setUIState has cyclomatic complexity 18 (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.
selectorParser.splitSelectorByFrame (cyclomatic 18) packages/isomorphic/selectorParser.ts:108— selectorParser.splitSelectorByFrame has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
java.formatContextOptions (cyclomatic 18) packages/isomorphic/codegen/java.ts:254— java.formatContextOptions has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
imageUtils.scaleImageToSize (cyclomatic 18) packages/isomorphic/imageUtils.ts:43— imageUtils.scaleImageToSize has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
urlMatch.globToRegexPattern (cyclomatic 18) REDACTED:30— urlMatch.globToRegexPattern has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Route._innerFulfill (cyclomatic 18) packages/playwright-core/src/client/network.ts:386— Route._innerFulfill has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
dependencies.validateDependenciesWindows (cyclomatic 18) packages/playwright-core/src/server/registry/dependencies.ts:150— dependencies.validateDependenciesWindows has cyclomatic complexity 18 (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.
WKPage._onConsoleMessage (cyclomatic 18) packages/playwright-core/src/server/webkit/wkPage.ts:538— WKPage._onConsoleMessage has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Session.startDaemon (cyclomatic 18) packages/playwright-core/src/tools/cli-client/session.ts:115— Session.startDaemon has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 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.
callTab.parseSerializedValue (cyclomatic 18) REDACTED:129— callTab.parseSerializedValue has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
consoleTab.ConsoleTab (cyclomatic 18) REDACTED:165— consoleTab.ConsoleTab has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 177, 173). 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.
ariaModeView.collectAriaModeTargets (cyclomatic 18) packages/trace-viewer/src/ui/ariaModeView.tsx:48— ariaModeView.collectAriaModeTargets has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
snapshotTab.InspectModeController (cyclomatic 18) packages/trace-viewer/src/ui/snapshotTab.tsx:291— snapshotTab.InspectModeController 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 one function literal inside it that branches (line 292). 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.
socksProxy.parsePattern (cyclomatic 18) REDACTED:334— socksProxy.parsePattern has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 338, 347, 366, …). 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.
check_dependency_age.main (cyclomatic 18) utils/check_dependency_age.js:126— check_dependency_age.main has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generateDotnetApi.renderMember (cyclomatic 18) utils/doclint/generateDotnetApi.js:341— generateDotnetApi.renderMember has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
selectorUtils.matchesAttributePart (cyclomatic 17) packages/injected/src/selectorUtils.ts:32— selectorUtils.matchesAttributePart has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
selectorUtils.elementText (cyclomatic 17) packages/injected/src/selectorUtils.ts:68— selectorUtils.elementText has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InjectedScript.querySelectorAll (cyclomatic 17) REDACTED:376— InjectedScript.querySelectorAll has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
traceModel.adjustMonotonicTime (cyclomatic 17) packages/isomorphic/trace/traceModel.ts:342— traceModel.adjustMonotonicTime has cyclomatic complexity 17 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Frame.gotoImpl (cyclomatic 17) packages/playwright-core/src/server/frames.ts:695— Frame.gotoImpl has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, 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.
WebSocketTransport._connect (cyclomatic 17) packages/playwright-core/src/server/transport.ts:81— WebSocketTransport._connect has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 96, 109, 121). 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.
FrameSession._updateViewport (cyclomatic 17) REDACTED:1011— FrameSession._updateViewport has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CRBrowser._onAttachedToTarget (cyclomatic 17) packages/playwright-core/src/server/chromium/crBrowser.ts:185— CRBrowser._onAttachedToTarget has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WKPage._initializeSessionMayThrow (cyclomatic 17) packages/playwright-core/src/server/webkit/wkPage.ts:164— WKPage._initializeSessionMayThrow has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
localUtils.zip (cyclomatic 17) packages/playwright-core/src/server/localUtils.ts:44— localUtils.zip has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Connection.dispatch (cyclomatic 17) packages/playwright-core/src/client/connection.ts:236— Connection.dispatch has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
treeView.TreeItemHeader (cyclomatic 17) packages/web/src/components/treeView.tsx:239— treeView.TreeItemHeader has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
check_deps.innerCheckDeps (cyclomatic 17) utils/check_deps.js:65— check_deps.innerCheckDeps has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (check_deps.innerCheckDeps::visit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Type.fromParsedType (cyclomatic 17) utils/doclint/documentation.js:523— Type.fromParsedType has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This is NOT this file's highest cyclomatic complexity: documentation.patchLinksInText (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
ApiParser.parseArgument (cyclomatic 17) utils/doclint/api_parser.js:146— ApiParser.parseArgument has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
api_parser.applyTemplates::visit (cyclomatic 17) utils/doclint/api_parser.js:334— api_parser.applyTemplates::visit has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generateDotnetApi.renderMethod::processArg (cyclomatic 17) utils/doclint/generateDotnetApi.js:596— generateDotnetApi.renderMethod::processArg has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (generateDotnetApi.renderMethod) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
generate_dotnet_channels.processCustomType (cyclomatic 17) utils/generate_dotnet_channels.js:235— generate_dotnet_channels.processCustomType has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
create.AwaitExpression (cyclomatic 17) utils/eslint-plugin-progress/index.js:157— create.AwaitExpression has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExecutionContext.evaluateFunction (cyclomatic 16) browser_patches/firefox/juggler/content/Runtime.js:396— ExecutionContext.evaluateFunction has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PageHandler.['Page.dispatchMouseEvent'] (cyclomatic 16) REDACTED:483— PageHandler.['Page.dispatchMouseEvent'] 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 2 function items inside it that branch (a function literal at line 523, sendEvents). 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.
annotations.Annotations::onLayerKeyDown (cyclomatic 16) packages/dashboard/src/annotations.tsx:297— annotations.Annotations::onLayerKeyDown has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
connect.ConnectApp (cyclomatic 16) packages/extension/src/ui/connect.tsx:68— connect.ConnectApp has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 4 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.
roleUtils.parseCSSContentPropertyAsString (cyclomatic 16) packages/injected/src/roleUtils.ts:459— roleUtils.parseCSSContentPropertyAsString has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs 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.
codeFrame.tokenColor (cyclomatic 16) packages/isomorphic/codeFrame.ts:164— codeFrame.tokenColor has cyclomatic complexity 16 (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.
cssTokenizer.escapeIdent (cyclomatic 16) packages/isomorphic/cssTokenizer.ts:892— cssTokenizer.escapeIdent has cyclomatic complexity 16 (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.
JavaScriptLanguageGenerator.generateAction (cyclomatic 16) packages/isomorphic/codegen/javascript.ts:53— JavaScriptLanguageGenerator.generateAction has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
traceModel.mergeActionsAndUpdateTimingSameTrace (cyclomatic 16) packages/isomorphic/trace/traceModel.ts:291— traceModel.mergeActionsAndUpdateTimingSameTrace has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventEmitter.removeListener (cyclomatic 16) packages/playwright-core/src/client/eventEmitter.ts:199— EventEmitter.removeListener has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FrameSelectors._queryFrames (cyclomatic 16) packages/playwright-core/src/server/frameSelectors.ts:171— FrameSelectors._queryFrames has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 177, query, a function literal at line 204). 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.
input.buildLayoutClosure (cyclomatic 16) packages/playwright-core/src/server/input.ts:307— input.buildLayoutClosure has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HarTracer._onResponse (cyclomatic 16) packages/playwright-core/src/server/har/harTracer.ts:568— HarTracer._onResponse has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
dependencies.validateDependenciesLinux (cyclomatic 16) packages/playwright-core/src/server/registry/dependencies.ts:213— dependencies.validateDependenciesLinux has cyclomatic complexity 16 (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.
Registry.install (cyclomatic 16) packages/playwright-core/src/server/registry/index.ts:934— Registry.install has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Connection.sendMessageToServer (cyclomatic 16) packages/playwright-core/src/client/connection.ts:180— Connection.sendMessageToServer has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
installActions.installBrowsers (cyclomatic 16) packages/playwright-core/src/cli/installActions.ts:90— installActions.installBrowsers has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BrowserBackend.callTool (cyclomatic 16) packages/playwright-core/src/tools/backend/browserBackend.ts:89— BrowserBackend.callTool has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
snapshotTab.collectSnapshots (cyclomatic 16) packages/trace-viewer/src/ui/snapshotTab.tsx:403— snapshotTab.collectSnapshots has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
compare.compare (cyclomatic 16) packages/utils/image_tools/compare.ts:36— compare.compare has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Member.filterForLanguage (cyclomatic 16) utils/doclint/documentation.js:395— Member.filterForLanguage has cyclomatic complexity 16 (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. This is NOT this file's highest cyclomatic complexity: documentation.patchLinksInText (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
generate_channels.inlineType (cyclomatic 16) utils/generate_channels.js:34— generate_channels.inlineType has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TypesGenerator.generateTypes (cyclomatic 16) utils/generate_types/index.js:80— TypesGenerator.generateTypes has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 95, 114, 87, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
validate_deps.isEntryUsed (cyclomatic 16) utils/validate_deps.js:177— validate_deps.isEntryUsed has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(computed) (cyclomatic 16) REDACTED:483— (computed) 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 items inside it that branch (a function literal at line 523, sendEvents, a function literal at line 496). 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.
generate_channels.generateChannels (cognitive 239) utils/generate_channels.js:239— generate_channels.generateChannels has cognitive complexity 239 (threshold 15). Drivers by points: if/else 24 (95 pts), ternaries 16 (73 pts), loops 15 (46 pts), boolean chains 25 (nesting depth added 159). 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.
roleUtils.getTextAlternativeInternal (cognitive 236) packages/injected/src/roleUtils.ts:703— roleUtils.getTextAlternativeInternal has cognitive complexity 236 (threshold 15). Drivers by points: if/else 61 (157 pts), boolean chains 59, loops 4 (12 pts), ternaries 3 (8 pts) (nesting depth added 109). 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.
snapshotterInjected.frameSnapshotStreamer (cognitive 179) packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:34— snapshotterInjected.frameSnapshotStreamer has cognitive complexity 179 (threshold 15). Drivers by points: if/else 80 (108 pts), boolean chains 38, ternaries 9 (17 pts), loops 8 (10 pts), error handling 4 (6 pts) (nesting depth added 40). Of this number, 41 points are the body's own statements and 138 belong to 14 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.
Streamer.captureSnapshot::visitNode (cognitive 118) packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:384— Streamer.captureSnapshot::visitNode has cognitive complexity 118 (threshold 15). Drivers by points: if/else 45 (69 pts), boolean chains 30, ternaries 6 (14 pts), loops 3 (5 pts) (nesting depth added 34). 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.
locatorGenerators.innerAsLocators (cognitive 113) packages/isomorphic/locatorGenerators.ts:86— locatorGenerators.innerAsLocators has cognitive complexity 113 (threshold 15). Drivers by points: if/else 37 (93 pts), ternaries 3 (10 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 65). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity· run (cognitive 97) · ×1
run (cognitive 97) utils/doclint/cli.js:50— run has cognitive complexity 97 (threshold 15). Drivers by points: if/else 20 (55 pts), loops 11 (28 pts), boolean chains 6, ternaries 1 (4 pts), error handling 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 57). Of this number, 60 points are the body's own statements and 37 belong to 12 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.
uiModeView.UIModeView (cognitive 85) packages/trace-viewer/src/ui/uiModeView.tsx:97— uiModeView.UIModeView has cognitive complexity 85 (threshold 15). Drivers by points: if/else 30 (38 pts), boolean chains 30, loops 7 (10 pts), ternaries 7 (nesting depth added 11). Of this number, 18 points are the body's own statements and 67 belong to 19 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.
APIRequestContext._sendRequest (cognitive 75) packages/playwright-core/src/server/fetch.ts:329— APIRequestContext._sendRequest has cognitive complexity 75 (threshold 15). Drivers by points: if/else 26 (34 pts), boolean chains 20, ternaries 13, error handling 2 (5 pts), loops 2 (3 pts) (nesting depth added 12). Most of this is not in the body itself: 3 of the 75 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 390, 394, 351, …). 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.
minimist.minimist (cognitive 74) packages/playwright-core/src/tools/cli-client/minimist.ts:36— minimist.minimist has cognitive complexity 74 (threshold 15). Drivers by points: if/else 23 (45 pts), ternaries 3 (14 pts), boolean chains 8, loops 5 (7 pts) (nesting depth added 35). Of this number, 70 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SnapshotRenderer.render::visit (cognitive 73) REDACTED:95— SnapshotRenderer.render::visit has cognitive complexity 73 (threshold 15). Drivers by points: if/else 19 (44 pts), boolean chains 20, ternaries 2 (5 pts), loops 2 (4 pts) (nesting depth added 30). 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.
program.program (cognitive 69) packages/playwright-core/src/tools/cli-client/program.ts:95— program.program has cognitive complexity 69 (threshold 15). Drivers by points: if/else 23 (44 pts), ternaries 8 (15 pts), boolean chains 7, loops 1 (2 pts), match/switch 1 (nesting depth added 29). Of this number, 65 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.
generateDotnetApi.translateType (cognitive 68) utils/doclint/generateDotnetApi.js:735— generateDotnetApi.translateType has cognitive complexity 68 (threshold 15). Drivers by points: if/else 29 (50 pts), ternaries 5 (10 pts), boolean chains 8 (nesting depth added 26). 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.
utilityScriptSerializers.parseEvaluationResultValue (cognitive 67) REDACTED:151— utilityScriptSerializers.parseEvaluationResultValue has cognitive complexity 67 (threshold 15). Drivers by points: if/else 24 (54 pts), loops 4 (12 pts), boolean chains 1 (nesting depth added 38). 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.
utilityScriptSerializers.innerSerialize (cognitive 67) REDACTED:253— utilityScriptSerializers.innerSerialize has cognitive complexity 67 (threshold 15). Drivers by points: if/else 34 (48 pts), loops 5 (11 pts), error handling 2 (5 pts), boolean chains 3 (nesting depth added 23). 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.
InjectedScript.expectSingleElement (cognitive 63) REDACTED:1536— InjectedScript.expectSingleElement has cognitive complexity 63 (threshold 15). Drivers by points: if/else 42 (54 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 13). 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.
selectorGenerator.buildTextCandidates (cognitive 61) packages/injected/src/selectorGenerator.ts:280— selectorGenerator.buildTextCandidates has cognitive complexity 61 (threshold 15). Drivers by points: if/else 14 (27 pts), loops 7 (21 pts), boolean chains 7, ternaries 4 (6 pts) (nesting depth added 29). 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.
dashboard.Dashboard (cognitive 60) REDACTED:67— dashboard.Dashboard has cognitive complexity 60 (threshold 15). Drivers by points: if/else 26 (27 pts), boolean chains 20, ternaries 12 (13 pts) (nesting depth added 2). Of this number, 31 points are the body's own statements and 29 belong to 22 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
hostPlatform.calculatePlatform (cognitive 59) packages/utils/hostPlatform.ts:41— hostPlatform.calculatePlatform has cognitive complexity 59 (threshold 15). Drivers by points: if/else 25 (53 pts), boolean chains 6 (nesting depth added 28). 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.
webSocketMock.inject (cognitive 57) packages/injected/src/webSocketMock.ts:38— webSocketMock.inject has cognitive complexity 57 (threshold 15). Drivers by points: if/else 42 (43 pts), boolean chains 8, ternaries 3 (4 pts), loops 2 (nesting depth added 2). Of this number, 50 points are the body's own statements and 7 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
markdown.buildTree (cognitive 57) utils/markdown.js:116— markdown.buildTree has cognitive complexity 57 (threshold 15). Drivers by points: if/else 17 (40 pts), loops 6 (14 pts), boolean chains 2, ternaries 1 (nesting depth added 31). Of this number, 52 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Response._build (cognitive 55) packages/playwright-core/src/tools/backend/response.ts:269— Response._build has cognitive complexity 55 (threshold 15). Drivers by points: if/else 22 (35 pts), ternaries 6 (11 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 19). 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.
FrameSession._initialize (cognitive 54) REDACTED:472— FrameSession._initialize has cognitive complexity 54 (threshold 15). Drivers by points: if/else 21 (35 pts), boolean chains 11, loops 4 (6 pts), error handling 1 (2 pts) (nesting depth added 17). Of this number, 47 points are the body's own statements and 7 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.
APIRequestContext._innerFetch (cognitive 53) packages/playwright-core/src/client/fetch.ts:197— APIRequestContext._innerFetch has cognitive complexity 53 (threshold 15). Drivers by points: if/else 20 (31 pts), boolean chains 10, loops 3 (9 pts), ternaries 3 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElementHandle._performPointerAction (cognitive 53) packages/playwright-core/src/server/dom.ts:400— ElementHandle._performPointerAction has cognitive complexity 53 (threshold 15). Drivers by points: if/else 25 (36 pts), ternaries 8 (14 pts), boolean chains 3 (nesting depth added 17). Of this number, 36 points are the body's own statements and 17 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.
SelectorEvaluatorImpl._matchesParents (cognitive 51) REDACTED:265— SelectorEvaluatorImpl._matchesParents has cognitive complexity 51 (threshold 15). Drivers by points: if/else 17 (43 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 29). Most of this is not in the body itself: 1 of the 51 points is its own statement and the rest belongs to one function literal inside it that branches (line 268). 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.
Response.serialize (cognitive 50) packages/playwright-core/src/tools/backend/response.ts:174— Response.serialize has cognitive complexity 50 (threshold 15). Drivers by points: if/else 13 (33 pts), ternaries 7 (12 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 27). 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.
consoleTab.useConsoleTabModel (cognitive 50) REDACTED:64— consoleTab.useConsoleTabModel has cognitive complexity 50 (threshold 15). Drivers by points: if/else 10 (21 pts), ternaries 7 (18 pts), boolean chains 10, loops 1 (nesting depth added 22). None of this is in the body itself: all 50 points belong to 4 function literals inside it that branch (lines 65, 70, 68, …). 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.
generateNameDefault (cognitive 50) utils/doclint/generateDotnetApi.js:417— generateNameDefault has cognitive complexity 50 (threshold 15). Drivers by points: if/else 12 (31 pts), boolean chains 11, loops 2 (6 pts), other 2 (nesting depth added 23). Of this number, 37 points are the body's own statements and 13 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.
HarBackend._harFindResponse (cognitive 49) packages/playwright-core/src/server/harBackend.ts:96— HarBackend._harFindResponse has cognitive complexity 49 (threshold 15). Drivers by points: if/else 11 (36 pts), boolean chains 7, loops 3 (6 pts) (nesting depth added 28). 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.
traceConsole.traceConsole (cognitive 49) REDACTED:21— traceConsole.traceConsole has cognitive complexity 49 (threshold 15). Drivers by points: if/else 14 (30 pts), ternaries 4 (9 pts), boolean chains 7, loops 3 (nesting depth added 21). 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.
selectorGenerator.generateSelectorFor (cognitive 47) packages/injected/src/selectorGenerator.ts:121— selectorGenerator.generateSelectorFor has cognitive complexity 47 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 10, ternaries 2 (6 pts), loops 4 (5 pts) (nesting depth added 18). Of this number, 44 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
jsonSchema.validate (cognitive 47) REDACTED:29— jsonSchema.validate has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (28 pts), loops 4 (9 pts), boolean chains 7, ternaries 1 (3 pts) (nesting depth added 21). 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.
workbench.PartitionedWorkbench (cognitive 47) packages/trace-viewer/src/ui/workbench.tsx:75— workbench.PartitionedWorkbench has cognitive complexity 47 (threshold 15). Drivers by points: if/else 18 (21 pts), boolean chains 16, ternaries 8, loops 1 (2 pts) (nesting depth added 4). Of this number, 22 points are the body's own statements and 25 belong to 10 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.
selectorUtils.elementText (cognitive 46) packages/injected/src/selectorUtils.ts:68— selectorUtils.elementText has cognitive complexity 46 (threshold 15). Drivers by points: if/else 12 (38 pts), boolean chains 4, loops 1 (4 pts) (nesting depth added 29). 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.
selectorParser.parseSelector (cognitive 46) packages/isomorphic/selectorParser.ts:44— selectorParser.parseSelector has cognitive complexity 46 (threshold 15). Drivers by points: if/else 10 (30 pts), boolean chains 6, ternaries 2 (6 pts), error handling 1 (3 pts), loops 1 (nesting depth added 26). Of this number, 45 points are the body's own statements and 1 belongs 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.
TraceModernizer._modernize_8_to_9 (cognitive 46) packages/isomorphic/trace/traceModernizer.ts:487— TraceModernizer._modernize_8_to_9 has cognitive complexity 46 (threshold 15). Drivers by points: if/else 12 (34 pts), loops 3 (7 pts), boolean chains 5 (nesting depth added 26). 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.
InjectedScript.elementState (cognitive 45) REDACTED:788— InjectedScript.elementState has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 11 (23 pts), if/else 11 (15 pts), boolean chains 7 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TraceLoader.load (cognitive 45) packages/isomorphic/trace/traceLoader.ts:39— TraceLoader.load has cognitive complexity 45 (threshold 15). Drivers by points: if/else 9 (25 pts), loops 5 (12 pts), boolean chains 8 (nesting depth added 23). 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.
innerRenderMdNode (cognitive 45) utils/markdown.js:306— innerRenderMdNode has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 11, loops 5 (10 pts), ternaries 2 (4 pts), match/switch 1 (2 pts), other 1 (nesting depth added 13). Of this number, 42 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
codeMirrorWrapper.CodeMirrorWrapper (cognitive 44) packages/web/src/components/codeMirrorWrapper.tsx:52— codeMirrorWrapper.CodeMirrorWrapper has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 13, loops 5 (10 pts) (nesting depth added 12). None of this is in the body itself: all 44 points belong to 4 function literals inside it that branch (lines 131, 79, 126, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
cssParser.parseCSS::consumeSimpleSelector (cognitive 43) packages/isomorphic/cssParser.ts:172— cssParser.parseCSS::consumeSimpleSelector has cognitive complexity 43 (threshold 15). Drivers by points: if/else 18 (34 pts), boolean chains 5, loops 2 (4 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.
roleUtils.innerAccumulatedElementText (cognitive 42) packages/injected/src/roleUtils.ts:1046— roleUtils.innerAccumulatedElementText has cognitive complexity 42 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 5 (15 pts), boolean chains 9, ternaries 2 (3 pts) (nesting depth added 16). Of this number, 27 points are the body's own statements and 15 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
urlMatch.globToRegexPattern (cognitive 42) REDACTED:30— urlMatch.globToRegexPattern has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (29 pts), ternaries 2 (6 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
selectorGenerator.buildNoTextCandidates (cognitive 41) packages/injected/src/selectorGenerator.ts:204— selectorGenerator.buildNoTextCandidates has cognitive complexity 41 (threshold 15). Drivers by points: if/else 13 (21 pts), loops 7 (12 pts), boolean chains 8 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ariaSnapshot.parseAriaSnapshot::convertMap (cognitive 41) packages/isomorphic/ariaSnapshot.ts:175— ariaSnapshot.parseAriaSnapshot::convertMap has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (26 pts), boolean chains 14, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.doFetch (cognitive 41) REDACTED:138— main.doFetch has cognitive complexity 41 (threshold 15). Drivers by points: if/else 21 (37 pts), boolean chains 3, ternaries 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Filter.matches (cognitive 40) packages/html-reporter/src/filter.ts:119— Filter.matches has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (22 pts), ternaries 7 (16 pts), boolean chains 2 (nesting depth added 17). Of this number, 18 points are the body's own statements and 22 belong to 5 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Page.expectScreenshot (cognitive 40) packages/playwright-core/src/server/page.ts:718— Page.expectScreenshot has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 9, ternaries 4 (6 pts), error handling 1, loops 1 (nesting depth added 9). Of this number, 33 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Frame._expectInternal (cognitive 40) packages/playwright-core/src/server/frames.ts:1535— Frame._expectInternal has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 9, ternaries 3 (6 pts) (nesting depth added 11). Of this number, 33 points are the body's own statements and 7 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.
ElementHandle._retryAction (cognitive 40) packages/playwright-core/src/server/dom.ts:328— ElementHandle._retryAction has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (30 pts), ternaries 2 (6 pts), boolean chains 3, loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
treeView.TreeView (cognitive 40) packages/web/src/components/treeView.tsx:53— treeView.TreeView has cognitive complexity 40 (threshold 15). Drivers by points: if/else 21 (27 pts), boolean chains 9, loops 2 (3 pts), ternaries 1 (nesting depth added 7). Most of this is not in the body itself: 3 of the 40 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 143, 107, 94, …). 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.
injectedScript.deepEquals (cognitive 39) REDACTED:1895— injectedScript.deepEquals has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (28 pts), loops 3 (7 pts), boolean chains 4 (nesting depth added 19). 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.
CRNetworkManager._onRequest (cognitive 39) packages/playwright-core/src/server/chromium/crNetworkManager.ts:295— CRNetworkManager._onRequest has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 17, ternaries 2 (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.
traceRequests.traceRequest (cognitive 39) REDACTED:75— traceRequests.traceRequest has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (23 pts), ternaries 6 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
recorder.Recorder (cognitive 39) packages/recorder/src/recorder.tsx:37— recorder.Recorder has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 16, if/else 9 (11 pts), ternaries 9 (10 pts), loops 1, match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 12 of the 39 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 83, 112, 139, …). 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.
build_deps_true.collectImports (cognitive 39) utils/build_deps_true.js:114— build_deps_true.collectImports has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (34 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FilePickerOverride._createPicker (cognitive 36) browser_patches/firefox/juggler/TargetRegistry.js:312— FilePickerOverride._createPicker has cognitive complexity 36 (threshold 15). Drivers by points: if/else 19, ternaries 16, boolean chains 1. Of this number, 31 points are the body's own statements and 5 belong to 3 function literals 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.
FrameSelectors._callOnSelectorInternal (cognitive 36) packages/playwright-core/src/server/frameSelectors.ts:233— FrameSelectors._callOnSelectorInternal has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (21 pts), ternaries 4 (8 pts), boolean chains 6, loops 1 (nesting depth added 14). Most of this is not in the body itself: 13 of the 36 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 250, getResult, a function literal at line 274). 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.
generateDotnetApi.renderMember (cognitive 36) utils/doclint/generateDotnetApi.js:341— generateDotnetApi.renderMember has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (25 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.
selectorGenerator.cssFallback (cognitive 35) packages/injected/src/selectorGenerator.ts:359— selectorGenerator.cssFallback has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (26 pts), ternaries 2 (4 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 18). Of this number, 32 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextOutput.list (cognitive 35) packages/playwright-core/src/tools/cli-client/output.ts:143— TextOutput.list has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 7 (13 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ariaSnapshot.matchesNode (cognitive 34) REDACTED:381— ariaSnapshot.matchesNode has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 19, if/else 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.
roleSelectorEngine.queryRole::match (cognitive 34) packages/injected/src/roleSelectorEngine.ts:145— roleSelectorEngine.queryRole::match has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 10 (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.
browserActions.launchContext (cognitive 34) REDACTED:66— browserActions.launchContext has cognitive complexity 34 (threshold 15). Drivers by points: if/else 22 (26 pts), error handling 2 (4 pts), boolean chains 2, ternaries 2 (nesting depth added 6). Of this number, 33 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
timeline.Timeline (cognitive 34) packages/trace-viewer/src/ui/timeline.tsx:37— timeline.Timeline has cognitive complexity 34 (threshold 15). Drivers by points: if/else 21 (24 pts), boolean chains 8, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 3 of the 34 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 90, 66, 135, …). 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.
workbenchLoader.WorkbenchLoader (cognitive 34) REDACTED:27— workbenchLoader.WorkbenchLoader has cognitive complexity 34 (threshold 15). Drivers by points: if/else 18 (20 pts), boolean chains 11, ternaries 2, loops 1 (nesting depth added 2). Most of this is not in the body itself: 10 of the 34 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 103, 147, 56, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
documentation.processCodeGroups (cognitive 34) utils/doclint/documentation.js:913— documentation.processCodeGroups has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 3 (6 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 21). 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.
patchLinksInText (cognitive 34) utils/doclint/documentation.js:755— patchLinksInText has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 8, ternaries 1 (2 pts) (nesting depth added 13). None of this is in the body itself: all 34 points belong to 5 function literals inside it that branch (lines 756, 807, 787, …). 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.
TraceModel.constructor (cognitive 33) packages/isomorphic/trace/traceModel.ts:98— TraceModel.constructor has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 15, loops 8 (12 pts), if/else 3 (6 pts) (nesting depth added 7). 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.
cookieStore.parseRawCookie (cognitive 33) packages/playwright-core/src/server/cookieStore.ts:135— cookieStore.parseRawCookie has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (23 pts), match/switch 2 (5 pts), boolean chains 4, loops 1 (nesting depth added 15). Of this number, 31 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.
BidiConnection._dispatchMessage (cognitive 33) packages/playwright-core/src/server/bidi/bidiConnection.ts:70— BidiConnection._dispatchMessage has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (25 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WVPage._onConsoleMessage (cognitive 33) packages/playwright-core/src/server/webkit/webview/wvPage.ts:532— WVPage._onConsoleMessage has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 13, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
serializers.innerParseSerializedValue (cognitive 33) REDACTED:35— serializers.innerParseSerializedValue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 22 (29 pts), loops 2 (4 pts) (nesting depth added 9). 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.
check_deps.innerCheckDeps (cognitive 33) utils/check_deps.js:65— check_deps.innerCheckDeps has cognitive complexity 33 (threshold 15). Drivers by points: if/else 43 (81 pts), loops 11 (23 pts), boolean chains 16, ternaries 4 (7 pts), error handling 2 (4 pts) (nesting depth added 55). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (check_deps.innerCheckDeps::visit, check_deps.innerCheckDeps::calculateDeps, check_deps.innerCheckDeps::allowImport) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ariaSnapshot.renderAriaTreeAsJSON::visit (cognitive 32) REDACTED:472— ariaSnapshot.renderAriaTreeAsJSON::visit has cognitive complexity 32 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 10, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
BidiNetworkManager._onBeforeRequestSent (cognitive 32) packages/playwright-core/src/server/bidi/bidiNetworkManager.ts:62— BidiNetworkManager._onBeforeRequestSent has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 4, ternaries 3 (4 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserBackend.callTool (cognitive 32) packages/playwright-core/src/tools/backend/browserBackend.ts:89— BrowserBackend.callTool has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 5 (14 pts), if/else 6 (12 pts), error handling 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 16). Of this number, 26 points are the body's own statements and 6 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.
validate_deps.validateDirectory (cognitive 32) utils/validate_deps.js:126— validate_deps.validateDirectory has cognitive complexity 32 (threshold 15). Drivers by points: loops 6 (16 pts), if/else 7 (15 pts), boolean chains 1 (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
InjectedScript.expectHitTarget (cognitive 31) REDACTED:1037— InjectedScript.expectHitTarget has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 5, loops 4 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Chromium.launchWithSeleniumHub (cognitive 31) REDACTED:213— Chromium.launchWithSeleniumHub has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 5 (8 pts), boolean chains 6, error handling 2 (4 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.
istanbulCoverage.mergeIstanbulCoverage (cognitive 30) packages/isomorphic/istanbulCoverage.ts:72— istanbulCoverage.mergeIstanbulCoverage has cognitive complexity 30 (threshold 15). Drivers by points: loops 7 (16 pts), boolean chains 10, if/else 2 (4 pts) (nesting depth added 11). 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, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
traceModel.mergeActionsAndUpdateTimingSameTrace (cognitive 30) packages/isomorphic/trace/traceModel.ts:291— traceModel.mergeActionsAndUpdateTimingSameTrace has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 5 (7 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
config.validateBrowserConfig (cognitive 30) packages/playwright-core/src/tools/mcp/config.ts:226— config.validateBrowserConfig has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generateDotnetApi.renderMethod (cognitive 30) utils/doclint/generateDotnetApi.js:515— generateDotnetApi.renderMethod has cognitive complexity 30 (threshold 15). Drivers by points: if/else 39 (67 pts), boolean chains 11, ternaries 4 (5 pts), loops 2 (4 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (generateDotnetApi.renderMethod::processArg) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
WebKit.defaultArgs (cognitive 29) packages/playwright-core/src/server/webkit/webkit.ts:101— WebKit.defaultArgs has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
program.killAllDaemons (cognitive 29) packages/playwright-core/src/tools/cli-client/program.ts:364— program.killAllDaemons has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (16 pts), error handling 2 (6 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
stackTrace.parseStackFrame (cognitive 29) packages/utils/stackTrace.ts:45— stackTrace.parseStackFrame has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
listView.ListView (cognitive 29) packages/web/src/components/listView.tsx:43— listView.ListView has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 14, if/else 10 (12 pts), ternaries 3 (nesting depth added 2). Most of this is not in the body itself: 3 of the 29 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 89, 124, 80, …). 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.
parseOverrides.parseOverrides (cognitive 29) utils/generate_types/parseOverrides.js:26— parseOverrides.parseOverrides has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 4 (7 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 10). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 4 function items inside it that branch (visit, serializeClass, visitProperties, …). 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.
(anonymous) (cognitive 29) utils/linux-browser-dependencies/inside_docker/list_dependencies.js:27— (anonymous) has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 10 (12 pts), boolean chains 2, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.jsonToTS (cognitive 28) utils/protocol-types-generator/index.js:40— index.jsonToTS has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 14 (18 pts), boolean chains 10 (nesting depth added 4). None of this is in the body itself: all 28 points belong to 12 function literals inside it that branch (lines 43, 47, 69, …). 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.
InjectedScript.selectOptions (cognitive 27) REDACTED:856— InjectedScript.selectOptions has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 6, loops 1 (nesting depth added 8). Most of this is not in the body itself: 11 of the 27 points are its own statements and the rest belongs to 2 function items inside it that branch (filter, filter::matchesLabel). 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.
PythonLocatorFactory.generateLocator (cognitive 27) packages/isomorphic/locatorGenerators.ts:416— PythonLocatorFactory.generateLocator has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 3 (7 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 12). 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.
EventEmitter.removeListener (cognitive 27) packages/playwright-core/src/client/eventEmitter.ts:199— EventEmitter.removeListener has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check_dependency_age.main (cognitive 27) utils/check_dependency_age.js:126— check_dependency_age.main has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 6 (8 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 10). Of this number, 17 points are the body's own statements and 10 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypesGenerator.classBody (cognitive 27) utils/generate_types/index.js:261— TypesGenerator.classBody has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 4 (6 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 8). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 281). 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.
validate_deps.isEntryUsed (cognitive 27) utils/validate_deps.js:177— validate_deps.isEntryUsed has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TargetRegistry.constructor (cognitive 26) browser_patches/firefox/juggler/TargetRegistry.js:373— TargetRegistry.constructor has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 6, loops 4 (nesting depth added 1). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (onOpenWindow, onTabOpenListener, onCloseWindow, …). 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.
reportView.ReportView (cognitive 26) packages/html-reporter/src/reportView.tsx:49— reportView.ReportView has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (9 pts), ternaries 4, loops 2 (3 pts), match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 26 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 89, 62, 72, …). 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.
selectorParser.parseSelectorString (cognitive 26) packages/isomorphic/selectorParser.ts:184— selectorParser.parseSelectorString has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 9, loops 1 (nesting depth added 2). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 2 function items inside it that branch (append, shouldIgnoreTextSelectorQuote). 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.
Frame.waitForSelector (cognitive 26) packages/playwright-core/src/server/frames.ts:837— Frame.waitForSelector has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (16 pts), ternaries 4 (5 pts), boolean chains 4, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 848, 855). 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.
APIRequestContext.fetch (cognitive 26) packages/playwright-core/src/server/fetch.ts:197— APIRequestContext.fetch has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 3 (6 pts), boolean chains 4, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
serializers.innerSerializeValue (cognitive 26) REDACTED:118— serializers.innerSerializeValue has cognitive complexity 26 (threshold 15). Drivers by points: if/else 21, loops 2 (4 pts), boolean chains 1 (nesting depth added 2). 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.
bisect-chromium.findExecutable (cognitive 26) REDACTED:97— bisect-chromium.findExecutable has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (19 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ApiParser.parseArgument (cognitive 26) utils/doclint/api_parser.js:146— ApiParser.parseArgument has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 8). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 26) utils/roll_browser.js:47— (anonymous) has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 5, loops 2 (4 pts), other 1 (nesting depth added 5). Of this number, 25 points are the body's own statements and 1 belongs 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.
parseMember (cognitive 26) utils/doclint/api_parser.js:91— parseMember has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 6, loops 2 (3 pts), other 1 (nesting depth added 4). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
InjectedScript.dispatchEvent (cognitive 25) REDACTED:1223— InjectedScript.dispatchEvent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 5, error handling 2 (4 pts), match/switch 1 (nesting depth added 11). Most of this is not in the body itself: 8 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (createTouch, createTouchList, a function literal at line 1256, …). 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.
webAuthn.inject (cognitive 25) packages/injected/src/webAuthn.ts:59— webAuthn.inject has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 14, if/else 6, loops 4, ternaries 1. Of this number, 14 points are the body's own statements and 11 belong to 11 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
selectorParser.splitSelectorByFrame (cognitive 25) packages/isomorphic/selectorParser.ts:108— selectorParser.splitSelectorByFrame has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 7, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JavaLocatorFactory.generateLocator (cognitive 25) packages/isomorphic/locatorGenerators.ts:526— JavaLocatorFactory.generateLocator has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 3 (7 pts), boolean chains 2, loops 1 (2 pts), match/switch 2 (nesting depth added 10). 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.
protocolFormatter._formatProtocolParam (cognitive 25) packages/isomorphic/protocolFormatter.ts:35— protocolFormatter._formatProtocolParam has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), error handling 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
urlMatch.resolveGlobBase (cognitive 25) REDACTED:214— urlMatch.resolveGlobBase has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 11). Most of this is not in the body itself: 9 of the 25 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 232, mapToken). 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.
HarTracer._onRequestFinished (cognitive 25) packages/playwright-core/src/server/har/harTracer.ts:330— HarTracer._onRequestFinished has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 8, ternaries 3 (nesting depth added 4). Of this number, 15 points are the body's own statements and 10 belong to 4 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.
HarTracer._onWebSocket (cognitive 25) packages/playwright-core/src/server/har/harTracer.ts:445— HarTracer._onWebSocket has cognitive complexity 25 (threshold 15). Drivers by points: if/else 18 (20 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 3). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (recordMessage, a function literal at line 512, updateTime, …). 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.
Connection.dispatch (cognitive 25) packages/playwright-core/src/client/connection.ts:236— Connection.dispatch has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
config.configFromCLIOptions (cognitive 25) packages/playwright-core/src/tools/mcp/config.ts:302— config.configFromCLIOptions has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 3, ternaries 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
callTab.parseSerializedValue (cognitive 25) REDACTED:129— callTab.parseSerializedValue has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (23 pts), loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
snapshotTab.collectSnapshots (cognitive 25) packages/trace-viewer/src/ui/snapshotTab.tsx:403— snapshotTab.collectSnapshots has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 5, loops 2 (4 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.
compare.compare (cognitive 25) packages/utils/image_tools/compare.ts:36— compare.compare has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 3, loops 2 (3 pts), ternaries 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
roleSelectorEngine.validateAttributes (cognitive 24) packages/injected/src/roleSelectorEngine.ts:61— roleSelectorEngine.validateAttributes has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (18 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JavaScriptLocatorFactory.generateLocator (cognitive 24) packages/isomorphic/locatorGenerators.ts:313— JavaScriptLocatorFactory.generateLocator has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 3 (7 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 10). 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. This shape REPEATS in the file: one other method here (CSharpLocatorFactory.generateLocator) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CSharpLocatorFactory.generateLocator (cognitive 24) packages/isomorphic/locatorGenerators.ts:638— CSharpLocatorFactory.generateLocator has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 3 (7 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 10). 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. This shape REPEATS in the file: one other method here (JavaScriptLocatorFactory.generateLocator) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
input.buildLayoutClosure (cognitive 24) packages/playwright-core/src/server/input.ts:307— input.buildLayoutClosure has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Frame.gotoImpl (cognitive 24) packages/playwright-core/src/server/frames.ts:695— Frame.gotoImpl has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, ternaries 4 (nesting depth added 5). Of this number, 22 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Frame.expect (cognitive 24) packages/playwright-core/src/server/frames.ts:1473— Frame.expect has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), error handling 3 (4 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 6). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
program.decorateMCPCommand (cognitive 24) packages/playwright-core/src/tools/mcp/program.ts:34— program.decorateMCPCommand has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 5, ternaries 2 (3 pts), error handling 2 (nesting depth added 4). None of this is in the body itself: all 24 points belong to 5 function literals inside it that branch (lines 120, 175, 94, …). 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.
consoleTab.format (cognitive 24) REDACTED:221— consoleTab.format has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 3 (5 pts), boolean chains 4, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ariaModeView.collectAriaModeTargets (cognitive 24) packages/trace-viewer/src/ui/ariaModeView.tsx:48— ariaModeView.collectAriaModeTargets has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 2 (4 pts), ternaries 3 (nesting depth added 8). Of this number, 23 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.
snapshotTab.InspectModeController (cognitive 24) packages/trace-viewer/src/ui/snapshotTab.tsx:291— snapshotTab.InspectModeController has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 7 (10 pts), if/else 3 (6 pts), error handling 2 (3 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). None of this is in the body itself: all 24 points belong to one function literal inside it that branches (line 292). 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.
documentation.patchCSharpOptionOverloads (cognitive 24) utils/doclint/documentation.js:835— documentation.patchCSharpOptionOverloads has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generate_channels.inlineType (cognitive 24) utils/generate_channels.js:34— generate_channels.inlineType has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 2, 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.
debuggerPanel.DebuggerPanel (cognitive 23) packages/dashboard/src/debuggerPanel.tsx:33— debuggerPanel.DebuggerPanel has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 14, if/else 6 (7 pts), ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 89, 50, 44, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
InjectedScript.querySelectorAll (cognitive 23) REDACTED:376— InjectedScript.querySelectorAll has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 8). 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.
JavaScriptLanguageGenerator._generateActionCall (cognitive 23) packages/isomorphic/codegen/javascript.ts:97— JavaScriptLanguageGenerator._generateActionCall has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 10 (20 pts), if/else 1 (2 pts), match/switch 1 (nesting depth added 11). 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.
PythonLanguageGenerator.generateHeader (cognitive 23) packages/isomorphic/codegen/python.ts:160— PythonLanguageGenerator.generateHeader has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (13 pts), if/else 6 (9 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SnapshotRenderer.resourceByUrl (cognitive 23) REDACTED:219— SnapshotRenderer.resourceByUrl has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 4, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
locatorParser.tokenize::readString (cognitive 23) packages/isomorphic/locatorParser.ts:82— locatorParser.tokenize::readString has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HarTracer._onResponse (cognitive 23) packages/playwright-core/src/server/har/harTracer.ts:568— HarTracer._onResponse has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 5 (9 pts), boolean chains 4 (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.
FrameSession._updateViewport (cognitive 23) REDACTED:1011— FrameSession._updateViewport has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (18 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
installActions.installBrowsers (cognitive 23) packages/playwright-core/src/cli/installActions.ts:90— installActions.installBrowsers has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (6 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
sourceTab.useSources (cognitive 23) packages/trace-viewer/src/ui/sourceTab.tsx:37— sourceTab.useSources has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, ternaries 3 (4 pts), error handling 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 23 points belong to one function literal inside it that branches (line 39). 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.
RecordActionTool._shouldGenerateKeyPressFor (cognitive 22) packages/injected/src/recorder/recorder.ts:609— RecordActionTool._shouldGenerateKeyPressFor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 8 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (JsonRecordActionTool._shouldGenerateKeyPressFor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
JsonRecordActionTool._shouldGenerateKeyPressFor (cognitive 22) packages/injected/src/recorder/recorder.ts:810— JsonRecordActionTool._shouldGenerateKeyPressFor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 8 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (RecordActionTool._shouldGenerateKeyPressFor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TraceModernizer._innerAppendEvent (cognitive 22) packages/isomorphic/trace/traceModernizer.ts:107— TraceModernizer._innerAppendEvent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 6, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
elementHandle.convertInputFiles (cognitive 22) packages/playwright-core/src/client/elementHandle.ts:282— elementHandle.convertInputFiles has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 5 (13 pts), if/else 4 (6 pts), loops 1 (3 pts) (nesting depth added 12). Of this number, 16 points are the body's own statements and 6 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.
Registry.constructor (cognitive 22) packages/playwright-core/src/server/registry/index.ts:510— Registry.constructor has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (11 pts), if/else 8 (9 pts), boolean chains 2 (nesting depth added 2). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (executablePathOrDie, a function literal at line 747, findExecutablePath, …). 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.
WKPage._onConsoleMessage (cognitive 22) packages/playwright-core/src/server/webkit/wkPage.ts:538— WKPage._onConsoleMessage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 10, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
localUtils.zip (cognitive 22) packages/playwright-core/src/server/localUtils.ts:44— localUtils.zip has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 4 (8 pts), boolean chains 1, error handling 1, ternaries 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ElementHandle._setInputFiles (cognitive 22) packages/playwright-core/src/server/dom.ts:746— ElementHandle._setInputFiles has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 3). Of this number, 14 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
api_parser.applyTemplates::visit (cognitive 22) utils/doclint/api_parser.js:334— api_parser.applyTemplates::visit has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6, loops 2 (3 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.
generate_dotnet_channels.inlineType (cognitive 22) utils/generate_dotnet_channels.js:81— generate_dotnet_channels.inlineType has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (22 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.
TypesGenerator.stringifySimpleType (cognitive 22) utils/generate_types/index.js:420— TypesGenerator.stringifySimpleType has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
setCookies (cognitive 22) browser_patches/firefox/juggler/TargetRegistry.js:1459— setCookies has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (7 pts), boolean chains 4, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sessionSidebar.SessionSidebar (cognitive 21) packages/dashboard/src/sessionSidebar.tsx:79— sessionSidebar.SessionSidebar has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 7, if/else 3 (6 pts), ternaries 4 (5 pts), loops 3 (nesting depth added 4). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 103, 83, 138, …). 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.
bidiInsertText.bidiInsertText (cognitive 21) packages/injected/src/bidiInsertText.ts:19— bidiInsertText.bidiInsertText has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, loops 2 (3 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.
Route._innerFulfill (cognitive 21) packages/playwright-core/src/client/network.ts:386— Route._innerFulfill has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 5, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Registry.install (cognitive 21) packages/playwright-core/src/server/registry/index.ts:934— Registry.install has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, ternaries 1 (3 pts), error handling 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
traceActions.traceAction (cognitive 21) REDACTED:65— traceActions.traceAction has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 7, ternaries 3 (6 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
traceRequests.traceRequests (cognitive 21) REDACTED:23— traceRequests.traceRequests has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3 (6 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
consoleTab.ConsoleTab (cognitive 21) REDACTED:165— consoleTab.ConsoleTab has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 7, if/else 6 (7 pts), ternaries 5 (7 pts) (nesting depth added 3). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 177, 173). 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.
ansi2html.ansi2html (cognitive 21) packages/web/src/ansi2html.ts:17— ansi2html.ansi2html has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (4 pts), match/switch 1 (4 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
splitView.SplitView (cognitive 21) packages/web/src/components/splitView.tsx:35— splitView.SplitView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5, ternaries 2 (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.
generateDotnetApi.renderMethod::processArg (cognitive 21) utils/doclint/generateDotnetApi.js:596— generateDotnetApi.renderMethod::processArg has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (generateDotnetApi.renderMethod) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
fromParsedType (cognitive 21) utils/doclint/documentation.js:523— fromParsedType has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 6, loops 3 (6 pts), 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.
PageHandler.['Page.dispatchMouseEvent'] (cognitive 20) REDACTED:483— PageHandler.['Page.dispatchMouseEvent'] has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). None of this is in the body itself: all 20 points belong to 2 function items inside it that branch (a function literal at line 523, sendEvents). 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.
annotations.Annotations::onLayerKeyDown (cognitive 20) packages/dashboard/src/annotations.tsx:297— annotations.Annotations::onLayerKeyDown has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3, 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.
Filter.tokenize (cognitive 20) packages/html-reporter/src/filter.ts:78— Filter.tokenize has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ariaSnapshot.toAriaNode (cognitive 20) REDACTED:239— ariaSnapshot.toAriaNode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 6, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
traceModel.adjustMonotonicTime (cognitive 20) packages/isomorphic/trace/traceModel.ts:342— traceModel.adjustMonotonicTime has cognitive complexity 20 (threshold 15). Drivers by points: loops 9 (10 pts), if/else 4 (7 pts), boolean chains 3 (nesting depth added 4). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
bidiExecutionContext.renderPreview (cognitive 20) REDACTED:203— bidiExecutionContext.renderPreview has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 3 (7 pts), boolean chains 3, loops 1 (2 pts), match/switch 1 (nesting depth added 9). 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.
Chromium._innerDefaultArgs (cognitive 20) REDACTED:328— Chromium._innerDefaultArgs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). Of this number, 17 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.
BidiChromium._innerDefaultArgs (cognitive 20) packages/playwright-core/src/server/bidi/bidiChromium.ts:105— BidiChromium._innerDefaultArgs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). Of this number, 17 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.
BrowserContextDispatcher.constructor (cognitive 20) packages/playwright-core/src/server/dispatchers/browserContextDispatcher.ts:71— BrowserContextDispatcher.constructor has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 11, if/else 6, loops 2 (3 pts) (nesting depth added 1). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 124, 155, 179, …). 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.
(computed) (cognitive 20) REDACTED:483— (computed) has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). None of this is in the body itself: all 20 points belong to 3 function items inside it that branch (a function literal at line 523, sendEvents, a function literal at line 496). 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.
PageAgent._dispatchKeyEvent (cognitive 19) browser_patches/firefox/juggler/content/PageAgent.js:495— PageAgent._dispatchKeyEvent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3 (nesting depth added 7). Of this number, 14 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InjectedScript.previewNode (cognitive 19) REDACTED:1290— InjectedScript.previewNode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, loops 2 (3 pts), ternaries 2 (3 pts) (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.
ClockController._replayLogOnce (cognitive 19) packages/injected/src/clock.ts:446— ClockController._replayLogOnce has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ariaSnapshot.findNewNode (cognitive 19) packages/isomorphic/ariaSnapshot.ts:545— ariaSnapshot.findNewNode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to one function item inside it that branches (fillMap). 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.
EventEmitter._removeAllListeners (cognitive 19) packages/playwright-core/src/client/eventEmitter.ts:275— EventEmitter._removeAllListeners has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserContext.constructor (cognitive 19) packages/playwright-core/src/client/browserContext.ts:98— BrowserContext.constructor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 4). None of this is in the body itself: all 19 points belong to 5 function literals inside it that branch (lines 120, 142, 170, …). 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.
crCoverage.convertToDisjointRanges (cognitive 19) packages/playwright-core/src/server/chromium/crCoverage.ts:240— crCoverage.convertToDisjointRanges has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 1 (3 pts), boolean chains 2, loops 2 (nesting depth added 6). Of this number, 16 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.
FFBrowserContext.initialize (cognitive 19) packages/playwright-core/src/server/firefox/ffBrowser.ts:172— FFBrowserContext.initialize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, boolean chains 3, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WKPage._onTargetCreated (cognitive 19) packages/playwright-core/src/server/webkit/wkPage.ts:309— WKPage._onTargetCreated has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (5 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserContext.setStorageState (cognitive 19) REDACTED:666— BrowserContext.setStorageState has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 2 (4 pts), boolean chains 1, error handling 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Session.deleteData (cognitive 19) packages/playwright-core/src/tools/cli-client/session.ts:62— Session.deleteData has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SimpleChannel._onMessageInternal (cognitive 18) browser_patches/firefox/juggler/SimpleChannel.js:197— SimpleChannel._onMessageInternal has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 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.
roleUtils.getCSSContent (cognitive 18) packages/injected/src/roleUtils.ts:426— roleUtils.getCSSContent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Highlight.updateHighlight (cognitive 18) packages/injected/src/highlight.ts:389— Highlight.updateHighlight has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3, boolean chains 2 (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.
SelectorEvaluatorImpl._querySimple (cognitive 18) REDACTED:227— SelectorEvaluatorImpl._querySimple has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2, loops 2 (nesting depth added 5). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 231). 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.
selectorEvaluator.sortInDOMOrder (cognitive 18) REDACTED:555— selectorEvaluator.sortInDOMOrder has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function items inside it that branch (visit, append). 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.
selectorGenerator.generateSelector (cognitive 18) packages/injected/src/selectorGenerator.ts:78— selectorGenerator.generateSelector has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
selectorGenerator.isGuidLike (cognitive 18) packages/injected/src/selectorGenerator.ts:462— selectorGenerator.isGuidLike has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InjectedScript.retarget (cognitive 18) REDACTED:674— InjectedScript.retarget has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 5, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InjectedScript.setupHitTargetInterceptor (cognitive 18) REDACTED:1153— InjectedScript.setupHitTargetInterceptor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 7, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (listener, stop). 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.
RecordActionTool.onInput (cognitive 18) packages/injected/src/recorder/recorder.ts:369— RecordActionTool.onInput has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 3 (6 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FrameSelectors._queryFrames (cognitive 18) packages/playwright-core/src/server/frameSelectors.ts:171— FrameSelectors._queryFrames has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 4, ternaries 3 (4 pts), loops 2 (nesting depth added 3). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 177, query, a function literal at line 204). 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.
HarTracer.stop (cognitive 18) packages/playwright-core/src/server/har/harTracer.ts:658— HarTracer.stop has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, loops 1 (2 pts), ternaries 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InterceptableRequest.createResponseBodyCallback (cognitive 18) packages/playwright-core/src/server/chromium/crNetworkManager.ts:610— InterceptableRequest.createResponseBodyCallback has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 4 (6 pts), boolean chains 2, loops 1 (nesting depth added 4). None of this is in the body itself: all 18 points belong to 2 function literals inside it that branch (lines 611, 635). 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.
dependencies.validateDependenciesLinux (cognitive 18) packages/playwright-core/src/server/registry/dependencies.ts:213— dependencies.validateDependenciesLinux has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (6 pts), loops 5 (6 pts), boolean chains 4, ternaries 2 (nesting depth added 2). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Registry.resolveBrowsers (cognitive 18) packages/playwright-core/src/server/registry/index.ts:1292— Registry.resolveBrowsers has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, loops 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Electron.launch (cognitive 18) packages/playwright-core/src/server/electron/electron.ts:180— Electron.launch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, error handling 2 (3 pts), ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
callTab.propertyToString (cognitive 18) REDACTED:102— callTab.propertyToString has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 7, ternaries 1 (2 pts) (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.
ariaModeView.AriaModeView (cognitive 18) packages/trace-viewer/src/ui/ariaModeView.tsx:148— ariaModeView.AriaModeView has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 6, if/else 4. Of this number, 14 points are the body's own statements and 4 belong to 3 function literals 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.
imageDiffView.ImageDiffView (cognitive 18) packages/web/src/shared/imageDiffView.tsx:66— imageDiffView.ImageDiffView has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 14, ternaries 4. Of this number, 16 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Member.filterForLanguage (cognitive 18) utils/doclint/documentation.js:395— Member.filterForLanguage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 7, error handling 1 (2 pts), loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parseTypeExpression (cognitive 18) utils/doclint/documentation.js:670— parseTypeExpression has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_innerRenderNodes (cognitive 18) utils/doclint/dotnetXmlDocumentation.js:36— _innerRenderNodes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6, other 1 (nesting depth added 1). None of this is in the body itself: all 18 points belong to 2 function items inside it that branch (a function literal at line 48, handleListItem). 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.
NetworkObserver.responseHead (cognitive 17) browser_patches/firefox/juggler/NetworkObserver.js:1038— NetworkObserver.responseHead has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 3 (5 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.
connect.ConnectApp (cognitive 17) packages/extension/src/ui/connect.tsx:68— connect.ConnectApp has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 7, ternaries 2. Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 83, a function literal at line 73, toggleGroup, …). 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.
domUtils.getAssociatedLabels (cognitive 17) packages/injected/src/domUtils.ts:68— domUtils.getAssociatedLabels has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, 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.
selectorUtils.matchesAttributePart (cognitive 17) packages/injected/src/selectorUtils.ts:32— selectorUtils.matchesAttributePart has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
injectedScript.createTextMatcher (cognitive 17) REDACTED:1798— injectedScript.createTextMatcher has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6, ternaries 1 (nesting depth added 2). Of this number, 14 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
java.formatContextOptions (cognitive 17) packages/isomorphic/codegen/java.ts:254— java.formatContextOptions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15, boolean chains 1, ternaries 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
imageUtils.scaleImageToSize (cognitive 17) packages/isomorphic/imageUtils.ts:43— imageUtils.scaleImageToSize has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (8 pts), boolean chains 3, if/else 3, ternaries 2 (3 pts) (nesting depth added 4). Of this number, 14 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ChannelOwner._wrapApiCall (cognitive 17) packages/playwright-core/src/client/channelOwner.ts:189— ChannelOwner._wrapApiCall has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, ternaries 1 (2 pts), error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FrameSelectors.resolveFramesForSelector (cognitive 17) packages/playwright-core/src/server/frameSelectors.ts:123— FrameSelectors.resolveFramesForSelector has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 4, ternaries 2 (4 pts), loops 2 (nesting depth added 5). Of this number, 11 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.
Tracing._stopChunk (cognitive 17) packages/playwright-core/src/server/trace/recorder/tracing.ts:458— Tracing._stopChunk has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DispatcherConnection.dispatch (cognitive 17) packages/playwright-core/src/server/dispatchers/dispatcher.ts:297— DispatcherConnection.dispatch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), error handling 2, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Credentials._handleGet (cognitive 17) packages/playwright-core/src/server/credentials.ts:186— Credentials._handleGet has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, loops 2 (4 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.
browserContext.verifyClientCertificates (cognitive 17) REDACTED:791— browserContext.verifyClientCertificates has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
traceViewer.startTraceViewerServer (cognitive 17) packages/playwright-core/src/server/trace/viewer/traceViewer.ts:90— traceViewer.startTraceViewerServer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (serveTraceDataRoute, a function literal at line 134, a function literal at line 145). 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.
ContextDebugger._updateSource (cognitive 17) packages/playwright-core/src/tools/dashboard/dashboardController.ts:517— ContextDebugger._updateSource has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 4). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Type.parse (cognitive 17) utils/doclint/documentation.js:489— Type.parse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
observe (cognitive 17) browser_patches/firefox/juggler/components/Juggler.js:70— observe has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (nesting depth added 8). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (loadStyleSheet, receiveMessage, disconnected, …). 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.
constructor (cognitive 17) browser_patches/firefox/juggler/content/PageAgent.js:83— constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (4 pts), loops 3, boolean chains 1 (nesting depth added 5). Of this number, 15 points are the body's own statements and 2 belong to 10 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.
roleUtils.isElementHiddenForAria (cognitive 16) packages/injected/src/roleUtils.ts:314— roleUtils.isElementHiddenForAria has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Highlight._ensureElementHighlightRaf (cognitive 16) packages/injected/src/highlight.ts:142— Highlight._ensureElementHighlightRaf has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (10 pts), loops 2 (3 pts), error handling 1 (2 pts), if/else 1 (nesting depth added 8). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function item inside it that branches (tick). 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.
clock.install (cognitive 16) packages/injected/src/clock.ts:850— clock.install has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KeyParser._readAttributes (cognitive 16) packages/isomorphic/ariaSnapshot.ts:442— KeyParser._readAttributes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TraceModernizer._modernize_9_to_10 (cognitive 16) packages/isomorphic/trace/traceModernizer.ts:548— TraceModernizer._modernize_9_to_10 has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventEmitter._addListener (cognitive 16) packages/playwright-core/src/client/eventEmitter.ts:124— EventEmitter._addListener has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
screenshotter.inPagePrepareForScreenshots::handleAnimations (cognitive 16) packages/playwright-core/src/server/screenshotter.ts:111— screenshotter.inPagePrepareForScreenshots::handleAnimations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), error handling 2 (6 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (screenshotter.inPagePrepareForScreenshots) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
screenshotter.inPagePrepareForScreenshots (cognitive 16) packages/playwright-core/src/server/screenshotter.ts:49— screenshotter.inPagePrepareForScreenshots has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 7 (13 pts), error handling 3 (11 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (screenshotter.inPagePrepareForScreenshots::handleAnimations) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CRBrowser._onAttachedToTarget (cognitive 16) packages/playwright-core/src/server/chromium/crBrowser.ts:185— CRBrowser._onAttachedToTarget has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 7, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
instrumentation.createInstrumentation (cognitive 16) packages/playwright-core/src/server/instrumentation.ts:136— instrumentation.createInstrumentation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 2, loops 2, ternaries 1 (nesting depth added 3). None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 159, 140, 144). 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.
program.collectList (cognitive 16) packages/playwright-core/src/tools/cli-client/program.ts:417— program.collectList has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 2 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
attachmentsTab.AttachmentsTab (cognitive 16) packages/trace-viewer/src/ui/attachmentsTab.tsx:95— attachmentsTab.AttachmentsTab has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 4 (6 pts), ternaries 3, loops 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 97, 125, 145). 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.
networkResourceDetails.dumpHex (cognitive 16) packages/trace-viewer/src/ui/networkResourceDetails.tsx:568— networkResourceDetails.dumpHex has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 1 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
networkTab.renderCell (cognitive 16) packages/trace-viewer/src/ui/networkTab.tsx:185— networkTab.renderCell has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, ternaries 3 (7 pts) (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.
snapshotTab.SnapshotView (cognitive 16) packages/trace-viewer/src/ui/snapshotTab.tsx:139— snapshotTab.SnapshotView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 146, 193). 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.
ImageChannel.intoRGB (cognitive 16) packages/utils/image_tools/imageChannel.ts:30— ImageChannel.intoRGB has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 2 (8 pts), if/else 2 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
comparators.compareImages (cognitive 16) packages/utils/comparators.ts:58— comparators.compareImages has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, boolean chains 4, ternaries 2. Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: 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.
HttpServer._onRequest (cognitive 16) REDACTED:294— HttpServer._onRequest has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
socksProxy.parsePattern (cognitive 16) REDACTED:334— socksProxy.parsePattern has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 338, 366, 347, …). 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.
treeView.TreeItemHeader (cognitive 16) packages/web/src/components/treeView.tsx:239— treeView.TreeItemHeader has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 4, ternaries 3. Of this number, 12 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
markdown.flattenWrappedLines (cognitive 16) utils/markdown.js:77— markdown.flattenWrappedLines has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
api_parser.parseVariable (cognitive 16) utils/doclint/api_parser.js:286— api_parser.parseVariable has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 2 (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.
linkUtils.renderJSSignature (cognitive 16) utils/doclint/linkUtils.js:119— linkUtils.renderJSSignature has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypesGenerator.generateTypes (cognitive 16) utils/generate_types/index.js:80— TypesGenerator.generateTypes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 95, 114, 87, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Workspace.ensureConsistent (cognitive 16) utils/workspace.js:95— Workspace.ensureConsistent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 7). Of this number, 15 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.
constructor (cognitive 16) browser_patches/firefox/juggler/content/FrameTree.js:402— constructor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 2 (3 pts), boolean chains 2, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 7 function items inside it that branch (webSocketClosed, frameReceived, frameSent, …). 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.
(computed) (cognitive 16) REDACTED:315— (computed) has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), boolean chains 4, ternaries 2 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Off the main sequence: playwright-core — playwright-core: abstractness 0.08, instability 0.00, distance 0.92 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Coverage not measured — .NET and JavaScript/TypeScript suite — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — examples/github-api/ (@playwright/test), examples/mock-battery/ (@playwright/test), examples/mock-filesystem/ (@playwright/test) — a gap in the analyzer, not something this repository is missing. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: 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.
Duplication concentrated across 9 sibling directories (75 clone groups) packages/playwright-core/src/server/firefox/ffBrowser.ts:136— 75 duplicated blocks under packages/playwright-core/src/server/ have copies in at least two of the sibling directories android, bidi, chromium, dispatchers, electron, firefox (+3 more sibling(s) not listed) — 60 of them are reported below, and 15 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 75 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 75 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 75 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 13 sibling directories (31 clone groups) REDACTED:253— 31 duplicated blocks under packages/ have copies in at least two of the sibling directories dashboard, extension, html-reporter, injected, isomorphic, playwright-browser-chromium (+7 more sibling(s) not listed) — 22 of them are reported below, and 9 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 31 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 31 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 31 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (16 clone groups) packages/playwright-core/src/client/network.ts:248— 16 duplicated blocks under packages/playwright-core/src/ have copies in at least two of the sibling directories cli, client, remote, server, tools — 8 of them are reported below, and 8 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (6 clone groups) browser_patches/firefox/juggler/NetworkObserver.js:858— 6 duplicated blocks under the repository root have copies in at least two of the sibling directories browser_patches, packages, utils — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplicated block (204 lines × 2 locations) packages/isomorphic/trace/versions/traceV7.ts:30— packages/isomorphic/trace/versions/traceV7.ts:30 · packages/isomorphic/trace/versions/traceV8.ts:171 — 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 (172 lines × 2 locations) packages/isomorphic/trace/versions/traceV10.ts:21— packages/isomorphic/trace/versions/traceV10.ts:21 · packages/isomorphic/trace/versions/traceV9.ts:163 — 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.
Wholesale file copy (149 identical lines × 2 files) packages/isomorphic/trace/versions/traceV6.ts:17— packages/isomorphic/trace/versions/traceV6.ts:17 · packages/isomorphic/trace/versions/traceV7.ts:17 — these 2 files are line-for-line copies of one another — 149 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (147 identical lines × 2 files) packages/isomorphic/trace/versions/traceV5.ts:18— packages/isomorphic/trace/versions/traceV5.ts:18 · packages/isomorphic/trace/versions/traceV6.ts:17 — these 2 files are line-for-line copies of one another — 147 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (139 identical lines × 2 files) packages/isomorphic/trace/versions/traceV5.ts:18— packages/isomorphic/trace/versions/traceV5.ts:18 · packages/isomorphic/trace/versions/traceV7.ts:17 — these 2 files are line-for-line copies of one another — 139 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (134 matched lines × 2 locations) · ×1
Duplicated block with local edits (134 matched lines × 2 locations) packages/playwright-core/src/server/firefox/ffBrowser.ts:136— packages/playwright-core/src/server/firefox/ffBrowser.ts:136 · packages/playwright-core/src/server/webkit/wkBrowser.ts:128 — the two spans are one implementation copied and then locally edited — 994 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (130 identical lines × 2 files) packages/isomorphic/trace/versions/traceV4.ts:17— packages/isomorphic/trace/versions/traceV4.ts:17 · packages/isomorphic/trace/versions/traceV5.ts:18 — these 2 files are line-for-line copies of one another — 130 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (129 identical lines × 2 files) packages/isomorphic/trace/versions/traceV4.ts:17— packages/isomorphic/trace/versions/traceV4.ts:17 · packages/isomorphic/trace/versions/traceV6.ts:17 — these 2 files are line-for-line copies of one another — 129 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (115 lines × 2 locations) packages/playwright-core/src/server/webkit/webview/wvPage.ts:1068— packages/playwright-core/src/server/webkit/webview/wvPage.ts:1068 · packages/playwright-core/src/server/webkit/wkPage.ts:1096 — 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 (112 lines × 2 locations) packages/isomorphic/trace/versions/traceV8.ts:35— packages/isomorphic/trace/versions/traceV8.ts:35 · packages/isomorphic/trace/versions/traceV9.ts:38 — 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.
Wholesale file copy (105 identical lines × 2 files) packages/playwright-core/src/server/webkit/webview/wvInterceptableRequest.ts:18— packages/playwright-core/src/server/webkit/webview/wvInterceptableRequest.ts:18 · packages/playwright-core/src/server/webkit/wkInterceptableRequest.ts:18 — these 2 files are line-for-line copies of one another — 105 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (87 identical lines × 2 files) packages/playwright-core/src/server/webkit/webview/wvConnection.ts:17— packages/playwright-core/src/server/webkit/webview/wvConnection.ts:17 · packages/playwright-core/src/server/webkit/wkConnection.ts:18 — these 2 files are line-for-line copies of one another — 87 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (86 identical lines × 2 files) packages/playwright-core/src/server/webkit/webview/wvExecutionContext.ts:18— packages/playwright-core/src/server/webkit/webview/wvExecutionContext.ts:18 · packages/playwright-core/src/server/webkit/wkExecutionContext.ts:18 — these 2 files are line-for-line copies of one another — 86 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (81 lines × 2 locations) packages/playwright-core/src/tools/backend/webstorage.ts:26— packages/playwright-core/src/tools/backend/webstorage.ts:26 · packages/playwright-core/src/tools/backend/webstorage.ts:130 — 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 (69 lines × 3 locations) packages/isomorphic/trace/versions/traceV6.ts:162— packages/isomorphic/trace/versions/traceV6.ts:162 · packages/isomorphic/trace/versions/traceV7.ts:183 · packages/isomorphic/trace/versions/traceV8.ts:324 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (64 lines × 3 locations) packages/isomorphic/trace/versions/traceV4.ts:19— packages/isomorphic/trace/versions/traceV4.ts:19 · packages/isomorphic/trace/versions/traceV5.ts:20 · packages/isomorphic/trace/versions/traceV6.ts:19 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Wholesale file copy (61 identical lines × 2 files) packages/playwright-core/src/server/webkit/webview/wvWorkers.ts:17— packages/playwright-core/src/server/webkit/webview/wvWorkers.ts:17 · packages/playwright-core/src/server/webkit/wkWorkers.ts:17 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (58 matched lines × 2 locations) · ×1
Duplicated block with local edits (58 matched lines × 2 locations) packages/isomorphic/locatorGenerators.ts:566— packages/isomorphic/locatorGenerators.ts:566 · packages/isomorphic/locatorGenerators.ts:672 — the two spans are one implementation copied and then locally edited — 466 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (54 matched lines × 2 locations) · ×1
Duplicated block with local edits (54 matched lines × 2 locations) REDACTED:253— REDACTED:253 · REDACTED:118 — the two spans are one implementation copied and then locally edited — 466 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 (53 lines × 2 locations) packages/playwright-core/src/server/webkit/webview/wvPage.ts:553— packages/playwright-core/src/server/webkit/webview/wvPage.ts:553 · packages/playwright-core/src/server/webkit/wkPage.ts:542 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (51 matched lines × 2 locations) · ×1
Duplicated block with local edits (51 matched lines × 2 locations) packages/playwright-core/src/server/chromium/crBrowser.ts:391— packages/playwright-core/src/server/chromium/crBrowser.ts:391 · packages/playwright-core/src/server/webkit/wkBrowser.ts:240 — the two spans are one implementation copied and then locally edited — 427 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 (44 lines × 2 locations) packages/playwright-core/src/server/bidi/bidiChromium.ts:105— packages/playwright-core/src/server/bidi/bidiChromium.ts:105 · REDACTED:328 — 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 (43 lines × 4 locations) packages/isomorphic/trace/versions/traceV5.ts:165— packages/isomorphic/trace/versions/traceV5.ts:165 · packages/isomorphic/trace/versions/traceV6.ts:171 · packages/isomorphic/trace/versions/traceV7.ts:192 · packages/isomorphic/trace/versions/traceV8.ts:333 — the 4 copies are spread across 4 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 (41 matched lines × 2 locations) · ×1
Duplicated block with local edits (41 matched lines × 2 locations) browser_patches/firefox/juggler/protocol/Protocol.js:19— browser_patches/firefox/juggler/protocol/Protocol.js:19 · browser_patches/firefox/juggler/protocol/Protocol.js:88 — the two spans are one implementation copied and then locally edited — 272 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (39 lines × 2 locations) packages/playwright-core/src/server/webkit/webview/wvPage.ts:1220— packages/playwright-core/src/server/webkit/webview/wvPage.ts:1220 · packages/playwright-core/src/server/webkit/wkPage.ts:1304 — 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 (34 lines × 3 locations) packages/isomorphic/locatorGenerators.ts:352— packages/isomorphic/locatorGenerators.ts:352 · packages/isomorphic/locatorGenerators.ts:459 · packages/isomorphic/locatorGenerators.ts:677 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (32 lines × 2 locations) packages/playwright-core/src/server/firefox/ffPage.ts:504— packages/playwright-core/src/server/firefox/ffPage.ts:504 · packages/playwright-core/src/server/webkit/wkPage.ts:914 — 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 (31 lines × 4 locations) packages/isomorphic/locatorGenerators.ts:319— packages/isomorphic/locatorGenerators.ts:319 · packages/isomorphic/locatorGenerators.ts:422 · packages/isomorphic/locatorGenerators.ts:538 · packages/isomorphic/locatorGenerators.ts:644 — all 4 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.
Complex function getTextAlternativeInternal (cyclomatic 138, cognitive 240) packages/injected/src/roleUtils.ts:703— getTextAlternativeInternal has cyclomatic complexity 138 and cognitive complexity 240; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 92, cognitive 118) packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:384— (anonymous) has cyclomatic complexity 92 and cognitive complexity 118; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 generateChannels (cyclomatic 81, cognitive 239) utils/generate_channels.js:239— generateChannels has cyclomatic complexity 81 and cognitive complexity 239; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 validateConfig (cyclomatic 79, cognitive 96) packages/playwright/src/common/configLoader.ts:127— validateConfig has cyclomatic complexity 79 and cognitive complexity 96; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function program (cyclomatic 64, cognitive 78) · ×1
Complex function program (cyclomatic 64, cognitive 78) packages/playwright-core/src/tools/cli-client/program.ts:95— program has cyclomatic complexity 64 and cognitive complexity 78; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 expectSingleElement (cyclomatic 58, cognitive 81) REDACTED:1536— expectSingleElement has cyclomatic complexity 58 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 ansi2html (cyclomatic 56, cognitive 21) packages/web/src/ansi2html.ts:17— ansi2html has cyclomatic complexity 56 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 validateProject (cyclomatic 53, cognitive 76) packages/playwright/src/common/configLoader.ts:257— validateProject has cyclomatic complexity 53 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function consumeAToken (cyclomatic 49, cognitive 75) packages/isomorphic/cssTokenizer.ts:143— consumeAToken has cyclomatic complexity 49 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 innerAsLocators (cyclomatic 46, cognitive 113) packages/isomorphic/locatorGenerators.ts:86— innerAsLocators has cyclomatic complexity 46 and cognitive complexity 113; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 visit (cyclomatic 44, cognitive 72) REDACTED:95— visit has cyclomatic complexity 44 and cognitive complexity 72; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function innerRenderMdNode (cyclomatic 44, cognitive 42) utils/markdown.js:306— innerRenderMdNode has cyclomatic complexity 44 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 innerSerialize (cyclomatic 43, cognitive 67) REDACTED:253— innerSerialize has cyclomatic complexity 43 and cognitive complexity 67; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 translateType (cyclomatic 42, cognitive 68) utils/doclint/generateDotnetApi.js:735— translateType has cyclomatic complexity 42 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 Dashboard (cyclomatic 40, cognitive 37) REDACTED:67— Dashboard has cyclomatic complexity 40 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 generateLocator (cyclomatic 40, cognitive 25) packages/isomorphic/locatorGenerators.ts:526— generateLocator has cyclomatic complexity 40 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 _innerFetch (cyclomatic 39, cognitive 61) packages/playwright-core/src/client/fetch.ts:197— _innerFetch has cyclomatic complexity 39 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateLocator (cyclomatic 39, cognitive 31) packages/isomorphic/locatorGenerators.ts:416— generateLocator has cyclomatic complexity 39 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 _build (cyclomatic 38, cognitive 57) packages/playwright-core/src/tools/backend/response.ts:269— _build has cyclomatic complexity 38 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _onRequest (cyclomatic 37, cognitive 41) packages/playwright-core/src/server/chromium/crNetworkManager.ts:295— _onRequest has cyclomatic complexity 37 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderPreview (cyclomatic 37, cognitive 20) REDACTED:203— renderPreview has cyclomatic complexity 37 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 matchesNode (cyclomatic 36, cognitive 35) REDACTED:381— matchesNode 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 minimist (cyclomatic 34, cognitive 70) packages/playwright-core/src/tools/cli-client/minimist.ts:36— minimist has cyclomatic complexity 34 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _initialize (cyclomatic 34, cognitive 49) REDACTED:472— _initialize has cyclomatic complexity 34 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _innerAppendEvent (cyclomatic 34, cognitive 22) packages/isomorphic/trace/traceModernizer.ts:107— _innerAppendEvent has cyclomatic complexity 34 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 buildTextCandidates (cyclomatic 33, cognitive 61) packages/injected/src/selectorGenerator.ts:280— buildTextCandidates has cyclomatic complexity 33 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function run (cyclomatic 33, cognitive 60) · ×1
Complex function run (cyclomatic 33, cognitive 60) utils/doclint/cli.js:50— run has cyclomatic complexity 33 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 calculatePlatform (cyclomatic 33, cognitive 59) packages/utils/hostPlatform.ts:41— calculatePlatform has cyclomatic complexity 33 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 runWatchModeLoop (cyclomatic 32, cognitive 71) packages/playwright/src/runner/watchMode.ts:79— runWatchModeLoop has cyclomatic complexity 32 and cognitive complexity 71; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 toMatchAriaSnapshot (cyclomatic 31, cognitive 47) packages/playwright/src/matchers/toMatchAriaSnapshot.ts:41— toMatchAriaSnapshot has cyclomatic complexity 31 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function visit (cyclomatic 31, cognitive 42) REDACTED:95— visit has cyclomatic complexity 31 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 31, cognitive 31) REDACTED:472— (anonymous) has cyclomatic complexity 31 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseEvaluationResultValue (cyclomatic 30, cognitive 67) REDACTED:151— parseEvaluationResultValue has cyclomatic complexity 30 and cognitive complexity 67; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 traceConsole (cyclomatic 30, cognitive 48) REDACTED:21— traceConsole has cyclomatic complexity 30 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function elementState (cyclomatic 30, cognitive 43) REDACTED:788— elementState has cyclomatic complexity 30 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function convertMap (cyclomatic 30, cognitive 42) packages/isomorphic/ariaSnapshot.ts:175— convertMap has cyclomatic complexity 30 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function match (cyclomatic 30, cognitive 34) · ×1
Complex function match (cyclomatic 30, cognitive 34) packages/injected/src/roleSelectorEngine.ts:145— match has cyclomatic complexity 30 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 ImageDiffView (cyclomatic 30, cognitive 20) packages/web/src/shared/imageDiffView.tsx:66— ImageDiffView has cyclomatic complexity 30 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.
REDACTED: 1760 lines of code REDACTED:1— REDACTED has 1760 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/frames.ts · ×1
packages/playwright-core/src/server/frames.ts: 1729 lines of code packages/playwright-core/src/server/frames.ts:1— packages/playwright-core/src/server/frames.ts has 1729 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/injected/src/recorder/recorder.ts · ×1
packages/injected/src/recorder/recorder.ts: 1609 lines of code packages/injected/src/recorder/recorder.ts:1— packages/injected/src/recorder/recorder.ts has 1609 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1502 lines of code REDACTED:1— REDACTED has 1502 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· browser_patches/firefox/juggler/TargetRegistry.js · ×1
browser_patches/firefox/juggler/TargetRegistry.js: 1437 lines of code browser_patches/firefox/juggler/TargetRegistry.js:1— browser_patches/firefox/juggler/TargetRegistry.js has 1437 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/tools/cli-daemon/commands.ts · ×1
packages/playwright-core/src/tools/cli-daemon/commands.ts: 1324 lines of code packages/playwright-core/src/tools/cli-daemon/commands.ts:1— packages/playwright-core/src/tools/cli-daemon/commands.ts has 1324 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/registry/index.ts · ×1
packages/playwright-core/src/server/registry/index.ts: 1307 lines of code packages/playwright-core/src/server/registry/index.ts:1— packages/playwright-core/src/server/registry/index.ts has 1307 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/injected/src/roleUtils.ts · ×1
packages/injected/src/roleUtils.ts: 1262 lines of code packages/injected/src/roleUtils.ts:1— packages/injected/src/roleUtils.ts has 1262 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/webkit/wkPage.ts · ×1
packages/playwright-core/src/server/webkit/wkPage.ts: 1241 lines of code packages/playwright-core/src/server/webkit/wkPage.ts:1— packages/playwright-core/src/server/webkit/wkPage.ts has 1241 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/webkit/webview/wvPage.ts · ×1
packages/playwright-core/src/server/webkit/webview/wvPage.ts: 1197 lines of code packages/playwright-core/src/server/webkit/webview/wvPage.ts:1— packages/playwright-core/src/server/webkit/webview/wvPage.ts has 1197 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1188 lines of code REDACTED:1— REDACTED has 1188 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· browser_patches/firefox/juggler/NetworkObserver.js · ×1
browser_patches/firefox/juggler/NetworkObserver.js: 1051 lines of code browser_patches/firefox/juggler/NetworkObserver.js:1— browser_patches/firefox/juggler/NetworkObserver.js has 1051 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/page.ts · ×1
packages/playwright-core/src/server/page.ts: 1039 lines of code packages/playwright-core/src/server/page.ts:1— packages/playwright-core/src/server/page.ts has 1039 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/dom.ts · ×1
packages/playwright-core/src/server/dom.ts: 960 lines of code packages/playwright-core/src/server/dom.ts:1— packages/playwright-core/src/server/dom.ts has 960 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· utils/doclint/documentation.js · ×1
utils/doclint/documentation.js: 915 lines of code utils/doclint/documentation.js:1— utils/doclint/documentation.js has 915 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/isomorphic/cssTokenizer.ts · ×1
packages/isomorphic/cssTokenizer.ts: 875 lines of code packages/isomorphic/cssTokenizer.ts:1— packages/isomorphic/cssTokenizer.ts has 875 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/chromium/crNetworkManager.ts · ×1
packages/playwright-core/src/server/chromium/crNetworkManager.ts: 870 lines of code packages/playwright-core/src/server/chromium/crNetworkManager.ts:1— packages/playwright-core/src/server/chromium/crNetworkManager.ts has 870 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/client/page.ts · ×1
packages/playwright-core/src/client/page.ts: 859 lines of code packages/playwright-core/src/client/page.ts:1— packages/playwright-core/src/client/page.ts has 859 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright/src/index.ts · ×1
packages/playwright/src/index.ts: 856 lines of code packages/playwright/src/index.ts:1— packages/playwright/src/index.ts has 856 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/trace/recorder/tracing.ts · ×1
packages/playwright-core/src/server/trace/recorder/tracing.ts: 845 lines of code packages/playwright-core/src/server/trace/recorder/tracing.ts:1— packages/playwright-core/src/server/trace/recorder/tracing.ts has 845 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/network.ts · ×1
packages/playwright-core/src/server/network.ts: 839 lines of code packages/playwright-core/src/server/network.ts:1— packages/playwright-core/src/server/network.ts has 839 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/client/network.ts · ×1
packages/playwright-core/src/client/network.ts: 835 lines of code packages/playwright-core/src/client/network.ts:1— packages/playwright-core/src/client/network.ts has 835 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/fetch.ts · ×1
packages/playwright-core/src/server/fetch.ts: 824 lines of code packages/playwright-core/src/server/fetch.ts:1— packages/playwright-core/src/server/fetch.ts has 824 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· utils/doclint/generateDotnetApi.js · ×1
utils/doclint/generateDotnetApi.js: 809 lines of code utils/doclint/generateDotnetApi.js:1— utils/doclint/generateDotnetApi.js has 809 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/injected/src/clock.ts · ×1
packages/injected/src/clock.ts: 803 lines of code packages/injected/src/clock.ts:1— packages/injected/src/clock.ts has 803 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright/src/isomorphic/teleReceiver.ts · ×1
packages/playwright/src/isomorphic/teleReceiver.ts: 789 lines of code packages/playwright/src/isomorphic/teleReceiver.ts:1— packages/playwright/src/isomorphic/teleReceiver.ts has 789 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright/src/reporters/html.ts · ×1
packages/playwright/src/reporters/html.ts: 773 lines of code packages/playwright/src/reporters/html.ts:1— packages/playwright/src/reporters/html.ts has 773 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 757 lines of code REDACTED:1— REDACTED has 757 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/isomorphic/locatorGenerators.ts · ×1
packages/isomorphic/locatorGenerators.ts: 735 lines of code packages/isomorphic/locatorGenerators.ts:1— packages/isomorphic/locatorGenerators.ts has 735 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/har/harTracer.ts · ×1
packages/playwright-core/src/server/har/harTracer.ts: 734 lines of code packages/playwright-core/src/server/har/harTracer.ts:1— packages/playwright-core/src/server/har/harTracer.ts has 734 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/bidi/bidiPage.ts · ×1
packages/playwright-core/src/server/bidi/bidiPage.ts: 699 lines of code packages/playwright-core/src/server/bidi/bidiPage.ts:1— packages/playwright-core/src/server/bidi/bidiPage.ts has 699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/isomorphic/locatorParser.ts · ×1
packages/isomorphic/locatorParser.ts: 694 lines of code packages/isomorphic/locatorParser.ts:1— packages/isomorphic/locatorParser.ts has 694 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/tools/dashboard/dashboardController.ts · ×1
packages/playwright-core/src/tools/dashboard/dashboardController.ts: 673 lines of code packages/playwright-core/src/tools/dashboard/dashboardController.ts:1— packages/playwright-core/src/tools/dashboard/dashboardController.ts has 673 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 669 lines of code REDACTED:1— REDACTED has 669 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright/src/worker/testInfo.ts · ×1
packages/playwright/src/worker/testInfo.ts: 658 lines of code packages/playwright/src/worker/testInfo.ts:1— packages/playwright/src/worker/testInfo.ts has 658 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright/src/reporters/base.ts · ×1
packages/playwright/src/reporters/base.ts: 651 lines of code packages/playwright/src/reporters/base.ts:1— packages/playwright/src/reporters/base.ts has 651 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright/src/runner/dispatcher.ts · ×1
packages/playwright/src/runner/dispatcher.ts: 638 lines of code packages/playwright/src/runner/dispatcher.ts:1— packages/playwright/src/runner/dispatcher.ts has 638 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 626 lines of code REDACTED:1— REDACTED has 626 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright/src/reporters/merge.ts · ×1
packages/playwright/src/reporters/merge.ts: 622 lines of code packages/playwright/src/reporters/merge.ts:1— packages/playwright/src/reporters/merge.ts has 622 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts · ×1
packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts: 620 lines of code packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:1— packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts has 620 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 (~1633 LoC) browser_patches/firefox/juggler/TargetRegistry.js— no import path from any entry point (565 application, 85 tooling, 823 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 (~1170 LoC) browser_patches/firefox/juggler/NetworkObserver.js— no import path from any entry point (565 application, 85 tooling, 823 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 (~916 LoC) utils/doclint/generateDotnetApi.js— no import path from any entry point (565 application, 85 tooling, 823 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 (~656 LoC) utils/generate_types/index.js— no import path from any entry point (565 application, 85 tooling, 823 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 (~253 LoC) browser_patches/firefox/juggler/SimpleChannel.js— no import path from any entry point (565 application, 85 tooling, 823 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 (~234 LoC) browser_patches/firefox/juggler/Helper.js— no import path from any entry point (565 application, 85 tooling, 823 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 (~171 LoC) utils/doclint/dotnetXmlDocumentation.js— no import path from any entry point (565 application, 85 tooling, 823 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (utils/doclint/generateDotnetApi.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~170 LoC) packages/html-reporter/src/sampleReport.ts— no import path from any entry point (565 application, 85 tooling, 823 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/html-reporter/src/testCaseView.story.tsx, packages/html-reporter/src/testFileView.story.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~161 LoC) browser_patches/firefox/juggler/components/Juggler.js— no import path from any entry point (565 application, 85 tooling, 823 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 (~158 LoC) utils/doclint/linkUtils.js— no import path from any entry point (565 application, 85 tooling, 823 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (utils/generate_types/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~139 LoC) utils/generate_types/parseOverrides.js— no import path from any entry point (565 application, 85 tooling, 823 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (utils/generate_types/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~135 LoC) utils/doclint/generateApiJson.js— no import path from any entry point (565 application, 85 tooling, 823 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 (~119 LoC) browser_patches/firefox/juggler/content/main.js— no import path from any entry point (565 application, 85 tooling, 823 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 (~116 LoC) utils/generate_chromium_default_font_families.js— no import path from any entry point (565 application, 85 tooling, 823 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 (~99 LoC) browser_patches/firefox/juggler/ChannelEventSink.sys.mjs— no import path from any entry point (565 application, 85 tooling, 823 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 (~48 LoC) packages/trace-viewer/src/ui/clickPointer.tsx— no import path from any entry point (565 application, 85 tooling, 823 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 (~38 LoC) packages/html-reporter/src/chip.story.tsx— no import path from any entry point (565 application, 85 tooling, 823 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 (~37 LoC) packages/dashboard/src/screencast.tsx— no import path from any entry point (565 application, 85 tooling, 823 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 (~35 LoC) packages/html-reporter/src/headerView.story.tsx— no import path from any entry point (565 application, 85 tooling, 823 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 (~33 LoC) packages/html-reporter/src/testCaseView.story.tsx— no import path from any entry point (565 application, 85 tooling, 823 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 (~29 LoC) packages/playwright-client/src/nodeStubs/path.ts— no import path from any entry point (565 application, 85 tooling, 823 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 (~27 LoC) packages/playwright-client/src/nodeStubs/async_hooks.ts— no import path from any entry point (565 application, 85 tooling, 823 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 (~25 LoC) packages/playwright-client/src/nodeStubs/fs.ts— no import path from any entry point (565 application, 85 tooling, 823 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 (~22 LoC) packages/playwright-client/src/nodeStubs/processShim.ts— no import path from any entry point (565 application, 85 tooling, 823 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 (~3 LoC) browser_patches/firefox/preferences/00-playwright-prefs.js— no import path from any entry point (565 application, 85 tooling, 823 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 'source-map' packages/playwright/src/runner/loadUtils.ts:30— Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED.
Unused dependency '@actions/github' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'istanbul-lib-instrument' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'yaml' — Declared in packages/web/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Duplicated predicate packages/playwright-core/src/browserServerImpl.ts:55— `!!options.ignoreDefaultArgs && !Array.isArray(options.ignoreDefaultArgs)` appears character-identically in 2 files — packages/playwright-core/src/browserServerImpl.ts, packages/playwright-core/src/client/browserType.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 browser_patches/firefox/juggler/NetworkObserver.js:317— `!c.origin || c.origin.toLowerCase() === origin` appears character-identically in 2 files — browser_patches/firefox/juggler/NetworkObserver.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/chromium/crExecutionContext.ts:113— `!js.isJavaScriptErrorInEvaluate(error) && !isSessionClosedError(error)` appears character-identically in 4 files — packages/playwright-core/src/server/chromium/crExecutionContext.ts, packages/playwright-core/src/server/firefox/ffExecutionContext.ts, packages/playwright-core/src/server/webkit/webview/wvExecutionContext.ts, packages/playwright-core/src/server/webkit/wkExecutionContext.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/bidi/bidiChromium.ts:61— `!logs.includes('crbug.com/357670') && !logs.includes('No usable sandbox!') && !logs.includes('crbug.com/638180')` appears character-identically in 2 files — packages/playwright-core/src/server/bidi/bidiChromium.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/webkit/webview/wvPage.ts:776— `!omitDeviceScaleFactor && this._page.browserContext._options.deviceScaleFactor` appears character-identically in 2 files — packages/playwright-core/src/server/webkit/webview/wvPage.ts, packages/playwright-core/src/server/webkit/wkPage.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/dom.ts:344— `!options.skipActionPreChecks && !options.force` appears character-identically in 2 files — packages/playwright-core/src/server/dom.ts, packages/playwright-core/src/server/frames.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:1245— `!result || result.object.subtype === 'null'` appears character-identically in 2 files — REDACTED, packages/playwright-core/src/server/webkit/wkPage.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/client/frame.ts:243— `(options as any).waitFor && (options as any).waitFor !== 'visible'` appears character-identically in 2 files — packages/playwright-core/src/client/frame.ts, packages/playwright-core/src/server/frames.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/webkit/webview/wvInterceptableRequest.ts:129— `300 <= response.status && response.status < 400` appears character-identically in 2 files — packages/playwright-core/src/server/webkit/webview/wvInterceptableRequest.ts, packages/playwright-core/src/server/webkit/wkInterceptableRequest.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 browser_patches/firefox/juggler/TargetRegistry.js:449— `Ci.nsIDOMWindowInternal || Ci.nsIDOMWindow` appears character-identically in 2 files — browser_patches/firefox/juggler/TargetRegistry.js, browser_patches/firefox/juggler/protocol/BrowserHandler.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/trace/viewer/traceViewer.ts:131— `__PW_HMR__ && process.env.PW_HMR_STATIC !== '1'` appears character-identically in 2 files — packages/playwright-core/src/server/trace/viewer/traceViewer.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/isomorphic/codegen/csharp.ts:88— `action.url && action.url !== 'about:blank' && action.url !== 'chrome://newtab/'` appears character-identically in 4 files — packages/isomorphic/codegen/csharp.ts, packages/isomorphic/codegen/java.ts, packages/isomorphic/codegen/javascript.ts, packages/isomorphic/codegen/python.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/client/connection.ts:304— `arg && typeof arg === 'object' && typeof arg.guid === 'string'` appears character-identically in 2 files — packages/playwright-core/src/client/connection.ts, packages/playwright-core/src/server/dispatchers/dispatcher.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/bidi/bidiFirefox.ts:109— `arg.startsWith('-profile') || arg.startsWith('--profile')` appears character-identically in 2 files — packages/playwright-core/src/server/bidi/bidiFirefox.ts, packages/playwright-core/src/server/firefox/firefox.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/client/errors.ts:36— `cause || 'Target page, context or browser has been closed'` appears character-identically in 2 files — packages/playwright-core/src/client/errors.ts, packages/playwright-core/src/server/errors.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/injected/src/domUtils.ts:179— `child.nodeType === 3 && isVisibleTextNode(child as Text)` appears character-identically in 2 files — packages/injected/src/domUtils.ts, packages/injected/src/roleUtils.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 utils/doclint/api_parser.js:430— `child.type !== 'li' || child.liType !== 'bullet' || !child.text.startsWith('langs:')` appears character-identically in 2 files — utils/doclint/api_parser.js, utils/markdown.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/bidi/bidiPdf.ts:95— `convertPrintParameterToInches(margin.bottom) || 0` appears character-identically in 2 files — packages/playwright-core/src/server/bidi/bidiPdf.ts, packages/playwright-core/src/server/chromium/crPdf.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/bidi/bidiPdf.ts:96— `convertPrintParameterToInches(margin.left) || 0` appears character-identically in 2 files — packages/playwright-core/src/server/bidi/bidiPdf.ts, packages/playwright-core/src/server/chromium/crPdf.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/bidi/bidiPdf.ts:97— `convertPrintParameterToInches(margin.right) || 0` appears character-identically in 2 files — packages/playwright-core/src/server/bidi/bidiPdf.ts, packages/playwright-core/src/server/chromium/crPdf.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/bidi/bidiPdf.ts:98— `convertPrintParameterToInches(margin.top) || 0` appears character-identically in 2 files — packages/playwright-core/src/server/bidi/bidiPdf.ts, packages/playwright-core/src/server/chromium/crPdf.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/bidi/bidiPdf.ts:88— `convertPrintParameterToInches(options.height) || paperHeight` appears character-identically in 2 files — packages/playwright-core/src/server/bidi/bidiPdf.ts, packages/playwright-core/src/server/chromium/crPdf.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/bidi/bidiPdf.ts:87— `convertPrintParameterToInches(options.width) || paperWidth` appears character-identically in 2 files — packages/playwright-core/src/server/bidi/bidiPdf.ts, packages/playwright-core/src/server/chromium/crPdf.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/isomorphic/codegen/csharp.ts:303— `deviceName && deviceDescriptors[deviceName]` appears character-identically in 3 files — packages/isomorphic/codegen/csharp.ts, packages/isomorphic/codegen/javascript.ts, packages/isomorphic/codegen/python.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/playwright-core/src/server/bidi/bidiPage.ts:603— `e instanceof Error && e.message.includes('Node does not have a layout object')` appears character-identically in 4 files — packages/playwright-core/src/server/bidi/bidiPage.ts, REDACTED, packages/playwright-core/src/server/firefox/ffPage.ts, packages/playwright-core/src/server/webkit/wkPage.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.
+ 15 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel utils/check_audit.js:40— `utils/check_audit.js` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/check_audit.js:47— `utils/check_audit.js` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/check_audit.js:52— `utils/check_audit.js` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/generate_chromium_default_font_families.js:116— `utils/generate_chromium_default_font_families.js` reports through `console.*` at line 116 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/video_stress.js:5— `utils/video_stress.js` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/video_stress.js:12— `utils/video_stress.js` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/video_stress.js:14— `utils/video_stress.js` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/protocol-types-generator/update-webview-protocol.js:56— `utils/protocol-types-generator/update-webview-protocol.js` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/protocol-types-generator/update-webview-protocol.js:62— `utils/protocol-types-generator/update-webview-protocol.js` reports through `console.*` at line 62 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/protocol-types-generator/update-webview-protocol.js:68— `utils/protocol-types-generator/update-webview-protocol.js` reports through `console.*` at line 68 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/protocol-types-generator/update-webview-protocol.js:72— `utils/protocol-types-generator/update-webview-protocol.js` reports through `console.*` at line 72 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/protocol-types-generator/update-webview-protocol.js:74— `utils/protocol-types-generator/update-webview-protocol.js` reports through `console.*` at line 74 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/doclint/api_parser.js:461— `utils/doclint/api_parser.js` reports through `console.*` at line 461 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/doclint/api_parser.js:462— `utils/doclint/api_parser.js` reports through `console.*` at line 462 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel utils/doclint/generateApiJson.js:36— `utils/doclint/generateApiJson.js` reports through `console.*` at line 36 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/isomorphic/cssTokenizer.ts:117— `packages/isomorphic/cssTokenizer.ts` reports through `console.*` at line 117 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/isomorphic/cssTokenizer.ts:140— `packages/isomorphic/cssTokenizer.ts` reports through `console.*` at line 140 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/isomorphic/codegen/javascript.ts:74— `packages/isomorphic/codegen/javascript.ts` reports through `console.*` at line 74 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/injected/src/clock.ts:252— `packages/injected/src/clock.ts` reports through `console.*` at line 252 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/injected/src/recorder/pollingRecorder.ts:48— `packages/injected/src/recorder/pollingRecorder.ts` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel browser_patches/firefox/juggler/ChannelEventSink.sys.mjs:47— `browser_patches/firefox/juggler/ChannelEventSink.sys.mjs` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel browser_patches/firefox/juggler/NetworkObserver.js:1047— `browser_patches/firefox/juggler/NetworkObserver.js` reports through `console.*` at line 1047 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel browser_patches/firefox/juggler/NetworkObserver.js:1060— `browser_patches/firefox/juggler/NetworkObserver.js` reports through `console.*` at line 1060 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel browser_patches/firefox/juggler/NetworkObserver.js:1069— `browser_patches/firefox/juggler/NetworkObserver.js` reports through `console.*` at line 1069 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel REDACTED:429— `REDACTED` reports through `console.*` at line 429 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
redundant comment browser_patches/firefox/juggler/NetworkObserver.js:663— "http channel ids that were fulfilled by service worker" repeats the code it sits on: 5 of its 6 words (channel, ids, fulfilled, service, worker) are already in `this._channelIdsFulfilledByServiceWorker = new Set();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:1738— ""To match an array" is "to contain an array" + "equal length"" repeats the code it sits on: 4 of its 5 words (match, array, contain, length) are already in `const lengthShouldMatch = expression !== 'to.contain.text.array';`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/isomorphic/locatorParser.ts:311— "Parses `(source[, [flagsKeyword=]<flagsEnum>.<flag> ( "|" <flagsEnum>.<flag> )*])`." repeats the code it sits on: 5 of its 6 words (parses, flags, keyword, enum, flag) are already in `protected parseRegexArguments(flagsEnum: string, flagsByName: Map<string, string>, flagsKeyword?: string): RegExp`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/isomorphic/trace/versions/traceV10.ts:225— "Node name, and optional attributes and child nodes." repeats the code it sits on: 5 of its 6 words (node, name, attributes, child, nodes) are already in `export type NodeNameAttributesChildNodesSnapshot = [ string ] | [ string, Record<string, string>, ...NodeSnapshot[] ];`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/isomorphic/trace/versions/traceV7.ts:77— "Node name, and optional attributes and child nodes." repeats the code it sits on: 5 of its 6 words (node, name, attributes, child, nodes) are already in `type NodeNameAttributesChildNodesSnapshot = [ string ] | [ string, Record<string, string>, ...NodeSnapshot[] ];`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/isomorphic/trace/versions/traceV8.ts:218— "Node name, and optional attributes and child nodes." repeats the code it sits on: 5 of its 6 words (node, name, attributes, child, nodes) are already in `type NodeNameAttributesChildNodesSnapshot = [ string ] | [ string, Record<string, string>, ...NodeSnapshot[] ];`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/isomorphic/trace/versions/traceV9.ts:369— "Node name, and optional attributes and child nodes." repeats the code it sits on: 5 of its 6 words (node, name, attributes, child, nodes) are already in `export type NodeNameAttributesChildNodesSnapshot = [ string ] | [ string, Record<string, string>, ...NodeSnapshot[] ];`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/playwright-core/src/server/dispatchers/jsHandleDispatcher.ts:52— "If "jsHandle" is an ElementHandle, it belongs to the same frame as "this"." repeats the code it sits on: 4 of its 5 words (js, handle, element, frame) are already in `return { handle: ElementHandleDispatcher.fromJSOrElementHandle(this.parentScope() as FrameDispatcher, jsHandle) };`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/playwright-core/src/server/dispatchers/jsHandleDispatcher.ts:58— "If "jsHandle" is an ElementHandle, it belongs to the same frame as "this"." repeats the code it sits on: 4 of its 5 words (js, handle, element, frame) are already in `return { handle: ElementHandleDispatcher.fromJSOrElementHandle(this.parentScope() as FrameDispatcher, jsHandle) };`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/playwright-core/src/server/dispatchers/jsHandleDispatcher.ts:66— "If "jsHandle" is an ElementHandle, it belongs to the same frame as "this"." repeats the code it sits on: 4 of its 5 words (js, handle, element, frame) are already in `properties.push({ name, value: ElementHandleDispatcher.fromJSOrElementHandle(this.parentScope() as FrameDispatcher, valu …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/playwright-core/src/server/dom.ts:305— "Return the middle point of the first quad." repeats the code it sits on: 4 of its 5 words (return, middle, point, quad) are already in `return { point: quadMiddlePoint(quad), box };`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:583— "Trust code and unrestricted file access." repeats the code it sits on: 4 of its 5 words (code, unrestricted, file, access) are already in `if (flags.origin === 'code' || options.config.allowUnrestrictedFileAccess || options.config.skillMode)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/playwright/src/runner/dispatcher.ts:41— "Worker slot is claimed when it has jobDispatcher assigned." repeats the code it sits on: 5 of its 6 words (worker, slot, job, dispatcher, assigned) are already in `private _workerSlots: { worker?: WorkerHost, jobDispatcher?: JobDispatcher }[] = [];`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/playwright/src/runner/loadUtils.ts:202— "Shard test groups." repeats the code it sits on: 3 of its 3 words (shard, test, groups) are already in `const testGroupsInThisShard = filterForShard(config.config.shard, testRun.options.shardWeights, testGroups);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/assets/to-do-notifications/scripts/todo.js:172— "Make a request to add our newItem object to the object store" repeats the code it sits on: 6 of its 7 words (request, add, new, item, object, store) are already in `const objectStoreRequest = objectStore.add(newItem[0]);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/extension/harness.ts:217— "Drags the tabs into the tab group that has the tab `groupTabTitle`." repeats the code it sits on: 5 of its 5 words (drags, tabs, tab, group, title) are already in `async dragIntoGroupOf(titles: string | string[], groupTabTitle: string): Promise<void>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/extension/harness.ts:340— "Changes the title and the color of the tab group that has the tab." repeats the code it sits on: 4 of its 5 words (title, color, tab, group) are already in `async editGroupOf(tabTitle: string, style: { title: string, color: string }): Promise<void>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/library/video.spec.ts:315— "Find a frame with all almost-black pixels." repeats the code it sits on: 5 of its 5 words (find, frame, almost, black, pixels) are already in `const frame = videoPlayer.findFrame(pixels => everyPixel(pixels, isAlmostBlack));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/mcp/cli-storage.spec.ts:27— "Set some cookies and localStorage" repeats the code it sits on: 4 of its 4 words (set, cookies, local, storage) are already in `await cli('eval', '() => { document.cookie = "testCookie=testValue"; localStorage.setItem("testKey", "testValue"); }');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/mcp/route.spec.ts:33— "Set up a route to mock the API response" repeats the code it sits on: 4 of its 5 words (set, route, api, response) are already in `const routeResponse = parseResponse(await client.callTool({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/page/page-network-response.spec.ts:128— "send request and wait for server response" repeats the code it sits on: 4 of its 5 words (request, wait, server, response) are already in `const [pageResponse] = await Promise.all([`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment utils/generate_types/test/test.ts:973— "Register the engine. Selectors will be prefixed with "tag="." repeats the code it sits on: 4 of its 5 words (register, engine, selectors, tag) are already in `await playwright.selectors.register('tag', createTagNameEngine);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Silent fallback default in catch browser_patches/firefox/juggler/content/Runtime.js:203— `onMessage` (in `_registerConsoleAPIListener`) swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/dashboard/src/sessionSidebar.tsx:38— `tabFavicon` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/injected/src/roleUtils.ts:400— `getIdRefs` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/isomorphic/locatorParser.ts:773— `locatorOrSelectorAsSelector` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/playwright-core/src/server/recorder.ts:476— `_readSource` swallows every exception into `return '// No source available'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/playwright-core/src/tools/utils/extension.ts:42— `listProfileDirectories` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/playwright-core/src/tools/mcp/config.ts:31— `fileExistsAsync` 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 REDACTED:402— `fileExists` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:411— `fileExistsAsync` 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 REDACTED:419— `dirExists` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/playwright/src/reporters/coverage.ts:67— `onEnd` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:293— `parseCSSStyle` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/trace-viewer/src/ui/networkResourceDetails.tsx:335— `WebSocketMessagesTab` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:384— `serveFolder` 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 tests/assets/reading-list/vue_2.6.14.js:320— `looseEqual` 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 tests/library/inspector/inspectorTest.ts:301— `text` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch tests/webview/webviewTest.ts:85— `listTabs` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch utils/test-results-db/db.ts:156— `fileSize` swallows every exception into `return 0` — 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.
Orphaned file utils/linux-browser-dependencies/inside_docker/list_dependencies.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/trace-viewer/src/ui/codegen.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 browser_patches/firefox/juggler/SimpleChannel.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/dashboard/src/annotateView.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file browser_patches/firefox/juggler/Helper.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/utils/image_tools/stats.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/utils/image_tools/compare.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 browser_patches/firefox/juggler/protocol/Dispatcher.js: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 browser_patches/firefox/juggler/protocol/PrimitiveTypes.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/dashboard/src/annotationImage.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 utils/doclint/linting-code-snippets/java/src/main/java/JavaSyntaxChecker.java: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 utils/generate_clip_paths.js: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 browser_patches/firefox/juggler/ChannelEventSink.sys.mjs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/playwright-core/src/androidServerImpl.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/utils/image_tools/imageChannel.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/dashboard/src/annotationZip.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Documentation: no build, run or usage example packages/playwright-browser-chromium/README.md:1— `playwright-browser-chromium` is a published package (`REDACTED` without `"private": true`) and neither `packages/playwright-browser-chromium/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/playwright-browser-firefox/README.md:1— `playwright-browser-firefox` is a published package (`REDACTED` without `"private": true`) and neither `packages/playwright-browser-firefox/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/playwright-browser-webkit/README.md:1— `playwright-browser-webkit` is a published package (`REDACTED` without `"private": true`) and neither `packages/playwright-browser-webkit/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/playwright-chromium/README.md:1— `playwright-chromium` is a command-line package (`bin` in `REDACTED`) and neither `packages/playwright-chromium/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/playwright-core/README.md:1— `playwright-core` is a command-line package (`bin` in `REDACTED`) and neither `packages/playwright-core/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/playwright-firefox/README.md:1— `playwright-firefox` is a command-line package (`bin` in `REDACTED`) and neither `packages/playwright-firefox/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/playwright-webkit/README.md:1— `playwright-webkit` is a command-line package (`bin` in `REDACTED`) and neither `packages/playwright-webkit/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Fat interface: DashboardChannel (26 required operations) packages/dashboard/src/dashboardChannel.ts:77— `DashboardChannel` declares 26 required operations: `selectTab`, `closeTab`, `newTab`, `closeSession`, `setVisible`, `navigate`, `back`, `forward`, `reload`, `mousemove`, `mousedown`, `mouseup`, `wheel`, `keydown`, `keyup`, `startRecording`, `stopRecording`, `readStream`, `screenshot`, `submitAnnotation`, `cancelAnnotation`, `debuggerResume`, `debuggerPause`, `debuggerStep`, `on`, `off`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: PageDelegate (31 required operations) packages/playwright-core/src/server/page.ts:59— `PageDelegate` declares 31 required operations: `reload`, `goBack`, `goForward`, `requestGC`, `addInitScript`, `removeInitScripts`, `closePage`, `navigateFrame`, `updateExtraHTTPHeaders`, `updateEmulatedViewportSize`, `updateEmulateMedia`, `updateRequestInterception`, `updateFileChooserInterception`, `bringToFront`, `setBackgroundColor`, `takeScreenshot`, `adoptElementHandle`, `getContentFrame`, `getOwnerFrame`, `getContentQuads`, `setInputFilePaths`, `getBoundingBox`, `getFrameElement`, `scrollRectIntoViewIfNeeded`, `startScreencast`, `stopScreencast`, `rafCountForStablePosition`, `inputActionEpilogue`, `resetForReuse`, `shouldToggleStyleSheetToSyncAnimations`, `setDockTile`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: Output (22 required operations) packages/playwright-core/src/tools/cli-client/output.ts:47— `Output` declares 22 required operations: `version`, `help`, `errorUnknownCommand`, `errorUnknownOption`, `errorTooManyArguments`, `errorAttachConflict`, `errorDetachNotAttached`, `errorBrowserNotOpenForTool`, `errorAttachNoTarget`, `errorInstallGlobalRequiresSkills`, `list`, `closeAll`, `deleteData`, `killAll`, `open`, `attach`, `close`, `detach`, `installed`, `show`, `toolResult`, `installStdio`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: TestServerInterface (16 required operations) packages/playwright/src/isomorphic/testServerInterface.ts:25— `TestServerInterface` declares 16 required operations: `initialize`, `ping`, `watch`, `open`, `resizeTerminal`, `checkBrowsers`, `installBrowsers`, `runGlobalSetup`, `runGlobalTeardown`, `clearCache`, `listFiles`, `listTests`, `runTests`, `findRelatedTestFiles`, `stopTests`, `closeGracefully`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 10 significant file(s) lose their only recent owner: packages/trace-viewer/src/ui/ariaModeView.tsx, packages/trace-viewer/src/ui/filmStrip.tsx, packages/injected/src/webAuthn.ts, packages/utils/crypto.ts, packages/isomorphic/codeFrame.ts, packages/trace-viewer/src/ui/videoThumbnails.ts, packages/playwright-core/src/server/webmcp.ts, packages/playwright-core/src/server/webkit/webview/syncServer.ts (+2 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 7 significant file(s) lose their only recent owner: packages/playwright-core/src/tools/mcp/browserModel.ts, packages/utils/webp/webp.ts, packages/isomorphic/istanbulCoverage.ts, packages/playwright-core/src/server/bidi/bidiOverCdp.ts, packages/playwright-core/src/tools/mcp/protocol.ts, packages/utils/pipeTransport.ts, packages/isomorphic/yaml.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 3 significant file(s) lose their only recent owner: packages/playwright/src/common/fixtures.ts, REDACTED, utils/doclint/dotnetXmlDocumentation.js. Pair on, review, or document these before any departure.
README/code drift docs/src/test-runners-csharp.md:389— docs/src/test-runners-csharp.md names .NET 10, but the projects target .NET 8. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift tests/assets/modernizr/README.md:5— tests/assets/modernizr/README.md links to `modernizr.com`, but `tests/assets/modernizr/modernizr.com` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
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 (23 single-owned of 563 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; 563 of the 796 production source files in this repository met that bar). They are anonymized user #4 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/playwright-core/src/server/ebml.ts.
No ADRs found utils/doclint/linting-code-snippets/csharp/linting-code-snippets.csproj:4— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `utils/doclint/linting-code-snippets/csharp/linting-code-snippets.csproj` makes this repository a deployable product (line 4).
D21 · Naming Consistency· `checkCdpMethod` spells `Cdp` where 21 names in the project spell it `CDP` · ×1
`checkCdpMethod` spells `Cdp` where 21 names in the project spell it `CDP` packages/extension/src/cdpPolicy.ts:33— 21 of 23 names in project playwright-internal spell the token `CDP` (21 of 23; unit: names in project playwright-internal containing `CDP`). Peers: Browser.newBrowserCDPSession (packages/playwright-core/src/client/browser.ts:158); BrowserContext.newCDPSession (packages/playwright-core/src/client/browserContext.ts:502); BrowserType.connectOverCDP (packages/playwright-core/src/client/browserType.ts:134); BrowserType.connectOverCDP (packages/playwright-core/src/client/browserType.ts:135); BrowserType.connectOverCDP (packages/playwright-core/src/client/browserType.ts:136). Rename to `checkCDPMethod`. [rule N6]
D21 · Naming Consistency· `AnchorID` spells `ID` where 412 names in the project spell it `Id` · ×1
`AnchorID` spells `ID` where 412 names in the project spell it `Id` packages/html-reporter/src/links.tsx:190— 412 of 413 names in project playwright-internal spell the token `Id` (412 of 413; unit: names in project playwright-internal containing `Id`). Peers: annotations.newAnnotationId (packages/dashboard/src/annotations.tsx:56); DashboardModel._requestId (packages/dashboard/src/dashboardModel.ts:101); DashboardModel.selectAnnotateFrame(focusAnnotationId) (packages/dashboard/src/dashboardModel.ts:219); DashboardModel.updateFrameAnnotations(frameId) (packages/dashboard/src/dashboardModel.ts:256); Transport._lastId (packages/dashboard/src/transport.ts:19). Rename to `AnchorId`. [rule N6]
D21 · Naming Consistency· `connectBidiOverCdp` spells `Cdp` where 21 names in the project spell it `CDP` · ×1
`connectBidiOverCdp` spells `Cdp` where 21 names in the project spell it `CDP` packages/playwright-core/src/server/bidi/bidiOverCdp.ts:29— 21 of 23 names in project playwright-internal spell the token `CDP` (21 of 23; unit: names in project playwright-internal containing `CDP`). Peers: Browser.newBrowserCDPSession (packages/playwright-core/src/client/browser.ts:158); BrowserContext.newCDPSession (packages/playwright-core/src/client/browserContext.ts:502); BrowserType.connectOverCDP (packages/playwright-core/src/client/browserType.ts:134); BrowserType.connectOverCDP (packages/playwright-core/src/client/browserType.ts:135); BrowserType.connectOverCDP (packages/playwright-core/src/client/browserType.ts:136). Rename to `connectBidiOverCDP`. [rule N6]
D21 · Naming Consistency· `_installMSEdgeChannel` spells `MS` where 25 names in the project spell it `Ms` · ×1
`_installMSEdgeChannel` spells `MS` where 25 names in the project spell it `Ms` packages/playwright-core/src/server/registry/index.ts:1142— 25 of 26 names in project playwright-internal spell the token `Ms` (25 of 26; unit: names in project playwright-internal containing `Ms`). Peers: CRNetworkManager._timestampToWallTimeMsForWebSocket (packages/playwright-core/src/server/chromium/crNetworkManager.ts:562); WritableStreamSdkObject.lastModifiedMs (packages/playwright-core/src/server/dispatchers/writableStreamDispatcher.ts:28); WritableStreamSdkObject.constructor(lastModifiedMs) (packages/playwright-core/src/server/dispatchers/writableStreamDispatcher.ts:30); WritableStreamDispatcher.constructor(lastModifiedMs) (packages/playwright-core/src/server/dispatchers/writableStreamDispatcher.ts:40); ebml.writeClusterHeader(timestampMs) (packages/playwright-core/src/server/ebml.ts:132). Rename to `_installMsEdgeChannel`. [rule N6]
D21 · Naming Consistency· `getFromENV` spells `ENV` where 20 names in the project spell it `Env` · ×1
`getFromENV` spells `ENV` where 20 names in the project spell it `Env` packages/utils/env.ts:17— 20 of 22 names in project playwright-internal spell the token `Env` (20 of 22; unit: names in project playwright-internal containing `Env`). Peers: config.configFromEnv (packages/playwright-core/src/tools/mcp/config.ts:428); index.connectOptionsFromEnv (packages/playwright/src/index.ts:621); base.resolveFromEnv (packages/playwright/src/reporters/base.ts:662); html.reportFolderFromEnv (packages/playwright/src/reporters/html.ts:196); html.getHtmlReportOptionProcessEnv (packages/playwright/src/reporters/html.ts:202). Rename to `getFromEnv`. [rule N6]
D21 · Naming Consistency· `getAsBooleanFromENV` spells `ENV` where 20 names in the project spell it `Env` · ×1
`getAsBooleanFromENV` spells `ENV` where 20 names in the project spell it `Env` packages/utils/env.ts:24— 20 of 22 names in project playwright-internal spell the token `Env` (20 of 22; unit: names in project playwright-internal containing `Env`). Peers: config.configFromEnv (packages/playwright-core/src/tools/mcp/config.ts:428); index.connectOptionsFromEnv (packages/playwright/src/index.ts:621); base.resolveFromEnv (packages/playwright/src/reporters/base.ts:662); html.reportFolderFromEnv (packages/playwright/src/reporters/html.ts:196); html.getHtmlReportOptionProcessEnv (packages/playwright/src/reporters/html.ts:202). Rename to `getAsBooleanFromEnv`. [rule N6]
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 16 of 563 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; 563 of the 796 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: utils/linux-browser-dependencies/inside_docker/list_dependencies.js, packages/trace-viewer/src/ui/codegen.ts, browser_patches/firefox/juggler/SimpleChannel.js, packages/dashboard/src/annotateView.tsx, browser_patches/firefox/juggler/Helper.js, packages/utils/image_tools/stats.ts, packages/utils/image_tools/compare.ts, browser_patches/firefox/juggler/protocol/Dispatcher.js (and 8 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
Logging is not universal — Only 3/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/playwright-chromium`, `packages/playwright-firefox`, `packages/playwright-test`, `packages/playwright-webkit`, `utils/doclint/linting-code-snippets/java` and 1 more.
No SAST .github/workflows/agent-review.yml:7— 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 22 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.
P3 · Security & performance tooling· Dependabot does not watch nuget/pip/maven/gradle · ×1
Dependabot does not watch nuget/pip/maven/gradle .github/dependabot.yml:2— `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `nuget`, `pip`, `maven`, `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Unused export 'PlusIcon' packages/dashboard/src/icons.tsx:85— Nothing imports this binding — it is safe to review for removal.
X7 · Silent fallback defaults· Pending state with no failure state · ×1
Pending state with no failure state packages/html-reporter/src/reportView.tsx:168— The view draws `<TestCaseViewLoader report= next= prev= testId= testIdToFileIdMap= />` under `report`, but `report` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Skipped (documented): (unnamed test) tests/extension/extension.spec.ts:62— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) tests/extension/scheme-detach.spec.ts:45— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) tests/assets/reading-list/react-dom_15.7.0.js:12046— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
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.
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 15 file(s) — `packages/dashboard/src/sessionSidebar.tsx`, `packages/injected/src/utilityScript.ts`, `packages/isomorphic/trace/trace.ts`, `packages/playwright-core/src/browserServerImpl.ts`, `REDACTED`, … (+10 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a1d96f-5405-7acd-9556-a36cb86c6db7 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 97 · Warnings: 2246 · Recommendations: 173 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 09:41 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.