playwright — Watchdog Audit

Executive summary

This system is a large, valuable asset with an overall health score of 51%, indicating it is workable but carries significant operational risk. With nearly 155,000 lines of production code and a rebuild cost of approximately €410,000, the business has substantial capital tied up in this platform. The primary concern is not immediate failure, but a compounding drag on delivery speed and a critical compliance gap that threatens market access.

The most urgent risk is Accessibility, which scored only 41%. For a system of this size, this is not just a technical debt item but a direct business liability. Non-compliant interfaces can exclude users, invite legal challenges, and damage brand reputation. Remediation here offers the highest protection for the asset’s value, turning a potential compliance failure into a competitive advantage.

Second, the codebase imposes a Velocity Tax on every change. Quality signals suggest that modifications in weaker areas cost 9–21% more effort than in clean code. This inefficiency acts as a hidden tax on the team, slowing down feature delivery and increasing long-term maintenance costs. Over time, this drag compounds, making the system harder and more expensive to evolve as it grows.

Despite these risks, the system shows strength in maturity and documentation, with a score of 80%. This suggests that new team members can onboard effectively and that the core logic is understandable. The architecture is also reasonably sound at 60%, meaning changes do not ripple uncontrollably. These foundations provide a stable base for targeted improvements.

Focus first on making custom controls keyboard-operable and enforcing accessibility standards in the toolchain. This single action breaks even in one to two months by eliminating the annual drag of non-compliant code. It is the highest-leverage move, offering immediate ROI and reducing long-term risk. Other improvements can wait until this foundation is secure.

Note that domain modeling, event-driven patterns, and test coverage were not measured. The assessment is partial, focusing on the areas with the most significant impact on business outcomes. Addressing the accessibility gap and velocity tax will yield the greatest return on investment for the organization.

Code Health 71% Adequate · gated by D2 Architecture 60% Adequate · gated by R9 Maturity 80% Strong Readiness 54% Adequate · gated by P3 Security 65% Adequate · gated by D29, D36 Accessibility 41% Weak · gated by AC4 Performance 60% Adequate

How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.

Accessibility 41% · 46% weightReadiness 54% · 25% weightArchitecture 60% · 14% weightPerformance 60% · 8% weightSecurity 65% · 4% weightCode Health 71% · 2% weightMaturity 80% · 1% weight

Raise Accessibility 41 → 70 (the Healthy floor) ⇒ headline 51 → ~59.

Code composition — where the lines go

Plumbing 0%Tests 100%

New since the last scan (100+)

1575 finding(s) are new versus the previous scan (2026-08-07) — surfaced by this scheduled scan itself, no pull request required. Showing the first 100; the full set is in the report.

D1 · snapshotterInjected.frameSnapshotStreamer (cyclomatic 146) packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts
D1 · cssTokenizer.tokenize (cyclomatic 143) packages/isomorphic/cssTokenizer.ts
D1 · roleUtils.getTextAlternativeInternal (cyclomatic 138) packages/injected/src/roleUtils.ts
D1 · Streamer.captureSnapshot (cyclomatic 106) packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts
D1 · uiModeView.UIModeView (cyclomatic 88) packages/trace-viewer/src/ui/uiModeView.tsx
D1 · generate_channels.generateChannels (cyclomatic 81) utils/generate_channels.js
D1 · annotations.Annotations (cyclomatic 80) packages/dashboard/src/annotations.tsx
D1 · check_deps.innerCheckDeps (cyclomatic 78) utils/check_deps.js
D1 · selectorParser.parseAttributeSelector (cyclomatic 69) packages/isomorphic/selectorParser.ts
D1 · dashboard.Dashboard (cyclomatic 68) packages/dashboard/src/dashboard.tsx
D1 · APIRequestContext._sendRequest (cyclomatic 65) packages/playwright-core/src/server/fetch.ts
D1 · webSocketMock.inject (cyclomatic 61) packages/injected/src/webSocketMock.ts
D1 · cssParser.parseCSS (cyclomatic 59) packages/isomorphic/cssParser.ts
D1 · generateDotnetApi.renderMethod (cyclomatic 58) utils/doclint/generateDotnetApi.js
D1 · InjectedScript.expectSingleElement (cyclomatic 57) packages/injected/src/injectedScript.ts
D1 · program.program (cyclomatic 57) packages/playwright-core/src/tools/cli-client/program.ts
D1 · ansi2html.ansi2html (cyclomatic 56) packages/web/src/ansi2html.ts
D1 · snapshotRenderer.snapshotScript (cyclomatic 55) packages/isomorphic/trace/snapshotRenderer.ts
D1 · ariaSnapshot.generateAriaTree (cyclomatic 52) packages/injected/src/ariaSnapshot.ts
D1 · cli.run (cyclomatic 47) utils/doclint/cli.js
D1 · locatorGenerators.innerAsLocators (cyclomatic 46) packages/isomorphic/locatorGenerators.ts
D1 · SnapshotRenderer.render (cyclomatic 46) packages/isomorphic/trace/snapshotRenderer.ts
D1 · recorder.Recorder (cyclomatic 46) packages/recorder/src/recorder.tsx
D1 · workbench.PartitionedWorkbench (cyclomatic 45) packages/trace-viewer/src/ui/workbench.tsx
D1 · ariaSnapshot.parseAriaSnapshot (cyclomatic 44) packages/isomorphic/ariaSnapshot.ts
D1 · utilityScriptSerializers.innerSerialize (cyclomatic 44) packages/isomorphic/utilityScriptSerializers.ts
D1 · ariaSnapshotRenderer.renderAriaSnapshotAsYaml (cyclomatic 43) packages/isomorphic/ariaSnapshotRenderer.ts
D1 · generateDotnetApi.translateType (cyclomatic 42) utils/doclint/generateDotnetApi.js
D1 · JavaLocatorFactory.generateLocator (cyclomatic 40) packages/isomorphic/locatorGenerators.ts
D1 · PythonLocatorFactory.generateLocator (cyclomatic 39) packages/isomorphic/locatorGenerators.ts
D1 · APIRequestContext._innerFetch (cyclomatic 39) packages/playwright-core/src/client/fetch.ts
D1 · FrameSession._initialize (cyclomatic 39) REDACTED
D1 · consoleTab.useConsoleTabModel (cyclomatic 39) REDACTED
D1 · codeMirrorWrapper.CodeMirrorWrapper (cyclomatic 39) packages/web/src/components/codeMirrorWrapper.tsx
D1 · minimist.minimist (cyclomatic 38) packages/playwright-core/src/tools/cli-client/minimist.ts
D1 · JavaScriptLocatorFactory.generateLocator (cyclomatic 37) packages/isomorphic/locatorGenerators.ts
D1 · CSharpLocatorFactory.generateLocator (cyclomatic 37) packages/isomorphic/locatorGenerators.ts
D1 · CRNetworkManager._onRequest (cyclomatic 37) packages/playwright-core/src/server/chromium/crNetworkManager.ts
D1 · bidiExecutionContext.renderPreview (cyclomatic 37) packages/playwright-core/src/server/bidi/bidiExecutionContext.ts
D1 · workbenchLoader.WorkbenchLoader (cyclomatic 37) REDACTED
D1 · treeView.TreeView (cyclomatic 37) packages/web/src/components/treeView.tsx
D1 · dashboard_compressed_v1.compressReports (cyclomatic 37) utils/flakiness-dashboard/processing/dashboard_compressed_v1.js
D1 · ariaSnapshot.matchesNode (cyclomatic 36) packages/injected/src/ariaSnapshot.ts
D1 · ariaSnapshot.renderAriaTreeAsJSON (cyclomatic 36) packages/injected/src/ariaSnapshot.ts
D1 · ElementHandle._performPointerAction (cyclomatic 36) packages/playwright-core/src/server/dom.ts
D1 · TraceModernizer._innerAppendEvent (cyclomatic 34) packages/isomorphic/trace/traceModernizer.ts
D1 · splitView.SplitView (cyclomatic 34) packages/web/src/components/splitView.tsx
D1 · roleSelectorEngine.queryRole (cyclomatic 33) packages/injected/src/roleSelectorEngine.ts
D1 · selectorGenerator.buildTextCandidates (cyclomatic 33) packages/injected/src/selectorGenerator.ts
D1 · hostPlatform.calculatePlatform (cyclomatic 33) packages/utils/hostPlatform.ts
D1 · Page.expectScreenshot (cyclomatic 32) packages/playwright-core/src/server/page.ts
D1 · browserActions.launchContext (cyclomatic 32) packages/playwright-core/src/cli/browserActions.ts
D1 · timeline.Timeline (cyclomatic 32) packages/trace-viewer/src/ui/timeline.tsx
D1 · imageDiffView.ImageDiffView (cyclomatic 32) packages/web/src/shared/imageDiffView.tsx
D1 · reportView.ReportView (cyclomatic 31) packages/html-reporter/src/reportView.tsx
D1 · selectorGenerator.generateSelectorFor (cyclomatic 31) packages/injected/src/selectorGenerator.ts
D1 · webAuthn.inject (cyclomatic 31) packages/injected/src/webAuthn.ts
D1 · Response._build (cyclomatic 31) packages/playwright-core/src/tools/backend/response.ts
D1 · playbackControl.usePlayback (cyclomatic 31) packages/trace-viewer/src/ui/playbackControl.tsx
D1 · utilityScriptSerializers.parseEvaluationResultValue (cyclomatic 30) packages/isomorphic/utilityScriptSerializers.ts
D1 · Frame._expectInternal (cyclomatic 30) packages/playwright-core/src/server/frames.ts
D1 · traceConsole.traceConsole (cyclomatic 30) packages/playwright-core/src/tools/trace/traceConsole.ts
D1 · serializers.innerSerializeValue (cyclomatic 30) packages/protocol/src/serializers.ts
D1 · ExecutionContext._createRemoteObject (cyclomatic 29) browser_patches/firefox/juggler/content/Runtime.js
D1 · selectorGenerator.buildNoTextCandidates (cyclomatic 29) packages/injected/src/selectorGenerator.ts
D1 · serializers.innerParseSerializedValue (cyclomatic 29) packages/protocol/src/serializers.ts
D1 · InjectedScript.elementState (cyclomatic 28) packages/injected/src/injectedScript.ts
D1 · selectorParser.parseSelectorString (cyclomatic 28) packages/isomorphic/selectorParser.ts
D1 · JavaScriptLanguageGenerator._generateActionCall (cyclomatic 28) packages/isomorphic/codegen/javascript.ts
D1 · jsonSchema.validate (cyclomatic 28) packages/isomorphic/jsonSchema.ts
D1 · traceRequests.traceRequest (cyclomatic 28) packages/playwright-core/src/tools/trace/traceRequests.ts
D1 · main.doFetch (cyclomatic 28) packages/trace-viewer/src/sw/main.ts
D1 · listView.ListView (cyclomatic 28) packages/web/src/components/listView.tsx
D1 · roleSelectorEngine.validateAttributes (cyclomatic 27) packages/injected/src/roleSelectorEngine.ts
D1 · WVPage._onConsoleMessage (cyclomatic 27) packages/playwright-core/src/server/webkit/webview/wvPage.ts
D1 · innerCheckDeps::visit (cyclomatic 27) utils/check_deps.js
D1 · TargetRegistry.constructor (cyclomatic 26) browser_patches/firefox/juggler/TargetRegistry.js
D1 · ariaSnapshot.toAriaNode (cyclomatic 26) packages/injected/src/ariaSnapshot.ts
D1 · KeyParser._applyAttribute (cyclomatic 26) packages/isomorphic/ariaSnapshot.ts
D1 · TraceModel.constructor (cyclomatic 26) packages/isomorphic/trace/traceModel.ts
D1 · screenshotter.inPagePrepareForScreenshots (cyclomatic 26) packages/playwright-core/src/server/screenshotter.ts
D1 · Frame.waitForSelector (cyclomatic 26) packages/playwright-core/src/server/frames.ts
D1 · PlaywrightServer.constructor (cyclomatic 26) packages/playwright-core/src/remote/playwrightServer.ts
D1 · InjectedScript.dispatchEvent (cyclomatic 25) packages/injected/src/injectedScript.ts
D1 · markdown.buildTree (cyclomatic 25) utils/markdown.js
D1 · index.jsonToTS (cyclomatic 25) utils/protocol-types-generator/index.js
D1 · Filter.matches (cyclomatic 24) packages/html-reporter/src/filter.ts
D1 · injectedScript.createTextMatcher (cyclomatic 24) packages/injected/src/injectedScript.ts
D1 · JavaLanguageGenerator._generateActionCall (cyclomatic 24) packages/isomorphic/codegen/java.ts
D1 · BrowserContextDispatcher.constructor (cyclomatic 24) packages/playwright-core/src/server/dispatchers/browserContextDispatcher.ts
D1 · processLauncher.launchProcess (cyclomatic 24) REDACTED
D1 · debuggerPanel.DebuggerPanel (cyclomatic 23) packages/dashboard/src/debuggerPanel.tsx
D1 · SelectorEvaluatorImpl._matchesParents (cyclomatic 23) packages/injected/src/selectorEvaluator.ts
D1 · InjectedScript.expectHitTarget (cyclomatic 23) packages/injected/src/injectedScript.ts
D1 · injectedScript.deepEquals (cyclomatic 23) packages/injected/src/injectedScript.ts
D1 · selectorParser.parseSelector (cyclomatic 23) packages/isomorphic/selectorParser.ts
D1 · CSharpLanguageGenerator._generateActionCall (cyclomatic 23) packages/isomorphic/codegen/csharp.ts
D1 · PythonLanguageGenerator._generateActionCall (cyclomatic 23) packages/isomorphic/codegen/python.ts
D1 · TraceModernizer._modernize_8_to_9 (cyclomatic 23) packages/isomorphic/trace/traceModernizer.ts
D1 · TraceLoader.load (cyclomatic 23) packages/isomorphic/trace/traceLoader.ts

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €140,000–€690,000

Cost to rebuild	€140,000–€690,000 (1.4–4.3 person-years (2,274–7,214 h), ~1–6 engineers)
Domain complexity	Standard — harder problems cost more per line
Quality factor	0.7× (at 51% quality) — the last 20% of quality is most of the work
Size & shape	Large · effort split not classified for 153,005 line(s) outside the .NET model (the tier breakdown is a C#-only syntax walk)
Effort basis	The rebuild estimate prices 153,058 code lines. Comment-only lines count toward the 154,690-line size but are not build effort.

This codebase represents roughly ~2.8 person-years of build effort (about ~€410,000 to rebuild). Its weakest lens is Accessibility at 41% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.

+8.5 pts · Medium effort · Keyboard semantics

Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.

+8.5 pts · Medium effort · A11y enforcement

Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.

+8.5 pts · Medium effort · Text alternatives

Diagnosis — what's actually going on

Value concentrated against a weak lens · High · Value at risk

This is a Large asset (~2.8 person-years to rebuild), and its weakest lens is Accessibility at 41%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Large, ~2.8 person-years rebuild (154,690 LoC) · weakest lens: Accessibility 41%

→ Direct remediation budget at Accessibility first — highest risk-reduction per euro on an asset this size.

The top fix pays for itself · High · Economics

The top-ranked fix costs roughly 3–10 engineer-days once. Not doing it costs about 82.5–495 engineer-days every year, paid as drag on the ~358,710 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 1–2 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 9–21% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.

Evidence: D15 churn: 88,449 line(s) changed over a 90-day window ⇒ ~358,710/year · D1/D2 code quality: averaging 4.3/10 ⇒ a 9–21% drag on each change · top-ranked remediation: Medium effort ⇒ about 3–10 engineer-day(s)

→ Do the top-ranked fix now if this code will still be yours in 2 months.

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.

A velocity tax on every change · Medium · Economics

The code-quality signals (complexity, duplication, cohesion) average 4.3/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 9–21% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)

Evidence: D1/D2 code quality: averaging 4.3/10 across the code-quality signals actually measured

→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.

Architecture — module dependency matrix

Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

549 modules, 1183 dependencies. 8 dependency cycles across 58 modules, marked above the diagonal.

Showing the 40 most-connected modules; 509 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →	1 browser_patches.firefox.juggler.TargetRegistry	2 browser_patches.firefox.juggler.content.FrameTree	3 browser_patches.firefox.juggler.content.Runtime	4 browser_patches.firefox.juggler.protocol.Dispatcher	6 packages.injected.src.injectedScript	7 packages.playwright-core.src.client.eventEmitter	8 packages.playwright-core.src.server.types	10 packages.playwright.src.common.test	11 packages.playwright-core.src.client.channelOwner	12 packages.playwright-core.src.server.progress	14 packages.playwright-core.src.client.jsHandle	15 packages.playwright-core.src.client.network	16 packages.playwright-core.src.client.elementHandle	18 packages.playwright-core.src.server.transport	19 packages.playwright-core.src.client.page	21 packages.playwright-core.src.server.dom	22 packages.playwright-core.src.server.instrumentation	24 packages.playwright-core.src.server.android.android	25 packages.playwright-core.src.server.chromium.crConnection	27 packages.playwright-core.src.server.frames	29 packages.playwright-core.src.client.playwright	30 packages.playwright-core.src.server.page	31 packages.playwright-core.src.client.browserType	33 packages.playwright-core.src.server.chromium.crPage	36 packages.playwright-core.src.client.browser	40 packages.playwright-core.src.server.chromium.crBrowser
1 browser_patches.firefox.juggler.TargetRegistry
2 browser_patches.firefox.juggler.content.FrameTree
3 browser_patches.firefox.juggler.content.Runtime
4 browser_patches.firefox.juggler.protocol.Dispatcher
5 packages.dashboard.src.dashboardChannel
6 packages.injected.src.injectedScript
7 packages.playwright-core.src.client.eventEmitter
8 packages.playwright-core.src.server.types
9 packages.playwright.src.common.config
10 packages.playwright.src.common.test
11 packages.playwright-core.src.client.channelOwner						1
12 packages.playwright-core.src.server.progress																	1
13 packages.playwright.src.reporters.reporterV2								4
14 packages.playwright-core.src.client.jsHandle									1
15 packages.playwright-core.src.client.network	1	2							5						1
16 packages.playwright-core.src.client.elementHandle		1							1		1
17 packages.playwright-core.src.server.dispatchers.browserContextDispatcher	1			1						1		2
18 packages.playwright-core.src.server.transport										1		1
19 packages.playwright-core.src.client.page	1	2					1		2			4	1
20 packages.playwright-core.src.client.browserContext	1	1							1			4			3
21 packages.playwright-core.src.server.dom		2			1					1	1		1		1
22 packages.playwright-core.src.server.instrumentation	2					1				2					2										2
23 packages.playwright-core.src.tools.backend.tab	1					1						2			1
24 packages.playwright-core.src.server.android.android	1					1				2							2
25 packages.playwright-core.src.server.chromium.crConnection										1				1			3
26 packages.playwright-core.src.server.dispatchers.dispatcher				1		1				2							1
27 packages.playwright-core.src.server.frames		3					2			3	1	2	1		2	1	1
28 packages.playwright-core.src.server.recorder	2	3				1				3					2		2
29 packages.playwright-core.src.client.playwright									1									1					1		1
30 packages.playwright-core.src.server.page	2	3					1			3		2	2		1	3	2			1
31 packages.playwright-core.src.client.browserType	1	1							1												1				1
32 packages.playwright-core.src.server.bidi.bidiPage		1								1			1		1	1						2
33 packages.playwright-core.src.server.chromium.crPage		3					2			1			2		2	2			2			3				1
34 packages.playwright-core.src.server.webkit.webview.wvPage		1					4			1		2	1		1	1						2
35 packages.playwright-core.src.server.webkit.wkPage		1					5			1		2	1		1	1						2
36 packages.playwright-core.src.client.browser	1								1						1								1
37 packages.playwright-core.src.server		2	1				2			3			1		2	1	1						1
38 packages.playwright-core.src.client	1					1	1		1												1				1
39 packages.playwright-core.src.server.browserContext							1			1		2			1		1					2			1
40 packages.playwright-core.src.server.chromium.crBrowser	2													1	2		1		2			1		1	1

Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself

At a glance — Code Health · 71% · Adequate · gated by D2 ·

The Good

D3 · TypeScript God Classes 7.3 GD1 · Repo Unfinished & placeholder code 10.0 R1 · React / TS Type Safety 9.1 R10 · React / TS Code Duplication 8.7 R2 · React / TS Cyclomatic Complexity 8.0 R7 · React / TS Dead Code 8.1 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X4 · Repo Structured logging 10.0

The Bad

D1 · TypeScript Cyclomatic Complexity 5.1 R3 · React / TS Large Files 5.3

The Ugly

D2 · TypeScript Cognitive Complexity 3.6

At a glance — Architecture · 60% · Adequate · gated by R9 ·

The Good

D35 · TypeScript Change Coupling 9.0 AX10 · Repo Code composition 9.7 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 R11 · React / TS Import Boundaries 9.0

The Bad

D5 · TypeScript Coupling 6.9

The Ugly

R9 · React / TS Circular Imports 0.0

At a glance — Maturity · 80% · Strong ·

The Good

D15 · TypeScript Churn × Complexity Hotspots 9.7 D16 · TypeScript Bus Factor 9.6 D19 · TypeScript Documentation Quality 10.0 D21 · TypeScript Naming Consistency 10.0 D34 · TypeScript Knowledge Freshness 9.8 M1 · Repo Documentation (README) 8.7 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

M2 · Repo Architecture documentation 5.0

The Ugly

D20 · TypeScript ADR Quality 0.0

At a glance — Readiness · 54% · Adequate · gated by P3 ·

The Good

D9 · TypeScript Test Distribution 10.0 D10 · TypeScript Test Quality 8.9 D13 · TypeScript REDACTED Scanning 10.0 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P4 · Repo Deployment & Rollback 7.0 R5 · React / TS Dependency Freshness 10.0 R6 · React / TS Tooling 10.0

The Bad

P2 · Repo Observability 6.0 P6 · Repo Release Hygiene 5.0 R4 · React / TS Test Coverage 6.3

The Ugly

P3 · Repo Security & performance tooling 3.0 R8 · React / TS Dependency Hygiene 4.5

At a glance — Security · 65% · Adequate · gated by D29, D36 ·

The Good

D28 · TypeScript Secrets (history) 9.0 D37 · TypeScript Vulnerability-disclosure Policy 10.0 D43 · TypeScript Malicious Dependencies 10.0 D44 · TypeScript Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0

The Bad

D30 · TypeScript Dependency Vulnerabilities 5.3 D31 · TypeScript IaC & Container Security 6.2

The Ugly

D29 · TypeScript Static Analysis (SAST) 0.1 D36 · TypeScript Supply-chain Provenance & Signing 2.5

At a glance — Accessibility · 41% · Weak · gated by AC4 ·

The Good

AC5 · Repo ARIA correctness 10.0 AC6 · Repo Visual & motion safety 7.9

The Bad

AC2 · Repo Forms & labels 5.3 AC3 · Repo Page structure 5.2

The Ugly

AC1 · Repo Text alternatives 4.2 AC4 · Repo Keyboard semantics 1.3 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 60% · Adequate ·

The Bad

PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A03:2021 — Injection	36	High / Critical
A05:2021 — Security Misconfiguration	24	High / Critical
A06:2021 — Vulnerable & Outdated Components	11	High / Critical
A02:2021 — Cryptographic Failures	2	High / Critical

Roadmap

First, ensure all interactive elements are fully keyboard-operable and links have valid hrefs. Next, enforce accessibility standards in the development toolchain by integrating linting and automated testing into the CI pipeline. Simultaneously, provide meaningful text alternatives for all media and ensure every form control has a proper programmatic label. Finally, correct the page structure by adding language attributes, a main landmark, and proper heading hierarchy.

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

Do this	Helps	Effort	Dimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.	+8.5 pts	Medium	Keyboard semantics
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.	+8.5 pts	Medium	A11y enforcement
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.	+8.5 pts	Medium	Text alternatives
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.	+8.4 pts	Medium	Page structure
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.	+8.4 pts	Medium	Forms & labels
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.	+7.6 pts	Medium	Visual & motion safety
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.	+2.6 pts	Medium	Security & performance tooling
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.	+2.6 pts	Medium	Release Hygiene

File quality

Per-file score 0–10 — a quality signature. Of 381 files carrying findings, judged against the Production bar: 2% slop · 67% mixed · 31% near-clean.

File	Score	Band	Worst signal
REDACTED	0.6	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	1.7	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	1.7	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	1.7	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	1.8	Slop	Static Analysis (SAST): High: REDACTED
tests/page/page-autowaiting-no-hang.spec.ts	3.3	Slop	Test Quality: No assertions (empty test): calling window.stop async
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
tests/library/tracing.spec.ts	4.2	Mixed	Test Quality: No assertions (empty test): should survive browser.close with auto-created traces dir
tests/library/page-close.spec.ts	4.4	Mixed	Test Quality: No assertions (empty test): should close page with active dialog
tests/library/unroute-behavior.spec.ts	4.5	Mixed	Test Quality: No assertions (empty test): page.close should not wait for active route handlers on the owning context
tests/page/page-autowaiting-basic.spec.ts	4.8	Mixed	Test Quality: No assertions (empty test): should work with noWaitAfter: true
REDACTED	5.0	Mixed	Static Analysis (SAST): High: REDACTED
packages/injected/src/injectedScript.ts	5.0	Mixed	Change Coupling: Boundary-crossing change coupling: injectedScript.ts ↔ selectors.ts
packages/isomorphic/locatorGenerators.ts	5.0	Mixed	Change Coupling: Boundary-crossing change coupling: locatorGenerators.ts ↔ selectors.ts
tests/library/role-utils.spec.ts	5.0	Mixed	Test Quality: No assertions (empty test): wpt accname #
tests/library/heap.spec.ts	5.0	Mixed	Test Quality: No assertions (empty test): test #${i} to request page and context
tests/page/page-history.spec.ts	5.0	Mixed	Test Quality: No assertions (empty test): page.reload during renderer-initiated navigation
packages/isomorphic/selectorParser.ts	5.0	Mixed	Change Coupling: Boundary-crossing change coupling: selectorParser.ts ↔ locator.ts

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

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

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

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

Could not be resolved — 27

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

Methodology & how to trust this report

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

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

What we checked — 76 dimensions across the health lenses

D1D2D3D5D9D10D13D14D15D16D19D20D21D28D29D30D31D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AC7AX10AX3AX4GD1M1M2M3M4P1P2P3P4P6PF3R1R10R11R2R3R4R5R6R7R8R9X1X12X13X14X15X16X17X18X19X20X21X22X23X25X26X28X29X3X30X32X4

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, 2244 of 2269 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0e58c-76e4-7007-8667-10f5b0d18028.

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

Run transparency — what happened this run

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

D4 Code Duplication — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.c, .cpp, .m) was not read by duplication detection: no source of those file kinds was exposed to the token comparison by any language model this pass could load. Duplication in .ts, .tsx is measured by R10 Code Duplication and is not part of this gap.
D6 Cohesion (LCOM4) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 5 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.ts, .js, .tsx, .mjs), 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository has NuGet-managed production source (.cs), whose `<PackageReference>` dependencies are exactly what this dimension assesses — but `dotnet list package` returned no packages, so there was nothing to assess. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED. This is a gap in the analysis run (restore or project-load failed), not a verdict about this repository. Dependencies declared for the other ecosystems present here (.c, .cpp, .java, .m, .mts, .py, .ts, .tsx) are not read yet either.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, 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.
D18 Solution Shape — evaluation did not complete — Dimension evaluation failed — excluded from the score.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository DOES commit C#/VB source and a project or solution file, so the conventions are there to read and the load still produced nothing. That is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and runs on C# constantly, and the remedy is to inspect the restore, the SDK band and the target resolution — not to build anything.
D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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 solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `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.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
D43 Malicious Dependencies — measured, with a gap in what it reached — 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 solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX2 Stateful singletons — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
P10 Library API & versioning — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads NuGet packaging and C# public API only, and no .NET project was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
PF1 Benchmark discipline — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
PF2 Allocation hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
PF3 Async & latency hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 317 further occurrence(s) are not listed individually; the score already reflects all 357.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 193 further occurrence(s) are not listed individually; the score already reflects all 233.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X10 Duplicated predicate — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's C# was parsed (it ships no .sln or .csproj, so it was read as syntax-only projects), but this check proves its findings from resolved symbols and a reference-free parse resolves none. It abstained rather than report a clean bill it could not earn. That is a gap in this analyzer's reach into build-less repositories — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's C# was parsed (it ships no .sln or .csproj, so it was read as syntax-only projects), but this check proves its findings from resolved symbols and a reference-free parse resolves none. It abstained rather than report a clean bill it could not earn. That is a gap in this analyzer's reach into build-less repositories — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's C# was parsed (it ships no .sln or .csproj, so it was read as syntax-only projects), but this check proves its findings from the project graph and a reference-free parse supplies none. It abstained rather than report a clean bill it could not earn. That is a gap in this analyzer's reach into build-less repositories — not a finding that the repository is free of what this check looks for.
X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity5.1 / 10Adequate✓ Tool-verified

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

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

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

238 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: packages/playwright-core/src/server/bidi/bidiDeserializer.ts (bidiDeserializer.deserializeBidiValue at 28), packages/playwright-core/src/tools/backend/tab.ts (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.

(anonymous) (cyclomatic 22) · ×2utils/roll_browser.js:47

snapshotterInjected.frameSnapshotStreamer (cyclomatic 146)packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:34

cssTokenizer.tokenize (cyclomatic 143)packages/isomorphic/cssTokenizer.ts:77

roleUtils.getTextAlternativeInternal (cyclomatic 138)packages/injected/src/roleUtils.ts:687

Streamer.captureSnapshot (cyclomatic 106)packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:367

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

What to do

Resolve the 2 (anonymous) (cyclomatic 22) finding(s) in Cyclomatic Complexity — start with roll_browser.js, list_dependencies.js. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 snapshotterInjected.frameSnapshotStreamer (cyclomatic 146) finding(s) in Cyclomatic Complexity — start with snapshotterInjected.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 cssTokenizer.tokenize (cyclomatic 143) finding(s) in Cyclomatic Complexity — start with cssTokenizer.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity3.6 / 10Weak✓ Tool-verified

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

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

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

294 method(s) exceeded the cognitive complexity threshold of 15; the worst was generate_channels.generateChannels at 239.

innerCheckDeps::visit (cognitive 54) · ×3utils/check_deps.js:134

generate_channels.generateChannels (cognitive 239)utils/generate_channels.js:239

roleUtils.getTextAlternativeInternal (cognitive 228)packages/injected/src/roleUtils.ts:687

cssTokenizer.tokenize (cognitive 210)packages/isomorphic/cssTokenizer.ts:77

snapshotterInjected.frameSnapshotStreamer (cognitive 179)packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:34

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

What to do

Resolve the 3 innerCheckDeps finding(s) in Cognitive Complexity — start with check_deps.js (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 generate_channels.generateChannels (cognitive 239) finding(s) in Cognitive Complexity — start with generate_channels.js. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 roleUtils.getTextAlternativeInternal (cognitive 228) finding(s) in Cognitive Complexity — start with roleUtils.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes7.3 / 10Strong✓ Tool-verified

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

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

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

112 god class(es) detected.

TooManyMethods: Page · ×37packages/playwright-core/src/client/page.ts:89

FileTooLong: src/injectedScript.ts · ×28packages/injected/src/injectedScript.ts

FunctionTooLong: snapshotterInjected.frameSnapshotStreamer · ×26packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:34

ClassTooLong: InjectedScript · ×14packages/injected/src/injectedScript.ts:92

MethodTooLong: Registry.constructor · ×7packages/playwright-core/src/server/registry/index.ts:510

What to do

Resolve the 37 TooManyMethods finding(s) in God Classes — start with page.ts (2), frames.ts (2), browserContext.ts (2). — One of this dimension's main actionable groups (37 warning-level).
Resolve the 28 FileTooLong finding(s) in God Classes — start with page.ts (2), network.ts (2), injectedScript.ts. — One of this dimension's main actionable groups (28 warning-level).
Resolve the 26 FunctionTooLong finding(s) in God Classes — start with program.ts (3), snapshotterInjected.ts, cssTokenizer.ts. — One of this dimension's main actionable groups (26 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D5 · Coupling6.9 / 10Adequate✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

What to do

Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality8.9 / 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.

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

628 skipped (628 with a documented reason), 569 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8098 tests.

No assertions (empty test): seed · ×39examples/todomvc/tests/seed.spec.ts:3

No assertions: should-uncomplete-completed-todo · ×530examples/todomvc/tests/completing-todos/should-uncomplete-completed-todo.spec.ts:7

Skipped (documented): (unnamed test) · ×628tests/assets/reading-list/react-dom_15.7.0.js:12046

What to do

Resolve the 39 No assertions (empty test) finding(s) in Test Quality — start with unroute-behavior.spec.ts (7), page-autowaiting-no-hang.spec.ts (4), heap.spec.ts (3). — One of this dimension's main actionable groups (39 issue-level).
Resolve the 530 No assertions finding(s) in Test Quality — start with slowmo.spec.ts (39), locator-generator.spec.ts (30), page-aria-snapshot.spec.ts (30). — One of this dimension's main actionable groups (530 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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

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

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

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

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

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

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

0 of 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 package.json, 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots9.7 / 10Stronggated by 103 serious findings✓ Tool-verified

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

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

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

Top hotspots: packages/injected/src/roleUtils.ts (8×138=1104); packages/injected/src/injectedScript.ts (19×57=1083); packages/playwright-core/src/server/fetch.ts (16×65=1040) Repeated repair below the complexity floor: packages/playwright-core/src/tools/mcp/extensionContextFactory.ts (6 of 7 changes were fixes); packages/playwright-core/src/tools/mcp/browserFactory.ts (5 of 9 changes were fixes); packages/playwright-core/src/tools/mcp/cdpRelay.ts (5 of 6 changes were fixes)

Hotspot: packages/injected/src/roleUtils.ts · ×96packages/injected/src/roleUtils.ts:687

Repeated repair: packages/playwright-core/src/tools/mcp/extensionContextFactory.ts · ×7packages/playwright-core/src/tools/mcp/extensionContextFactory.ts:29

What to do

Resolve the 96 Hotspot finding(s) in Churn × Complexity Hotspots — start with fetch.ts (2), browserContext.ts (2), program.ts (2). — One of this dimension's main actionable groups (96 warning-level).
Resolve the 7 Repeated repair finding(s) in Churn × Complexity Hotspots — start with extensionContextFactory.ts, browserFactory.ts, cdpRelay.ts. — One of this dimension's main actionable groups (7 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.

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

24 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/playwright/src/common/fixtures.ts. Counted over 553 of the 788 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.

Do you agree with this assessment?

D19 · Documentation QualityExemplary◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README and a companion architecture/design docs give an overview of Playwright as the end-to-end automation framework for Chromium, Firefox, WebKit with a single API across all three browsers, plus links to documentation (https://playwright.dev), and install/usage guidance. The README also documents several subdirectories (browser_patches/winldd/, packages/playwright-browser-chromium/, etc.) as tools or libraries in the project, each with its own README that is not clipped by the scanner but is internal documentation for those directories.

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.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: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — 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.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D29 · Static Analysis (SAST)0.1 / 10Critical✓ Tool-verified

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

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

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

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

36 finding(s): 0 critical, 22 high, 12 medium, 2 low. semgrep hit a parse error in 20 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), … (+15 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 13 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

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities5.3 / 10Adequate✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir/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, Go, Java and Kotlin via Maven/Gradle, npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

11 finding(s): 0 critical, 6 high, 5 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

REDACTED

What to do

Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Medium vulnerability 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.

Do you agree with this assessment?

D31 · IaC & Container Security6.2 / 10Adequate✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

24 finding(s): 0 critical, 6 high, 18 medium, 0 low.

REDACTED

What to do

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.

Do you agree with this assessment?

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

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

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

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

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

Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D35 · Change Coupling9.0 / 10Adequategated by 14 critical findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: injectedScript.ts↔selectors.ts 90%; crExecutionContext.ts↔wkExecutionContext.ts 90%; TargetRegistry.js↔main.js 85%

Boundary-crossing change coupling: injectedScript.ts ↔ selectors.ts · ×14packages/injected/src/injectedScript.ts

Change coupling: locator.ts ↔ selectors.ts · ×27packages/playwright-core/src/client/locator.ts

Change-coupling hub: TargetRegistry.js → FrameTree.js, PageAgent.js, Runtime.js, main.js, Protocol.js · ×3browser_patches/firefox/juggler/TargetRegistry.js

Change coupling clique: bidiExecutionContext.ts, crExecutionContext.ts, wkExecutionContext.tspackages/playwright-core/src/server/bidi/bidiExecutionContext.ts

What to do

Resolve the 14 Boundary-crossing change coupling finding(s) in Change Coupling — start with injectedScript.ts, selectorParser.ts, locatorGenerators.ts. — One of this dimension's main actionable groups (14 issue-level).
Resolve the 27 Change coupling finding(s) in Change Coupling — start with REDACTED (2), NetworkObserver.js (2), video.ts (2). — One of this dimension's main actionable groups (27 warning-level).
Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with TargetRegistry.js, PageHandler.js, BrowserHandler.js. — One of this dimension's main actionable groups (3 warning-level).

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

Do you agree with this assessment?

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

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

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

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

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

REDACTED

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

What to do

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 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.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

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

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

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

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

No known-vulnerable dependencies in the 2 ecosystem(s) that were scanned (npm,osv). Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives4.2 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). (×2) — packages/dashboard/src/recording.tsx:53, packages/html-reporter/src/testResultView.tsx:190
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×5) — packages/html-reporter/src/testResultView.tsx:172, packages/html-reporter/src/testResultView.tsx:182, packages/trace-viewer/src/ui/attachmentsTab.tsx:140, …

What to do

Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.

Do you agree with this assessment?

AC2 · Forms & labels5.3 / 10Adequate✓ Tool-verified

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

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

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

This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×2) — packages/dashboard/src/annotateView.tsx:115, packages/dashboard/src/annotations.tsx:424
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×8) — packages/injected/src/injectedScript.ts:811, packages/injected/src/injectedScript.ts:811, packages/injected/src/injectedScript.ts:848, …
This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — packages/recorder/src/callLog.tsx:42
This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — packages/web/src/components/codeMirrorWrapper.tsx:203
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — packages/web/src/components/tabbedPane.tsx:67

What to do

Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.

Do you agree with this assessment?

AC3 · Page structure5.2 / 10Adequate✓ Tool-verified

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

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

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

The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — packages/extension/src/ui/connect.html:17, packages/html-reporter/index.html:18
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — packages/trace-viewer/index.html:17
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — packages/trace-viewer/snapshot.html:17
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — packages/trace-viewer/snapshot.html:19
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — packages/trace-viewer/src/ui/networkResourceDetails.tsx:150

What to do

Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.

Do you agree with this assessment?

AC4 · Keyboard semantics1.3 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: interactive elements plus elements the markup gives a click/key handler or the repo's own CSS styles `cursor: pointer`, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

This <div> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click. — packages/dashboard/src/annotations.tsx:366
The repo's own CSS styles .annotations-rect with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — packages/dashboard/src/annotations.tsx:405
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×10) — packages/dashboard/src/settingsView.tsx:63, packages/extension/src/ui/tabItem.tsx:44, packages/html-reporter/src/labels.tsx:31, …
The repo's own CSS styles .gantt-bar with `cursor: pointer`, so this <rect> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — packages/html-reporter/src/gantt.tsx:152
An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. — packages/trace-viewer/src/ui/uiModeView.tsx:461
This role="tree" is the tab stop for the whole widget (it carries the tabindex and the key handler), but nothing tells assistive tech which role="treeitem" is active: the container never sets aria-activedescendant, and no option is focusable, so DOM focus never moves off the container. The highlight a sighted user follows is invisible to a screen reader — arrowing through the widget announces nothing (WCAG 4.1.2). Either set aria-activedescendant on the container to the active option's id, or give the active role="treeitem" tabindex="0" (the rest -1) and focus() it when the selection moves. — packages/web/src/components/treeView.tsx:139
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×2) — packages/web/src/components/treeView.tsx:273, packages/web/src/components/treeView.tsx:285

What to do

Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.

Do you agree with this assessment?

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

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

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

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

Do you agree with this assessment?

AC6 · Visual & motion safety7.9 / 10Strong✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

`* you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ .tag` sets color: white on background-color: #8c959f — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — packages/trace-viewer/src/ui/tag.css:17

What to do

Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.

Do you agree with this assessment?

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

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

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

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

No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 101 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

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

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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.

Do you agree with this assessment?

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

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

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

What to do

Add a README to the 17 of 26 project(s) that lack one — worth up to 1.3 pts.

Do you agree with this assessment?

M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

P2 · Observability6.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

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

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

What to do

Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.

Do you agree with this assessment?

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

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

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

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

What to do

Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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.

Do you agree with this assessment?

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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

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

`executablesOrSharedLibraries` is async and calls existsSync — 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:311
`listInstalledBrowsers` is async and calls existsSync — 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:1181
`_installDriver` is async and calls existsSync — 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:174
`createProfile` is async and calls existsSync — 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:19
`syncLocalStorageWithSettings` is async and calls mkdirSync, writeFileSync — 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/server/launchApp.ts:101, REDACTED:180
`zip` is async and calls statSync — 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:44
`listen` is async and calls unlinkSync — 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:40
`startTraceViewerServer` is async and calls existsSync — 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:90
`openPage` is async and calls existsSync — 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/browserActions.ts:230
`launchBrowserServer` is async and calls readFileSync — 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:88
`closeTrace` is async and calls existsSync — 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:62
`openTrace` is async and calls existsSync — 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:67
`loadTrace` is async and calls existsSync — 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:79
`installSkills` is async and calls existsSync — 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:30
`startDaemon` is async and calls openSync, readFileSync — 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:114
`resolveCLIConfigForCLI` is async and calls existsSync — 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:158
`patchGitIgnore` is async and calls existsSync — 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:114
`ensureConfiguredBrowserInstalled` is async and calls existsSync — 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:130
`acquireSingleton` is async and calls unlinkSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:238
`killAllDaemons` is async and calls execSync — 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:357
`toHaveScreenshot` is async and calls existsSync, writeFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/matchers/toMatchSnapshot.ts:331
`removeDirAndLogToConsole` is async and calls existsSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/util.ts:367
`mergeTraceFiles` is async and calls existsSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/worker/testTracing.ts:344
`collectFiles` is async and calls existsSync, statSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/runner/projectUtils.ts:174
`detectChangedTestFiles` is async and calls execFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/runner/vcs.ts:22
`onEnd` is async and calls statSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/reporters/blob.ts:76
`build` is async and calls mkdirSync, readdirSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/reporters/html.ts:353
`_writeReportData` is async and calls appendFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/reporters/html.ts:470
`extractReportZip` is async and calls rmSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/reporters/html.ts:237
`init` is async and calls existsSync, readFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/agents/generateAgents.ts:219
`appendToMCPJson` is async and calls readFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/agents/generateAgents.ts:312
`deleteFile` is async and calls existsSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/agents/generateAgents.ts:386
`initRepo` is async and calls existsSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/agents/generateAgents.ts:404
`load` is async and calls readFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/playwright/src/transform/esmLoader.ts:64
`launchProcess` is async and calls rmSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:133
`stopProfiling` is async and calls mkdirSync, writeFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/utils/profiler.ts:37
`onEnd` is async and calls closeSync, mkdirSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — tests/config/parquetReporter.ts:56
`postReportComment` is async and calls readFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — tests/config/postReportComment.js:23
`start` is async and calls existsSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — tests/config/remote-server-impl.js:4

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.

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication8.7 / 10Strong✓ Tool-verified

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

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

78 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) — 62 of them are reported below, and 16 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 78 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 78 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 78 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
32 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 10 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 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/isomorphic/utilityScriptSerializers.ts:253
16 duplicated blocks under packages/playwright-core/src/ have copies in at least two of the sibling directories cli, client, remote, server, tools — 9 of them are reported below, and 7 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:234
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:832
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:1065 · packages/playwright-core/src/server/webkit/wkPage.ts:1093 — 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:1065
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/client/browserContext.ts:179 · packages/playwright-core/src/client/page.ts:178 — the two spans are one implementation copied and then locally edited — 780 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/client/browserContext.ts:179
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 — 88 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/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/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/utilityScriptSerializers.ts:253 · packages/protocol/src/serializers.ts:156 — the two spans are one implementation copied and then locally edited — 621 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/isomorphic/utilityScriptSerializers.ts:253
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
utils/build_deps_true.js:31 · utils/check_deps.js:25 — the two spans are one implementation copied and then locally edited — 487 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. — utils/build_deps_true.js:31
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
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:366 · 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:366
REDACTED:735 · packages/playwright-core/src/server/firefox/ffPage.ts:210 — the two spans are one implementation copied and then locally edited — 347 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:735
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
packages/playwright-core/src/tools/cli-client/channelSessions.ts:88 · packages/utils/chromiumChannels.ts:25 — 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/playwright-core/src/tools/cli-client/channelSessions.ts:88
browser_patches/firefox/juggler/NetworkObserver.js:832 · packages/playwright-core/src/server/network.ts:59 — 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:832
browser_patches/firefox/juggler/protocol/Protocol.js:19 · browser_patches/firefox/juggler/protocol/Protocol.js:87 — the two spans are one implementation copied and then locally edited — 261 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
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:1217 · packages/playwright-core/src/server/webkit/wkPage.ts:1301 — 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:1217
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/playwright-core/src/client/browserContext.ts:420 · packages/playwright-core/src/client/page.ts:589 — 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:420
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:911 — 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

What to do

Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.

Do you agree with this assessment?

R11 · Import Boundaries9.0 / 10Strong✓ Tool-verified

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

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

packages/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/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-core/src/server/bidi/bidiOverCdp.ts:17 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:17
packages/playwright-core/src/server/bidi/bidiOverCdp.ts:18 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:18
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
tests/extension/extension-fixtures.ts:148 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:148
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.

Do you agree with this assessment?

R2 · Cyclomatic Complexity8.0 / 10Strong✓ Tool-verified

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

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

getTextAlternativeInternal has cyclomatic complexity 137 and cognitive complexity 232; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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:687
(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:128
program has cyclomatic complexity 65 and cognitive complexity 79; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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:77
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. — packages/injected/src/injectedScript.ts:1518
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
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
validateProject has cyclomatic complexity 45 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/src/common/configLoader.ts:258
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. — packages/isomorphic/trace/snapshotRenderer.ts:89
innerSerialize has cyclomatic complexity 44 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/utilityScriptSerializers.ts:253
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
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:709
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. — packages/dashboard/src/dashboard.tsx: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
(anonymous) 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:180
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
compressReports has cyclomatic complexity 37 and cognitive complexity 109; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/flakiness-dashboard/processing/dashboard_compressed_v1.js:33
_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:282

What to do

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

Do you agree with this assessment?

R3 · Large Files5.3 / 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.

92 file(s) over 400 lines (counted as significant lines — blank lines excluded — over production source only, tests excluded), largest first: packages/injected/src/injectedScript.ts (1743), packages/playwright-core/src/server/frames.ts (1715), packages/injected/src/recorder/recorder.ts (1609), REDACTED (1499), packages/playwright-core/src/tools/cli-daemon/commands.ts (1308), packages/playwright-core/src/server/registry/index.ts (1295) (+86 more).

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.

tests/config/proxy.ts:19 imports '../third_party/proxy', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — tests/config/proxy.ts
tests/library/browsercontext-har.spec.ts:20 imports '../../packages/utils/third_party/extractZip', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — tests/library/browsercontext-har.spec.ts
tests/library/trace-viewer.spec.ts:22 imports '../../packages/utils/third_party/extractZip', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — tests/library/trace-viewer.spec.ts
tests/playwright-test/reporter-blob.spec.ts:21 imports '../../packages/utils/third_party/extractZip', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — tests/playwright-test/reporter-blob.spec.ts
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. (×36) — packages/injected/src/injectedScript.ts, packages/injected/src/recorder/recorder.ts, packages/injected/src/roleUtils.ts, …

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R5 · Dependency Freshness10.0 / 10Exemplary✓ Tool-verified

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 package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

This repository declares test tooling, and the ✓ above records that declaration — but tests/config/proxy.ts and 3 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — tests/config/proxy.ts

Do you agree with this assessment?

R7 · Dead Code8.1 / 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.

327 file(s) (~168745 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
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) (~617 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 269 application, 82 tooling and 811 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 (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×30) — browser_patches/firefox/juggler/TargetRegistry.js, browser_patches/firefox/juggler/NetworkObserver.js, utils/doclint/generateDotnetApi.js, …
no import path from any entry point (269 application, 82 tooling, 811 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 (269 application, 82 tooling, 811 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (utils/generate_types/index.js, utils/render_release_notes.mjs) — 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/linkUtils.js
no import path from any entry point (269 application, 82 tooling, 811 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 (269 application, 82 tooling, 811 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 — 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.

Do you agree with this assessment?

R8 · Dependency Hygiene4.5 / 10Weak✓ Tool-verified

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

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

Imported but not declared in any reachable package.json — installs work only by hoisting accident. — utils/doclint/cli.js:26
Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — packages/playwright/src/runner/loadUtils.ts:30
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
Declared in packages/web/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

R9 · Circular Imports0.0 / 10Critical✓ Tool-verified

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

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

packages/html-reporter/src/labels.tsx → packages/html-reporter/src/links.tsx → packages/html-reporter/src/labels.tsx — packages/html-reporter/src/labels.tsx
packages/playwright-core/src/cli/program.ts → packages/playwright-core/src/tools/cli-client/program.ts → packages/playwright-core/src/coreBundle.ts → packages/playwright-core/src/cli/program.ts (one verified cycle inside a mutually-dependent group of 4 files) — packages/playwright-core/src/cli/program.ts
packages/playwright-core/src/client/android.ts → packages/playwright-core/src/client/connect.ts → packages/playwright-core/src/client/connection.ts → packages/playwright-core/src/client/android.ts (one verified cycle inside a mutually-dependent group of 5 files) — packages/playwright-core/src/client/android.ts
packages/playwright-core/src/client/browser.ts → packages/playwright-core/src/client/browserContext.ts → packages/playwright-core/src/client/browser.ts (one verified cycle inside a mutually-dependent group of 9 files) — packages/playwright-core/src/client/browser.ts
packages/playwright-core/src/server/browserContext.ts → packages/playwright-core/src/server/debugger.ts → packages/playwright-core/src/server/browserContext.ts (one verified cycle inside a mutually-dependent group of 68 files) — packages/playwright-core/src/server/browserContext.ts
packages/playwright-core/src/server/registry/browserFetcher.ts → packages/playwright-core/src/server/registry/index.ts → packages/playwright-core/src/server/registry/browserFetcher.ts (one verified cycle inside a mutually-dependent group of 3 files) — packages/playwright-core/src/server/registry/browserFetcher.ts
packages/playwright-core/src/tools/utils/mcp/http.ts → packages/playwright-core/src/tools/utils/mcp/server.ts → packages/playwright-core/src/tools/utils/mcp/http.ts — packages/playwright-core/src/tools/utils/mcp/http.ts

What to do

Break each cycle by extracting the shared piece into a module both sides can import.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC4 · Keyboard semantics	2.1.1, 2.4.3	Partial signal
AC5 · ARIA correctness	4.1.2	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	71%	Adequate — gated by D2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	60%	Adequate — gated by R9	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	80%	Strong	Strongest area.
Readiness	54%	Adequate — gated by P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	65%	Adequate — gated by D29, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	41%	Weak — gated by AC4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	60%	Adequate	Acceptable, with room to improve.

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

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

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, .tsx, .mjs), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Not evidenced — 4 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.

C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 50 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.

AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/bui…; runtime evidence skipped 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — Dependency hygiene not measured — no packages were read
D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
D18 Solution Shape — Dimension evaluation failed
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout nor 2+ sibling source directories each declaring an aggregate root. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — Most of this repository's production source (.c, .cpp, .cs, .java, .m, .mts, .py, .ts, .tsx) was not read by navigability analysis, so tracing effort was not assessed — whatever else resolved (another language's projects) is not this repository's navigability. Not scored — this is a gap in the analyzer's reach, 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
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D4 Code Duplication — Duplication not measured — .c, .cpp, .m not exposed to the token comparison
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.
D6 Cohesion (LCOM4) — D6 reads a CS/VB/GO/SCALA/SWIFT/DART/JAVA/PY class graph only — this repository's production source is .c, .cpp, .m, .mts, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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 — the repository wires up no coverage collector for `--collect:"XPlat Code Coverage"` to use; 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. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Domain Modelling — not scored — this repository shows 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 — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
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
P10 Library API & versioning — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
PF2 Allocation hygiene — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X10 Duplicated predicate — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — no async methods found
X24 Document value interpolated into markup unescaped — This check needs a compiled C# program and this repository commits no project file to compile, so only its syntax could be read. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check needs a compiled C# program and this repository commits no project file to compile, so only its syntax could be read. That is a limit of the analyzer, not a finding about your code.
X5 Nullable reference types — This check needs a compiled C# program and this repository commits no project file to compile, so only its syntax could be read. That is a limit of the analyzer, not a finding about your code.
X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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 — 139 finding(s)

D10 · Test Quality · No assertions (empty test) · ×39

No assertions (empty test): seed examples/todomvc/tests/seed.spec.ts:3 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): page.close should not wait for active route handlers on the owning context tests/library/unroute-behavior.spec.ts:120 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): context.close should not wait for active route handlers on the owned pages tests/library/unroute-behavior.spec.ts:135 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): route.continue should not throw if page has been closed tests/library/unroute-behavior.spec.ts:265 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): route.fallback should not throw if page has been closed tests/library/unroute-behavior.spec.ts:279 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): route.fulfill should not throw if page has been closed tests/library/unroute-behavior.spec.ts:293 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should not continue requests in flight (page) tests/library/unroute-behavior.spec.ts:307 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should not continue requests in flight (context) tests/library/unroute-behavior.spec.ts:321 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should survive browser.close with auto-created traces dir tests/library/tracing.spec.ts:471 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should not hang for clicks that open dialogs tests/library/tracing.spec.ts:664 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): start allows restart with different options after stop tests/library/screencast.spec.ts:142 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should not throw with empty handler tests/library/route-web-socket.spec.ts:577 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): 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): 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): should not throw UnhandledPromiseRejection when page closes tests/library/page-close.spec.ts:124 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): 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): 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): 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): 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): should handle rejected certificate in handshake with HTTP/2 tests/library/client-certificates.spec.ts:955 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should keep URL parameters when adding json/version tests/library/chromium/connect-over-cdp.spec.ts:289 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should append /json/version with a slash if there isnt one tests/library/chromium/connect-over-cdp.spec.ts:301 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should pause on context close tests/library/inspector/pause.spec.ts:458 — 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:145 — 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:624 — Test method has an empty body — it asserts nothing and exercises no code.
+ 14 more in this group — see findings.md.

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

Boundary-crossing change coupling: injectedScript.ts ↔ selectors.ts packages/injected/src/injectedScript.ts — `packages/injected/src/injectedScript.ts` (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: selectorParser.ts ↔ locator.ts packages/isomorphic/selectorParser.ts — `packages/isomorphic/selectorParser.ts` (context isomorphic) and `packages/playwright-core/src/client/locator.ts` (context playwright-core) sit in DIFFERENT parts of the tree yet change together 65% of the time (11 of the 17 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 11 shared commits counted here, the most recent 3 are `d7775efb` feat(selectors): add pierceFrames context option (#42033); `d0c1b736` feat(selectors): support entering frames while piercing (#42031); `7ffedf3c` feat: add pierceFrames() locator API (#41963) — run `git show` on any of them.
Boundary-crossing change coupling: locatorGenerators.ts ↔ selectors.ts packages/isomorphic/locatorGenerators.ts — `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 — `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 — `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: snapshotRenderer.ts ↔ snapshotterInjected.ts packages/isomorphic/trace/snapshotRenderer.ts — `packages/isomorphic/trace/snapshotRenderer.ts` (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: utilityScript.ts ↔ page.ts packages/injected/src/utilityScript.ts — `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 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) — 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: traceViewer.ts ↔ traceLoaderBackends.ts packages/playwright-core/src/server/trace/viewer/traceViewer.ts — `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 — `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 — `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 — `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: channelOwner.ts ↔ zones.ts packages/playwright-core/src/client/channelOwner.ts — `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.
Boundary-crossing change coupling: connection.ts ↔ zones.ts packages/playwright-core/src/client/connection.ts — `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 — `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.

AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×8

Click handler on a non-interactive <div> packages/dashboard/src/settingsView.tsx:63 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/extension/src/ui/tabItem.tsx:44 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/html-reporter/src/treeItem.tsx:36 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/web/src/components/codeMirrorWrapper.tsx:203 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/web/src/components/gridView.tsx:78 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/web/src/components/toolbar.tsx:37 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/web/src/components/treeView.tsx:273 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> packages/web/src/components/treeView.tsx:285 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · High CVE · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D31 · IaC & Container Security · High IaC · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

AC1 · Text alternatives · <img> without a text alternative · ×5

<img> without a text alternative packages/html-reporter/src/testResultView.tsx:172 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/html-reporter/src/testResultView.tsx:182 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/trace-viewer/src/ui/attachmentsTab.tsx:140 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/trace-viewer/src/ui/filmStrip.tsx:73 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/trace-viewer/src/ui/networkResourceDetails.tsx:247 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.

AC2 · Forms & labels · <textarea> without a programmatic label · ×5

<textarea> without a programmatic label packages/dashboard/src/annotateView.tsx:115 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label packages/dashboard/src/annotations.tsx:424 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label packages/injected/src/injectedScript.ts:811 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label packages/injected/src/injectedScript.ts:923 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label packages/playwright-core/src/server/frames.ts:1360 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.

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:178 — 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.)

R9 · Circular Imports · Import cycle (2 files) · ×5

Import cycle (2 files) packages/html-reporter/src/labels.tsx — packages/html-reporter/src/labels.tsx → packages/html-reporter/src/links.tsx → packages/html-reporter/src/labels.tsx
Import cycle (2 files) packages/playwright-core/src/client/browser.ts — packages/playwright-core/src/client/browser.ts → packages/playwright-core/src/client/browserContext.ts → packages/playwright-core/src/client/browser.ts (one verified cycle inside a mutually-dependent group of 9 files)
Import cycle (2 files) packages/playwright-core/src/server/browserContext.ts — packages/playwright-core/src/server/browserContext.ts → packages/playwright-core/src/server/debugger.ts → packages/playwright-core/src/server/browserContext.ts (one verified cycle inside a mutually-dependent group of 68 files)
Import cycle (2 files) packages/playwright-core/src/server/registry/browserFetcher.ts — packages/playwright-core/src/server/registry/browserFetcher.ts → packages/playwright-core/src/server/registry/index.ts → packages/playwright-core/src/server/registry/browserFetcher.ts (one verified cycle inside a mutually-dependent group of 3 files)
Import cycle (2 files) packages/playwright-core/src/tools/utils/mcp/http.ts — packages/playwright-core/src/tools/utils/mcp/http.ts → packages/playwright-core/src/tools/utils/mcp/server.ts → packages/playwright-core/src/tools/utils/mcp/http.ts

AC2 · Forms & labels · <input> without a programmatic label · ×4

<input> without a programmatic label packages/injected/src/injectedScript.ts:811 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label packages/injected/src/injectedScript.ts:923 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label packages/injected/src/injectedScript.ts:1005 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label packages/playwright-core/src/server/frames.ts:1360 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.

AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×3

Click handler on a non-interactive <span> packages/html-reporter/src/labels.tsx:31 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> packages/recorder/src/callLog.tsx:42 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> packages/trace-viewer/src/ui/tag.tsx:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

AC2 · Forms & labels · <select> without a programmatic label · ×2

<select> without a programmatic label packages/injected/src/injectedScript.ts:848 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label packages/web/src/components/tabbedPane.tsx:67 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.

AC3 · Page structure · <html> without a lang · ×2

<html> without a lang packages/extension/src/ui/connect.html:17 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/html-reporter/index.html:18 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").

AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×2

Clickable element isn't keyboard-operable packages/dashboard/src/annotations.tsx:405 — The repo's own CSS styles .annotations-rect with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Clickable element isn't keyboard-operable packages/html-reporter/src/gantt.tsx:152 — The repo's own CSS styles .gantt-bar with `cursor: pointer`, so this <rect> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.

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

REDACTED
REDACTED

R9 · Circular Imports · Import cycle (3 files) · ×2

Import cycle (3 files) packages/playwright-core/src/cli/program.ts — packages/playwright-core/src/cli/program.ts → packages/playwright-core/src/tools/cli-client/program.ts → packages/playwright-core/src/coreBundle.ts → packages/playwright-core/src/cli/program.ts (one verified cycle inside a mutually-dependent group of 4 files)
Import cycle (3 files) packages/playwright-core/src/client/android.ts — packages/playwright-core/src/client/android.ts → packages/playwright-core/src/client/connect.ts → packages/playwright-core/src/client/connection.ts → packages/playwright-core/src/client/android.ts (one verified cycle inside a mutually-dependent group of 5 files)

AC2 · Forms & labels · Custom control with no accessible name on <span> · ×1

Custom control with no accessible name on <span> packages/recorder/src/callLog.tsx:42 — This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.

AC2 · Forms & labels · Custom control with no accessible name on <div> · ×1

Custom control with no accessible name on <div> packages/web/src/components/codeMirrorWrapper.tsx:203 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.

AC3 · Page structure · Document without a <title> · ×1

Document without a <title> packages/trace-viewer/snapshot.html:17 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.

AC3 · Page structure · <iframe> without a title · ×1

<iframe> without a title packages/trace-viewer/snapshot.html:19 — An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.

AC4 · Keyboard semantics · Double-click handler on a non-interactive <div> · ×1

Double-click handler on a non-interactive <div> packages/dashboard/src/annotations.tsx:366 — This <div> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.

AC4 · Keyboard semantics · Composite <div role="tree"> never reports its active option · ×1

Composite <div role="tree"> never reports its active option packages/web/src/components/treeView.tsx:139 — This role="tree" is the tab stop for the whole widget (it carries the tabindex and the key handler), but nothing tells assistive tech which role="treeitem" is active: the container never sets aria-activedescendant, and no option is focusable, so DOM focus never moves off the container. The highlight a sighted user follows is invisible to a screen reader — arrowing through the widget announces nothing (WCAG 4.1.2). Either set aria-activedescendant on the container to the active option's id, or give the active role="treeitem" tabindex="0" (the rest -1) and focus() it when the selection moves.

AC4 · Keyboard semantics · Click handler on a non-interactive <img> · ×1

Click handler on a non-interactive <img> packages/web/src/shared/imageDiffView.tsx:202 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.

D28 · Secrets (history) · REDACTED · ×1

REDACTED

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

REDACTED

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

REDACTED

R8 · Dependency Hygiene · Unlisted import 'lodash' · ×1

Unlisted import 'lodash' utils/doclint/cli.js:26 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

Serious — 1483 finding(s)

D10 · Test Quality · No assertions · ×530

No assertions: should-uncomplete-completed-todo examples/todomvc/tests/completing-todos/should-uncomplete-completed-todo.spec.ts:7 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render packages/web/src/components/splitView.spec.ts:23 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render sidebar first packages/web/src/components/splitView.spec.ts:31 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render horizontal split packages/web/src/components/splitView.spec.ts:39 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should hide sidebar packages/web/src/components/splitView.spec.ts:47 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: drag resize packages/web/src/components/splitView.spec.ts:53 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should test app that opens window fast tests/electron/electron-app.spec.ts:243 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should create page for browser view tests/electron/electron-app.spec.ts:269 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should detach debugger on app-initiated exit tests/electron/electron-app.spec.ts:337 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should run pre-ready apis tests/electron/electron-app.spec.ts:346 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: connected tab is in green Playwright group, connect page is closed tests/extension/tab-grouping.spec.ts:43 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: tab added to group gets auto-attached tests/extension/tab-grouping.spec.ts:80 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: chrome:// tab dragged into group stays until it navigates to a debuggable URL tests/extension/tab-grouping.spec.ts:128 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: tab removed from group gets auto-detached tests/extension/tab-grouping.spec.ts:206 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: connected tab is removed from group on disconnect tests/extension/tab-grouping.spec.ts:260 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: tab is re-added to Playwright group after reconnecting tests/extension/tab-grouping.spec.ts:291 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: srgb to lab conversion should work tests/image_tools/unit.spec.ts:26 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: colorDeltaE94 should work tests/image_tools/unit.spec.ts:40 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fast stats and naive computation should match tests/image_tools/unit.spec.ts:47 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ssim + fastStats should match "weber" algorithm from ssim.js tests/image_tools/unit.spec.ts:69 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: typescript types should work tests/installation/typescript-types.spec.ts:18 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: screencast works tests/installation/screencast.spec.ts:18 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: npm: @playwright/test should work tests/installation/playwright-test-package-managers.spec.ts:19 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: npm: playwright + @playwright/test should work tests/installation/playwright-test-package-managers.spec.ts:28 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: npm: @playwright/test + playwright-core should work tests/installation/playwright-test-package-managers.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 505 more in this group — see findings.md.

D15 · Churn × Complexity Hotspots · Hotspot · ×96

Hotspot: packages/injected/src/roleUtils.ts packages/injected/src/roleUtils.ts:687 — packages/injected/src/roleUtils.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 138 in roleUtils.getTextAlternativeInternal at line 687. 4 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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: packages/injected/src/injectedScript.ts packages/injected/src/injectedScript.ts:1518 — packages/injected/src/injectedScript.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in InjectedScript.expectSingleElement at line 1518. 4 of those changes were fix/bug commits, and the other 15 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/injected/src/injectedScript.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/fetch.ts packages/playwright-core/src/server/fetch.ts:326 — packages/playwright-core/src/server/fetch.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in APIRequestContext._sendRequest at line 326. 7 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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:1530 — packages/playwright-core/src/server/frames.ts changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in Frame._expectInternal at line 1530. 6 of those changes were fix/bug commits, and the other 23 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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/page.ts packages/playwright-core/src/server/page.ts:717 — packages/playwright-core/src/server/page.ts changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in Page.expectScreenshot at line 717. 4 of those changes were fix/bug commits, and the other 17 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/playwright-core/src/server/page.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:267 — packages/playwright-core/src/tools/backend/response.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in Response._build at line 267. 5 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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: REDACTED REDACTED:472 — REDACTED changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in FrameSession._initialize at line 472. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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/browserContext.ts packages/playwright-core/src/server/browserContext.ts:809 — packages/playwright-core/src/server/browserContext.ts changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in browserContext.verifyClientCertificates at line 809. 7 of those changes were fix/bug commits, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/playwright-core/src/server/browserContext.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/generate_channels.js utils/generate_channels.js:239 — utils/generate_channels.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 81 in generate_channels.generateChannels at line 239. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- utils/generate_channels.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/playwright-core/src/tools/cli-client/program.ts packages/playwright-core/src/tools/cli-client/program.ts:77 — packages/playwright-core/src/tools/cli-client/program.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in program.program at line 77. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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/isomorphic/trace/snapshotRenderer.ts packages/isomorphic/trace/snapshotRenderer.ts:322 — packages/isomorphic/trace/snapshotRenderer.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in snapshotRenderer.snapshotScript at line 322. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/isomorphic/trace/snapshotRenderer.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/locatorGenerators.ts packages/isomorphic/locatorGenerators.ts:86 — packages/isomorphic/locatorGenerators.ts changed 8 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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/playwright-core/src/server/dom.ts packages/playwright-core/src/server/dom.ts:391 — packages/playwright-core/src/server/dom.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in ElementHandle._performPointerAction at line 391. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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: packages/playwright/src/common/configLoader.ts packages/playwright/src/common/configLoader.ts:128 — packages/playwright/src/common/configLoader.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 87 in configLoader.validateConfig at line 128. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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-core/src/tools/mcp/program.ts packages/playwright-core/src/tools/mcp/program.ts:34 — packages/playwright-core/src/tools/mcp/program.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in program.decorateMCPCommand at line 34. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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/isomorphic/trace/traceModernizer.ts packages/isomorphic/trace/traceModernizer.ts:107 — packages/isomorphic/trace/traceModernizer.ts changed 10 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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.
Hotspot: utils/check_deps.js utils/check_deps.js:62 — utils/check_deps.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 78 in check_deps.innerCheckDeps at line 62. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- utils/check_deps.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/injected/src/ariaSnapshot.ts packages/injected/src/ariaSnapshot.ts:81 — packages/injected/src/ariaSnapshot.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/injected/src/ariaSnapshot.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/utilityScriptSerializers.ts packages/isomorphic/utilityScriptSerializers.ts:253 — packages/isomorphic/utilityScriptSerializers.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/isomorphic/utilityScriptSerializers.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/config.ts packages/playwright-core/src/tools/mcp/config.ts:158 — packages/playwright-core/src/tools/mcp/config.ts changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in config.resolveCLIConfigForCLI at line 158. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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/server/trace/recorder/snapshotterInjected.ts packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:34 — packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 146 in snapshotterInjected.frameSnapshotStreamer at line 34. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/playwright-core/src/server/trace/recorder/snapshotterInjected.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 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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-core/src/client/browserContext.ts packages/playwright-core/src/client/browserContext.ts:99 — packages/playwright-core/src/client/browserContext.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in BrowserContext.constructor at line 99. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/playwright-core/src/client/browserContext.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/frameSelectors.ts packages/playwright-core/src/server/frameSelectors.ts:243 — packages/playwright-core/src/server/frameSelectors.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in FrameSelectors._callOnSelectorInternal at line 243. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/playwright-core/src/server/frameSelectors.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:57 — packages/playwright/src/common/config.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in FullConfigInternal.constructor at line 57. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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.
+ 71 more in this group — see findings.md.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×40

Sync-over-async blocking packages/playwright-core/src/server/registry/dependencies.ts:311 — `executablesOrSharedLibraries` is async and calls existsSync — 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:1181 — `listInstalledBrowsers` is async and calls existsSync — 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:174 — `_installDriver` is async and calls existsSync — 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:19 — `createProfile` is async and calls existsSync — 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:101 — `syncLocalStorageWithSettings` is async and calls mkdirSync, writeFileSync — 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:44 — `zip` is async and calls statSync — 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:40 — `listen` is async and calls unlinkSync — 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:90 — `startTraceViewerServer` is async and calls existsSync — 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/browserActions.ts:230 — `openPage` is async and calls existsSync — 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:88 — `launchBrowserServer` is async and calls readFileSync — 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/trace/traceUtils.ts:62 — `closeTrace` is async and calls existsSync — 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/trace/traceUtils.ts:67 — `openTrace` is async and calls existsSync — 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/trace/traceUtils.ts:79 — `loadTrace` is async and calls existsSync — 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/utils/installSkills.ts:30 — `installSkills` is async and calls existsSync — 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:114 — `startDaemon` is async and calls openSync, readFileSync — 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:158 — `resolveCLIConfigForCLI` is async and calls existsSync — 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:114 — `patchGitIgnore` is async and calls existsSync — 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:130 — `ensureConfiguredBrowserInstalled` is async and calls existsSync — 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:180 — `syncLocalStorageWithSettings` is async and calls mkdirSync, writeFileSync — 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:238 — `acquireSingleton` is async and calls unlinkSync — 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:357 — `killAllDaemons` is async and calls execSync — 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/src/matchers/toMatchSnapshot.ts:331 — `toHaveScreenshot` is async and calls existsSync, writeFileSync — 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/src/util.ts:367 — `removeDirAndLogToConsole` is async and calls existsSync — 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/src/worker/testTracing.ts:344 — `mergeTraceFiles` is async and calls existsSync — 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/src/runner/projectUtils.ts:174 — `collectFiles` is async and calls existsSync, statSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
+ 15 more in this group — see findings.md.

D3 · God Classes · TooManyMethods · ×37

TooManyMethods: Page packages/playwright-core/src/client/page.ts:89 — TooManyMethods — 124 methods. The bar is 30 methods; this is 94 over it, 4.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.
TooManyMethods: Frame packages/playwright-core/src/server/frames.ts:513 — TooManyMethods — 102 methods. The bar is 30 methods; this is 72 over it, 3.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: 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:48 — TooManyMethods — 78 methods. The bar is 30 methods; this is 48 over it, 2.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.
TooManyMethods: InjectedScript packages/injected/src/injectedScript.ts: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 packages/playwright-core/src/server/browserContext.ts: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:55 — 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:121 — TooManyMethods — 71 methods. The bar is 30 methods; this is 41 over it, 2.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PageDispatcher packages/playwright-core/src/server/dispatchers/pageDispatcher.ts:56 — 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: BrowserContext packages/playwright-core/src/client/browserContext.ts:65 — 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: PageTarget browser_patches/firefox/juggler/TargetRegistry.js:408 — 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: FrameSession REDACTED:400 — 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: FrameDispatcher packages/playwright-core/src/server/dispatchers/frameDispatcher.ts:30 — 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: 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 browser_patches/firefox/juggler/protocol/PageHandler.js: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: 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: BrowserHandler browser_patches/firefox/juggler/protocol/BrowserHandler.js:16 — 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: 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.
TooManyMethods: ElementHandleDispatcher packages/playwright-core/src/server/dispatchers/elementHandlerDispatcher.ts:28 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 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.
+ 12 more in this group — see findings.md.

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

No test reaches this file packages/injected/src/injectedScript.ts — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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/PageHandler.js — 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 — 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 — 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/selectorEvaluator.ts — 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 — 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 — 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 — 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 — 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 — 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/ariaSnapshot.ts — 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 — 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 — 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 — 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 — 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 — 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 — 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.
+ 11 more in this group — see findings.md.

D3 · God Classes · FileTooLong · ×28

FileTooLong: src/injectedScript.ts packages/injected/src/injectedScript.ts — FileTooLong — 1351 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: InjectedScript (92-1745). The bar is 500 significant lines; this is 851 over it, 2.70× 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 — 1340 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: Frame (513-1861). The bar is 500 significant lines; this is 840 over it, 2.68× 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 — 1099 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 599 over it, 2.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: cli-daemon/commands.ts packages/playwright-core/src/tools/cli-daemon/commands.ts — FileTooLong — 1056 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 556 over it, 2.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: webkit/wkPage.ts packages/playwright-core/src/server/webkit/wkPage.ts — FileTooLong — 933 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: WKPage (56-1268). The bar is 500 significant lines; this is 433 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 — 930 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: WVPage (54-1218). The bar is 500 significant lines; this is 430 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: juggler/TargetRegistry.js browser_patches/firefox/juggler/TargetRegistry.js — FileTooLong — 906 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 406 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/roleUtils.ts packages/injected/src/roleUtils.ts — FileTooLong — 862 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 362 over it, 1.72× 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 — 851 significant lines (blank, comment-only and punctuation-only lines excluded), about 65% of them inside a single declaration: FrameSession (400-1202). The bar is 500 significant lines; this is 351 over it, 1.70× 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/page.ts packages/playwright-core/src/server/page.ts — FileTooLong — 821 significant lines (blank, comment-only and punctuation-only lines excluded), about 68% of them inside a single declaration: Page (166-977). The bar is 500 significant lines; this is 321 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: server/dom.ts packages/playwright-core/src/server/dom.ts — FileTooLong — 726 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: ElementHandle (121-970). The bar is 500 significant lines; this is 226 over it, 1.45× 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 — 724 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 224 over it, 1.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 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 — 674 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: Tracing (88-807). The bar is 500 significant lines; this is 174 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: client/page.ts packages/playwright-core/src/client/page.ts — FileTooLong — 660 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: Page (89-935). The bar is 500 significant lines; this is 160 over it, 1.32× 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 — 638 significant lines (blank, comment-only and punctuation-only lines excluded), about 64% of them inside a single declaration: APIRequestContext (102-675). The bar is 500 significant lines; this is 138 over it, 1.28× 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: chromium/crNetworkManager.ts packages/playwright-core/src/server/chromium/crNetworkManager.ts — FileTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 128 over it, 1.26× 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/browserContext.ts packages/playwright-core/src/server/browserContext.ts — FileTooLong — 622 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: BrowserContext (90-768). The bar is 500 significant lines; this is 122 over it, 1.24× 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 — 621 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 121 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 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: har/harTracer.ts packages/playwright-core/src/server/har/harTracer.ts — FileTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: HarTracer (66-731). 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 — 577 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 77 over it, 1.15× 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/network.ts packages/playwright-core/src/server/network.ts — FileTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 64 over it, 1.13× 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 — 553 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 53 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
+ 3 more in this group — see findings.md.

D35 · Change Coupling · Change coupling · ×27

Change coupling: locator.ts ↔ selectors.ts packages/playwright-core/src/client/locator.ts — `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 — `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: index.ts ↔ tasks.ts packages/playwright/src/plugins/index.ts — `packages/playwright/src/plugins/index.ts` and `packages/playwright/src/runner/tasks.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 — 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: dashboard.tsx ↔ dashboardChannel.ts packages/dashboard/src/dashboard.tsx — `packages/dashboard/src/dashboard.tsx` 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: loaderMain.ts ↔ loaderHost.ts packages/playwright/src/loader/loaderMain.ts — `packages/playwright/src/loader/loaderMain.ts` and `packages/playwright/src/runner/loaderHost.ts` change together 67% of the time (8 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 8 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 — `REDACTED` and `packages/playwright-core/src/server/firefox/ffPage.ts` change together 66% of the time (47 of the 71 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 47 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: crNetworkManager.ts ↔ wkInterceptableRequest.ts packages/playwright-core/src/server/chromium/crNetworkManager.ts — `packages/playwright-core/src/server/chromium/crNetworkManager.ts` and `packages/playwright-core/src/server/webkit/wkInterceptableRequest.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 `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: testServerConnection.ts ↔ testServer.ts packages/playwright/src/isomorphic/testServerConnection.ts — `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: traceModel.ts ↔ traceModernizer.ts packages/isomorphic/trace/traceModel.ts — `packages/isomorphic/trace/traceModel.ts` and `packages/isomorphic/trace/traceModernizer.ts` change together 63% of the time (12 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 12 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: chromium.ts ↔ browserTypeDispatcher.ts packages/playwright-core/src/server/chromium/chromium.ts — `packages/playwright-core/src/server/chromium/chromium.ts` and `packages/playwright-core/src/server/dispatchers/browserTypeDispatcher.ts` change together 62% of the time (8 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 8 shared commits counted here, the most recent 3 are `4afdd64a` chore(browserType): merge connectOverCDP and connectOverCDPTransport …; `8f503225` feat(browserType): allow passing a ConnectionTransport to connectOver…; `2085f53b` chore: remove unused _connectOverCDPTransport method (#40195) — run `git show` on any of them.
Change coupling: NetworkObserver.js ↔ main.js browser_patches/firefox/juggler/NetworkObserver.js — `browser_patches/firefox/juggler/NetworkObserver.js` and `browser_patches/firefox/juggler/content/main.js` change together 62% of the time (8 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 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: navigate.ts ↔ tab.ts packages/playwright-core/src/tools/backend/navigate.ts — `packages/playwright-core/src/tools/backend/navigate.ts` and `packages/playwright-core/src/tools/backend/tab.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 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 `7563c5a6` fix(mcp): report a dialog opened during navigation instead of timing …; `273c8aab` feat(mcp): support python, java and csharp in --codegen (#42106); `87b2074d` fix(cli): tab-new navigates to url when provided (#39977) — run `git show` on any of them.
Change coupling: video.ts ↔ screencast.ts packages/playwright-core/src/client/video.ts — `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: FrameTree.js ↔ Protocol.js browser_patches/firefox/juggler/content/FrameTree.js — `browser_patches/firefox/juggler/content/FrameTree.js` and `browser_patches/firefox/juggler/protocol/Protocol.js` 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 `d0b1fc27` chore: roll browser patches (#38909); `01103405` chore: update browser patches to 09195c9 (#32877); `3536e81d` chore: update browser patches as of May 26, 2023 (#23556) (#24079) — run `git show` on any of them.
Change coupling: electron.ts ↔ loader.ts packages/playwright-core/src/server/electron/electron.ts — `packages/playwright-core/src/server/electron/electron.ts` and `packages/playwright-core/src/server/electron/loader.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 `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: networkFilters.tsx ↔ tabbedPane.tsx packages/trace-viewer/src/ui/networkFilters.tsx — `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: NetworkObserver.js ↔ FrameTree.js browser_patches/firefox/juggler/NetworkObserver.js — `browser_patches/firefox/juggler/NetworkObserver.js` and `browser_patches/firefox/juggler/content/FrameTree.js` 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 `d0b1fc27` chore: roll browser patches (#38909); `01103405` chore: update browser patches to 09195c9 (#32877); `aa1862cd` chore: update browser patches as of Aug, 1 2023 (#27005) — run `git show` on any of them.
Change coupling: pdf.ts ↔ response.ts packages/playwright-core/src/tools/backend/pdf.ts — `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: REDACTED ↔ wkPage.ts REDACTED — `REDACTED` and `packages/playwright-core/src/server/webkit/wkPage.ts` change together 54% of the time (56 of the 104 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 56 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: ffNetworkManager.ts ↔ wkInterceptableRequest.ts packages/playwright-core/src/server/firefox/ffNetworkManager.ts — `packages/playwright-core/src/server/firefox/ffNetworkManager.ts` and `packages/playwright-core/src/server/webkit/wkInterceptableRequest.ts` change together 54% of the time (7 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 7 shared commits counted here, the most recent 3 are `1ac9a570` feat(har): include `WebSocket` in `.har` (#41015); `73f6cf9a` chore: normalize resource types (#38480); `5271fe1f` chore: remove unused request param from route.continue (#32307) — run `git show` on any of them.
Change coupling: snapshot.ts ↔ tab.ts packages/playwright-core/src/tools/backend/snapshot.ts — `packages/playwright-core/src/tools/backend/snapshot.ts` and `packages/playwright-core/src/tools/backend/tab.ts` change together 52% of the time (14 of the 27 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 14 shared commits counted here, the most recent 3 are `273c8aab` feat(mcp): support python, java and csharp in --codegen (#42106); `1b18f3bf` feat(aria-snapshot): add boxes option to include bounding boxes (#40389); `fb75e252` fix(cli): resolve refs for snapshot command (#40114) — run `git show` on any of them.
Change coupling: testCaseView.tsx ↔ testFileView.tsx packages/html-reporter/src/testCaseView.tsx — `packages/html-reporter/src/testCaseView.tsx` and `packages/html-reporter/src/testFileView.tsx` change together 50% of the time (15 of the 30 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 15 shared commits counted here, the most recent 3 are `f00452c6` chore: deduplicate msToString and bytesToString into isomorphic/forma…; `5d5b28f7` feat(html): show the list of runs from the same worker (#39103); `d92591a9` fix(ui): dont mutate searchparams (#38275) — run `git show` on any of them.
Change coupling: workerHost.ts ↔ workerMain.ts packages/playwright/src/runner/workerHost.ts — `packages/playwright/src/runner/workerHost.ts` and `packages/playwright/src/worker/workerMain.ts` 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `86b465c0` chore: merge agent cache from workers (#38500); `34a09f37` chore: remove mdb, replace by `sendMessage` ipc into test worker (#38…; `d669fcde` chore: step error recovery framework (#36996) — run `git show` on any of them.
Change coupling: clock.ts ↔ browserContextDispatcher.ts packages/playwright-core/src/server/clock.ts — `packages/playwright-core/src/server/clock.ts` and `packages/playwright-core/src/server/dispatchers/browserContextDispatcher.ts` change together 50% of the time (9 of the 18 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 `ff6d41b3` chore: enforce dispatcher API convention for server types (4) (#40037); `c2763fe7` feat: clock.uninstall (#36856); `e4355f72` chore: migrate some dispatchers from CallMetadata to Progress (part 3… — run `git show` on any of them.
Change coupling: filmStrip.tsx ↔ workbench.tsx packages/trace-viewer/src/ui/filmStrip.tsx — `packages/trace-viewer/src/ui/filmStrip.tsx` and `packages/trace-viewer/src/ui/workbench.tsx` 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 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 `0ee695b5` feat(trace-viewer): show screencast frames during playback (#42751); `51023b42` chore(trace-viewer): show only the screencast frame on timeline hover…; `ea3fab65` chore(trace): pass trace param to sha1 requests (#37788) — run `git show` on any of them.
+ 2 more in this group — see findings.md.

D3 · God Classes · FunctionTooLong · ×26

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: 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 packages/dashboard/src/dashboard.tsx: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 packages/isomorphic/trace/snapshotRenderer.ts:322 — 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:687 — FunctionTooLong — getTextAlternativeInternal runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: program.decorateProgram packages/playwright-core/src/cli/program.ts:37 — 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: program.program packages/playwright-core/src/tools/cli-client/program.ts:77 — FunctionTooLong — program runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× 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: check_deps.innerCheckDeps utils/check_deps.js:62 — 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: generateDotnetApi.renderMethod utils/doclint/generateDotnetApi.js:489 — 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: 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: program.decorateMCPCommand packages/playwright-core/src/tools/mcp/program.ts:34 — FunctionTooLong — decorateMCPCommand runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× 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:57 — FunctionTooLong — inject runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× 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: connect.ConnectApp packages/extension/src/ui/connect.tsx:39 — FunctionTooLong — ConnectApp runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
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.
FunctionTooLong: sessionSidebar.SessionSidebar packages/dashboard/src/sessionSidebar.tsx:79 — FunctionTooLong — SessionSidebar runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: utilityScriptSerializers.innerSerialize packages/isomorphic/utilityScriptSerializers.ts:253 — FunctionTooLong — innerSerialize 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.
+ 1 more in this group — see findings.md.

D31 · IaC & Container Security · Medium IaC · ×18

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

D3 · God Classes · ClassTooLong · ×14

ClassTooLong: InjectedScript packages/injected/src/injectedScript.ts:92 — ClassTooLong — 1161 significant lines (blank, comment-only and punctuation-only lines excluded), 77 methods. The bar is 400 significant lines; this is 761 over it, 2.90× 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:513 — ClassTooLong — 960 significant lines (blank, comment-only and punctuation-only lines excluded), 102 methods. The bar is 400 significant lines; this is 560 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.
ClassTooLong: WKPage packages/playwright-core/src/server/webkit/wkPage.ts:56 — ClassTooLong — 849 significant lines (blank, comment-only and punctuation-only lines excluded), 92 methods. The bar is 400 significant lines; this is 449 over it, 2.12× 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 — 820 significant lines (blank, comment-only and punctuation-only lines excluded), 90 methods. The bar is 400 significant lines; this is 420 over it, 2.05× 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 — 629 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 229 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.
ClassTooLong: ElementHandle packages/playwright-core/src/server/dom.ts:121 — ClassTooLong — 600 significant lines (blank, comment-only and punctuation-only lines excluded), 71 methods. The bar is 400 significant lines; this is 200 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.
ClassTooLong: Page packages/playwright-core/src/client/page.ts:89 — ClassTooLong — 560 significant lines (blank, comment-only and punctuation-only lines excluded), 124 methods. The bar is 400 significant lines; this is 160 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: Page packages/playwright-core/src/server/page.ts:166 — ClassTooLong — 560 significant lines (blank, comment-only and punctuation-only lines excluded), 75 methods. The bar is 400 significant lines; this is 160 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: FrameSession REDACTED:400 — ClassTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 154 over it, 1.39× 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 — 523 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 123 over it, 1.31× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BidiPage packages/playwright-core/src/server/bidi/bidiPage.ts:45 — ClassTooLong — 492 significant lines (blank, comment-only and punctuation-only lines excluded), 61 methods. The bar is 400 significant lines; this is 92 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HarTracer packages/playwright-core/src/server/har/harTracer.ts:66 — 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 packages/playwright-core/src/server/browserContext.ts:90 — ClassTooLong — 472 significant lines (blank, comment-only and punctuation-only lines excluded), 74 methods. The bar is 400 significant lines; this is 72 over it, 1.18× 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:102 — ClassTooLong — 407 significant lines (blank, comment-only and punctuation-only lines excluded), 21 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.

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

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: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:third-party-deep-import] packages/playwright-core/src/server/bidi/bidiOverCdp.ts:17 — packages/playwright-core/src/server/bidi/bidiOverCdp.ts:17 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:18 — packages/playwright-core/src/server/bidi/bidiOverCdp.ts:18 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:test-cross-package-internals] tests/extension/extension-fixtures.ts:148 — tests/extension/extension-fixtures.ts:148 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/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.

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

Repeated repair: packages/playwright-core/src/tools/mcp/extensionContextFactory.ts packages/playwright-core/src/tools/mcp/extensionContextFactory.ts:29 — packages/playwright-core/src/tools/mcp/extensionContextFactory.ts changed 7 times in last 90 days and 6 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 extensionContextFactory.createExtensionBrowser at line 29), 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): honor --user-data-dir in extension mode (#42190)”; “fix(mcp): mention PLAYWRIGHT_MCP_EXECUTABLE_PATH in extension not found error (#42122)”; “fix(mcp): pass noDefaults for extension CDP connections (#42119)”; “fix(mcp): validate Host and Origin on CDP relay WebSocket upgrades (#42103)”. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/playwright-core/src/tools/mcp/extensionContextFactory.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/browserFactory.ts packages/playwright-core/src/tools/mcp/browserFactory.ts:186 — packages/playwright-core/src/tools/mcp/browserFactory.ts changed 9 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 8 (its worst body is browserFactory.createPersistentBrowser at line 186), 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)”; “fix(mcp): report the actual remote browser name in browserInfo (#42228)”; “fix(mcp): honor --user-data-dir in extension mode (#42190)”; “fix(registry): evaluate `defaultCacheDirectory` lazily (#41942)”. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/playwright-core/src/tools/mcp/browserFactory.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/cdpRelay.ts packages/playwright-core/src/tools/mcp/cdpRelay.ts:148 — packages/playwright-core/src/tools/mcp/cdpRelay.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 CDPRelayServer._openConnectPageInBrowser at line 148), 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): time out extension connection when a token is passed (#42525)”; “fix(mcp): honor --user-data-dir in extension mode (#42190)”; “fix(mcp): validate Host and Origin on CDP relay WebSocket upgrades (#42103)”; “fix(mcp): reconnect to the browser after disconnect (#41966)”. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/playwright-core/src/tools/mcp/cdpRelay.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 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 3 (its worst body is index.createConnection at line 29), 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)”; “fix(mcp): wait for client event stream before server->client requests (#41559)”. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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/playwright-core/src/server/browser.ts packages/playwright-core/src/server/browser.ts:105 — 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 105), 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): respect launch proxy and proxy.bypass (#42873)”; “fix(chromium): replay execution contexts when connecting to Android WebView (#42447)”; “fix(mcp): validate Host and Origin on CDP relay WebSocket upgrades (#42103)”. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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/chromium/chromiumSwitches.ts packages/playwright-core/src/server/chromium/chromiumSwitches.ts:56 — packages/playwright-core/src/server/chromium/chromiumSwitches.ts changed 3 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 chromiumSwitches.chromiumSwitches at line 56), 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): disable more background requests to Google services (#42909)”; “fix(chromium): stop disabling BoundaryEventDispatchTracksNodeRemoval (#42294)”; “fix(chromium): disable BlockOriginHeaderModificationOnRedirect (#41696)”. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07: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/playwright-core/src/tools/utils/mcp/http.ts packages/playwright-core/src/tools/utils/mcp/http.ts:61 — packages/playwright-core/src/tools/utils/mcp/http.ts changed 3 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 http.installHttpTransport at line 61), 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 run heartbeat for clients without the event stream (#42189)”; “fix(mcp): only enable /killkillkill under test (#42133)”; “fix(mcp): wait for client event stream before server->client requests (#41559)”. 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-06-27..2026-09-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-27 17:39:27 -07:00' --until='2026-09-25 17:39:27 -07:00' --full-history --no-merges -- packages/playwright-core/src/tools/utils/mcp/http.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.

D3 · God Classes · MethodTooLong · ×7

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:326 — MethodTooLong — _sendRequest runs 250 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 150 over it, 2.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.
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 packages/injected/src/injectedScript.ts:1518 — 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 packages/injected/src/injectedScript.ts: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 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
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.

R7 · Dead Code · Dead file (~21 LoC) · ×5

Dead file (~21 LoC) packages/html-reporter/src/testFileView.story.tsx — no import path from any entry point (269 application, 82 tooling, 811 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 (269 application, 82 tooling, 811 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 (269 application, 82 tooling, 811 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 (269 application, 82 tooling, 811 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 (269 application, 82 tooling, 811 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

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

REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Medium CVE · ×4

REDACTED
REDACTED
REDACTED
REDACTED

R4 · Test Coverage · This test file cannot be loaded · ×4

This test file cannot be loaded tests/config/proxy.ts — tests/config/proxy.ts:19 imports '../third_party/proxy', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded tests/library/browsercontext-har.spec.ts — tests/library/browsercontext-har.spec.ts:20 imports '../../packages/utils/third_party/extractZip', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded tests/library/trace-viewer.spec.ts — tests/library/trace-viewer.spec.ts:22 imports '../../packages/utils/third_party/extractZip', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded tests/playwright-test/reporter-blob.spec.ts — tests/playwright-test/reporter-blob.spec.ts:21 imports '../../packages/utils/third_party/extractZip', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.

D2 · Cognitive Complexity · innerCheckDeps · ×3

innerCheckDeps::visit (cognitive 54) utils/check_deps.js:134 — 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.
innerCheckDeps::calculateDeps (cognitive 18) utils/check_deps.js:207 — 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.
innerCheckDeps::allowImport (cognitive 17) utils/check_deps.js:244 — 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.

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

REDACTED
REDACTED
REDACTED

D35 · Change Coupling · Change-coupling hub · ×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: PageHandler.js → FrameTree.js, PageAgent.js, main.js, Protocol.js browser_patches/firefox/juggler/protocol/PageHandler.js — `browser_patches/firefox/juggler/protocol/PageHandler.js` changes together with 4 other files — `browser_patches/firefox/juggler/content/FrameTree.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: 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.

R7 · Dead Code · Dead file (~24 LoC) · ×3

Dead file (~24 LoC) packages/playwright-client/src/nodeStubs/crypto.ts — no import path from any entry point (269 application, 82 tooling, 811 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 (269 application, 82 tooling, 811 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 (269 application, 82 tooling, 811 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

AC1 · Text alternatives · <video> without a captions track · ×2

<video> without a captions track packages/dashboard/src/recording.tsx:53 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
<video> without a captions track packages/html-reporter/src/testResultView.tsx:190 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).

D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 22) · ×2

(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.
(anonymous) (cyclomatic 22) utils/linux-browser-dependencies/inside_docker/list_dependencies.js:27 — (anonymous) has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to 13 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.

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

REDACTED
REDACTED

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

Duplicated block (40 lines × 2 locations) browser_patches/firefox/juggler/NetworkObserver.js:832 — browser_patches/firefox/juggler/NetworkObserver.js:832 · packages/playwright-core/src/server/network.ts:59 — 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.

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

Dead file (~170 LoC) packages/html-reporter/src/sampleReport.ts — no import path from any entry point (269 application, 82 tooling, 811 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 (~170 LoC) utils/doclint/linkUtils.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (utils/generate_types/index.js, utils/render_release_notes.mjs) — 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

AC3 · Page structure · Page without a main landmark · ×1

Page without a main landmark packages/trace-viewer/index.html:17 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.

AC3 · Page structure · Data table has no header cells · ×1

Data table has no header cells packages/trace-viewer/src/ui/networkResourceDetails.tsx:150 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).

AC4 · Keyboard semantics · Link used as a button (placeholder href) · ×1

Link used as a button (placeholder href) packages/trace-viewer/src/ui/uiModeView.tsx:461 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.

AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.0 · ×1

Low contrast colour pair in CSS (3.0:1) packages/trace-viewer/src/ui/tag.css:17 — `* you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ .tag` sets color: white on background-color: #8c959f — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.

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

Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 101 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

D1 · Cyclomatic Complexity · snapshotterInjected.frameSnapshotStreamer (cyclomatic 146) · ×1

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, 39 points are the body's own statements and 107 belong to 12 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · cssTokenizer.tokenize (cyclomatic 143) · ×1

cssTokenizer.tokenize (cyclomatic 143) packages/isomorphic/cssTokenizer.ts:77 — cssTokenizer.tokenize has cyclomatic complexity 143 (threshold 15). Most of this is not in the body itself: 3 of the 143 points are its own statements and the rest belongs to 18 function literals inside it that branch (lines 143, 470, 342, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · roleUtils.getTextAlternativeInternal (cyclomatic 138) · ×1

roleUtils.getTextAlternativeInternal (cyclomatic 138) packages/injected/src/roleUtils.ts:687 — roleUtils.getTextAlternativeInternal has cyclomatic complexity 138 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Streamer.captureSnapshot (cyclomatic 106) · ×1

Streamer.captureSnapshot (cyclomatic 106) packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:367 — Streamer.captureSnapshot has cyclomatic complexity 106 (threshold 15). Most of this is not in the body itself: 8 of the 106 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 384, 455, 464, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · uiModeView.UIModeView (cyclomatic 88) · ×1

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.

D1 · Cyclomatic Complexity · generate_channels.generateChannels (cyclomatic 81) · ×1

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.

D1 · Cyclomatic Complexity · annotations.Annotations (cyclomatic 80) · ×1

annotations.Annotations (cyclomatic 80) packages/dashboard/src/annotations.tsx:137 — annotations.Annotations has cyclomatic complexity 80 (threshold 15). Of this number, 43 points are the body's own statements and 37 belong to 18 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · check_deps.innerCheckDeps (cyclomatic 78) · ×1

check_deps.innerCheckDeps (cyclomatic 78) utils/check_deps.js:62 — check_deps.innerCheckDeps has cyclomatic complexity 78 (threshold 15). Of this number, 76 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · selectorParser.parseAttributeSelector (cyclomatic 69) · ×1

selectorParser.parseAttributeSelector (cyclomatic 69) packages/isomorphic/selectorParser.ts:276 — selectorParser.parseAttributeSelector has cyclomatic complexity 69 (threshold 15). Of this number, 66 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · dashboard.Dashboard (cyclomatic 68) · ×1

dashboard.Dashboard (cyclomatic 68) packages/dashboard/src/dashboard.tsx:67 — dashboard.Dashboard has cyclomatic complexity 68 (threshold 15). Of this number, 50 points are the body's own statements and 18 belong to 13 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · APIRequestContext._sendRequest (cyclomatic 65) · ×1

APIRequestContext._sendRequest (cyclomatic 65) packages/playwright-core/src/server/fetch.ts:326 — APIRequestContext._sendRequest has cyclomatic complexity 65 (threshold 15). Most of this is not in the body itself: 4 of the 65 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 392, 396, 353, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · webSocketMock.inject (cyclomatic 61) · ×1

webSocketMock.inject (cyclomatic 61) packages/injected/src/webSocketMock.ts:38 — webSocketMock.inject has cyclomatic complexity 61 (threshold 15). Of this number, 51 points are the body's own statements and 10 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.

D1 · Cyclomatic Complexity · cssParser.parseCSS (cyclomatic 59) · ×1

cssParser.parseCSS (cyclomatic 59) packages/isomorphic/cssParser.ts:39 — cssParser.parseCSS has cyclomatic complexity 59 (threshold 15). Of this number, 49 points are the body's own statements and 10 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.

D1 · Cyclomatic Complexity · generateDotnetApi.renderMethod (cyclomatic 58) · ×1

generateDotnetApi.renderMethod (cyclomatic 58) utils/doclint/generateDotnetApi.js:489 — generateDotnetApi.renderMethod has cyclomatic complexity 58 (threshold 15). Of this number, 45 points are the body's own statements and 13 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InjectedScript.expectSingleElement (cyclomatic 57) · ×1

InjectedScript.expectSingleElement (cyclomatic 57) packages/injected/src/injectedScript.ts:1518 — 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.

D1 · Cyclomatic Complexity · program.program (cyclomatic 57) · ×1

program.program (cyclomatic 57) packages/playwright-core/src/tools/cli-client/program.ts:77 — program.program has cyclomatic complexity 57 (threshold 15). Of this number, 55 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.

D1 · Cyclomatic Complexity · ansi2html.ansi2html (cyclomatic 56) · ×1

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.

D1 · Cyclomatic Complexity · snapshotRenderer.snapshotScript (cyclomatic 55) · ×1

snapshotRenderer.snapshotScript (cyclomatic 55) packages/isomorphic/trace/snapshotRenderer.ts:322 — snapshotRenderer.snapshotScript has cyclomatic complexity 55 (threshold 15). Most of this is not in the body itself: 3 of the 55 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 357, 473, 553, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · ariaSnapshot.generateAriaTree (cyclomatic 52) · ×1

ariaSnapshot.generateAriaTree (cyclomatic 52) packages/injected/src/ariaSnapshot.ts:81 — ariaSnapshot.generateAriaTree has cyclomatic complexity 52 (threshold 15). Of this number, 23 points are the body's own statements and 29 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.

D1 · Cyclomatic Complexity · cli.run (cyclomatic 47) · ×1

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.

D1 · Cyclomatic Complexity · innerRenderMdNode (cyclomatic 47) · ×1

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.

D1 · Cyclomatic Complexity · locatorGenerators.innerAsLocators (cyclomatic 46) · ×1

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.

D1 · Cyclomatic Complexity · SnapshotRenderer.render (cyclomatic 46) · ×1

SnapshotRenderer.render (cyclomatic 46) packages/isomorphic/trace/snapshotRenderer.ts:87 — SnapshotRenderer.render has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 1 of the 46 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 89, 195). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · recorder.Recorder (cyclomatic 46) · ×1

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.

D1 · Cyclomatic Complexity · workbench.PartitionedWorkbench (cyclomatic 45) · ×1

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.

D1 · Cyclomatic Complexity · ariaSnapshot.parseAriaSnapshot (cyclomatic 44) · ×1

ariaSnapshot.parseAriaSnapshot (cyclomatic 44) packages/isomorphic/ariaSnapshot.ts:131 — ariaSnapshot.parseAriaSnapshot has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 9 of the 44 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 175, 152). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · utilityScriptSerializers.innerSerialize (cyclomatic 44) · ×1

utilityScriptSerializers.innerSerialize (cyclomatic 44) packages/isomorphic/utilityScriptSerializers.ts:253 — utilityScriptSerializers.innerSerialize has cyclomatic complexity 44 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · ariaSnapshotRenderer.renderAriaSnapshotAsYaml (cyclomatic 43) · ×1

ariaSnapshotRenderer.renderAriaSnapshotAsYaml (cyclomatic 43) packages/isomorphic/ariaSnapshotRenderer.ts:27 — ariaSnapshotRenderer.renderAriaSnapshotAsYaml has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 4 of the 43 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 38, 83, 32). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · generateDotnetApi.translateType (cyclomatic 42) · ×1

generateDotnetApi.translateType (cyclomatic 42) utils/doclint/generateDotnetApi.js:709 — 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.

D1 · Cyclomatic Complexity · JavaLocatorFactory.generateLocator (cyclomatic 40) · ×1

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.

D1 · Cyclomatic Complexity · PythonLocatorFactory.generateLocator (cyclomatic 39) · ×1

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.

D1 · Cyclomatic Complexity · APIRequestContext._innerFetch (cyclomatic 39) · ×1

APIRequestContext._innerFetch (cyclomatic 39) packages/playwright-core/src/client/fetch.ts:179 — APIRequestContext._innerFetch 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 one function literal inside it that branches (line 180). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · FrameSession._initialize (cyclomatic 39) · ×1

FrameSession._initialize (cyclomatic 39) REDACTED:472 — FrameSession._initialize has cyclomatic complexity 39 (threshold 15). Of this number, 31 points are the body's own statements and 8 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.

D1 · Cyclomatic Complexity · consoleTab.useConsoleTabModel (cyclomatic 39) · ×1

consoleTab.useConsoleTabModel (cyclomatic 39) REDACTED:64 — consoleTab.useConsoleTabModel 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 6 function literals inside it that branch (lines 65, 68, 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.

D1 · Cyclomatic Complexity · codeMirrorWrapper.CodeMirrorWrapper (cyclomatic 39) · ×1

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.

D1 · Cyclomatic Complexity · minimist.minimist (cyclomatic 38) · ×1

minimist.minimist (cyclomatic 38) packages/playwright-core/src/tools/cli-client/minimist.ts:36 — minimist.minimist has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · JavaScriptLocatorFactory.generateLocator (cyclomatic 37) · ×1

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.

D1 · Cyclomatic Complexity · CSharpLocatorFactory.generateLocator (cyclomatic 37) · ×1

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.

D1 · Cyclomatic Complexity · CRNetworkManager._onRequest (cyclomatic 37) · ×1

CRNetworkManager._onRequest (cyclomatic 37) packages/playwright-core/src/server/chromium/crNetworkManager.ts:282 — 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.

D1 · Cyclomatic Complexity · bidiExecutionContext.renderPreview (cyclomatic 37) · ×1

bidiExecutionContext.renderPreview (cyclomatic 37) packages/playwright-core/src/server/bidi/bidiExecutionContext.ts: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.

D1 · Cyclomatic Complexity · workbenchLoader.WorkbenchLoader (cyclomatic 37) · ×1

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

D1 · Cyclomatic Complexity · treeView.TreeView (cyclomatic 37) · ×1

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.

D1 · Cyclomatic Complexity · dashboard_compressed_v1.compressReports (cyclomatic 37) · ×1

dashboard_compressed_v1.compressReports (cyclomatic 37) utils/flakiness-dashboard/processing/dashboard_compressed_v1.js:33 — dashboard_compressed_v1.compressReports 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.

D1 · Cyclomatic Complexity · ariaSnapshot.matchesNode (cyclomatic 36) · ×1

ariaSnapshot.matchesNode (cyclomatic 36) packages/injected/src/ariaSnapshot.ts:377 — 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.

D1 · Cyclomatic Complexity · ariaSnapshot.renderAriaTreeAsJSON (cyclomatic 36) · ×1

ariaSnapshot.renderAriaTreeAsJSON (cyclomatic 36) packages/injected/src/ariaSnapshot.ts:464 — ariaSnapshot.renderAriaTreeAsJSON has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 4 of the 36 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 468, 516). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · ElementHandle._performPointerAction (cyclomatic 36) · ×1

ElementHandle._performPointerAction (cyclomatic 36) packages/playwright-core/src/server/dom.ts:391 — 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 literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · TraceModernizer._innerAppendEvent (cyclomatic 34) · ×1

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.

D1 · Cyclomatic Complexity · splitView.SplitView (cyclomatic 34) · ×1

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.

D1 · Cyclomatic Complexity · roleSelectorEngine.queryRole (cyclomatic 33) · ×1

roleSelectorEngine.queryRole (cyclomatic 33) packages/injected/src/roleSelectorEngine.ts:143 — roleSelectorEngine.queryRole has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 145, 190). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · selectorGenerator.buildTextCandidates (cyclomatic 33) · ×1

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.

D1 · Cyclomatic Complexity · hostPlatform.calculatePlatform (cyclomatic 33) · ×1

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.

D1 · Cyclomatic Complexity · Page.expectScreenshot (cyclomatic 32) · ×1

Page.expectScreenshot (cyclomatic 32) packages/playwright-core/src/server/page.ts:717 — 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 literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · browserActions.launchContext (cyclomatic 32) · ×1

browserActions.launchContext (cyclomatic 32) packages/playwright-core/src/cli/browserActions.ts:65 — browserActions.launchContext has cyclomatic complexity 32 (threshold 15). Of this number, 31 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · timeline.Timeline (cyclomatic 32) · ×1

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.

D1 · Cyclomatic Complexity · imageDiffView.ImageDiffView (cyclomatic 32) · ×1

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 literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · reportView.ReportView (cyclomatic 31) · ×1

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.

D1 · Cyclomatic Complexity · selectorGenerator.generateSelectorFor (cyclomatic 31) · ×1

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 literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · webAuthn.inject (cyclomatic 31) · ×1

webAuthn.inject (cyclomatic 31) packages/injected/src/webAuthn.ts:57 — webAuthn.inject has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · Response._build (cyclomatic 31) · ×1

Response._build (cyclomatic 31) packages/playwright-core/src/tools/backend/response.ts:267 — Response._build 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.

D1 · Cyclomatic Complexity · playbackControl.usePlayback (cyclomatic 31) · ×1

playbackControl.usePlayback (cyclomatic 31) packages/trace-viewer/src/ui/playbackControl.tsx:48 — playbackControl.usePlayback has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 11 of the 31 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 150, 124, 205, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · utilityScriptSerializers.parseEvaluationResultValue (cyclomatic 30) · ×1

utilityScriptSerializers.parseEvaluationResultValue (cyclomatic 30) packages/isomorphic/utilityScriptSerializers.ts: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.

D1 · Cyclomatic Complexity · Frame._expectInternal (cyclomatic 30) · ×1

Frame._expectInternal (cyclomatic 30) packages/playwright-core/src/server/frames.ts:1530 — 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.

D1 · Cyclomatic Complexity · traceConsole.traceConsole (cyclomatic 30) · ×1

traceConsole.traceConsole (cyclomatic 30) packages/playwright-core/src/tools/trace/traceConsole.ts: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.

D1 · Cyclomatic Complexity · serializers.innerSerializeValue (cyclomatic 30) · ×1

serializers.innerSerializeValue (cyclomatic 30) packages/protocol/src/serializers.ts:156 — serializers.innerSerializeValue has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · ExecutionContext._createRemoteObject (cyclomatic 29) · ×1

ExecutionContext._createRemoteObject (cyclomatic 29) browser_patches/firefox/juggler/content/Runtime.js:460 — 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.

D1 · Cyclomatic Complexity · selectorGenerator.buildNoTextCandidates (cyclomatic 29) · ×1

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.

D1 · Cyclomatic Complexity · serializers.innerParseSerializedValue (cyclomatic 29) · ×1

serializers.innerParseSerializedValue (cyclomatic 29) packages/protocol/src/serializers.ts:58 — serializers.innerParseSerializedValue has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · generateNameDefault (cyclomatic 29) · ×1

generateNameDefault (cyclomatic 29) utils/doclint/generateDotnetApi.js:391 — 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.

D1 · Cyclomatic Complexity · InjectedScript.elementState (cyclomatic 28) · ×1

InjectedScript.elementState (cyclomatic 28) packages/injected/src/injectedScript.ts:783 — InjectedScript.elementState 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.

D1 · Cyclomatic Complexity · selectorParser.parseSelectorString (cyclomatic 28) · ×1

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 literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · JavaScriptLanguageGenerator._generateActionCall (cyclomatic 28) · ×1

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.

D1 · Cyclomatic Complexity · jsonSchema.validate (cyclomatic 28) · ×1

jsonSchema.validate (cyclomatic 28) packages/isomorphic/jsonSchema.ts: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.

D1 · Cyclomatic Complexity · traceRequests.traceRequest (cyclomatic 28) · ×1

traceRequests.traceRequest (cyclomatic 28) packages/playwright-core/src/tools/trace/traceRequests.ts: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.

D1 · Cyclomatic Complexity · main.doFetch (cyclomatic 28) · ×1

main.doFetch (cyclomatic 28) packages/trace-viewer/src/sw/main.ts: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.

D1 · Cyclomatic Complexity · listView.ListView (cyclomatic 28) · ×1

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.

D1 · Cyclomatic Complexity · roleSelectorEngine.validateAttributes (cyclomatic 27) · ×1

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.

D1 · Cyclomatic Complexity · WVPage._onConsoleMessage (cyclomatic 27) · ×1

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.

D1 · Cyclomatic Complexity · innerCheckDeps · ×1

innerCheckDeps::visit (cyclomatic 27) utils/check_deps.js:134 — 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.

D1 · Cyclomatic Complexity · TargetRegistry.constructor (cyclomatic 26) · ×1

TargetRegistry.constructor (cyclomatic 26) browser_patches/firefox/juggler/TargetRegistry.js:115 — 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 literals inside it that branch (lines 185, 152, 220, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · ariaSnapshot.toAriaNode (cyclomatic 26) · ×1

ariaSnapshot.toAriaNode (cyclomatic 26) packages/injected/src/ariaSnapshot.ts:235 — 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.

D1 · Cyclomatic Complexity · KeyParser._applyAttribute (cyclomatic 26) · ×1

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.

D1 · Cyclomatic Complexity · TraceModel.constructor (cyclomatic 26) · ×1

TraceModel.constructor (cyclomatic 26) packages/isomorphic/trace/traceModel.ts:98 — TraceModel.constructor has cyclomatic complexity 26 (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.

D1 · Cyclomatic Complexity · screenshotter.inPagePrepareForScreenshots (cyclomatic 26) · ×1

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

D1 · Cyclomatic Complexity · Frame.waitForSelector (cyclomatic 26) · ×1

Frame.waitForSelector (cyclomatic 26) packages/playwright-core/src/server/frames.ts:836 — 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 846, 853). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · PlaywrightServer.constructor (cyclomatic 26) · ×1

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.

D1 · Cyclomatic Complexity · InjectedScript.dispatchEvent (cyclomatic 25) · ×1

InjectedScript.dispatchEvent (cyclomatic 25) packages/injected/src/injectedScript.ts:1205 — 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 literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · markdown.buildTree (cyclomatic 25) · ×1

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 literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · index.jsonToTS (cyclomatic 25) · ×1

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.

D1 · Cyclomatic Complexity · Filter.matches (cyclomatic 24) · ×1

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.

D1 · Cyclomatic Complexity · injectedScript.createTextMatcher (cyclomatic 24) · ×1

injectedScript.createTextMatcher (cyclomatic 24) packages/injected/src/injectedScript.ts:1780 — 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 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.

D1 · Cyclomatic Complexity · JavaLanguageGenerator._generateActionCall (cyclomatic 24) · ×1

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.

D1 · Cyclomatic Complexity · BrowserContextDispatcher.constructor (cyclomatic 24) · ×1

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.

D1 · Cyclomatic Complexity · processLauncher.launchProcess (cyclomatic 24) · ×1

processLauncher.launchProcess (cyclomatic 24) REDACTED:133 — processLauncher.launchProcess has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · debuggerPanel.DebuggerPanel (cyclomatic 23) · ×1

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.

D1 · Cyclomatic Complexity · SelectorEvaluatorImpl._matchesParents (cyclomatic 23) · ×1

SelectorEvaluatorImpl._matchesParents (cyclomatic 23) packages/injected/src/selectorEvaluator.ts: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.

D1 · Cyclomatic Complexity · InjectedScript.expectHitTarget (cyclomatic 23) · ×1

InjectedScript.expectHitTarget (cyclomatic 23) packages/injected/src/injectedScript.ts:1023 — 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.

D1 · Cyclomatic Complexity · injectedScript.deepEquals (cyclomatic 23) · ×1

injectedScript.deepEquals (cyclomatic 23) packages/injected/src/injectedScript.ts:1877 — 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.

D1 · Cyclomatic Complexity · selectorParser.parseSelector (cyclomatic 23) · ×1

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.

D1 · Cyclomatic Complexity · CSharpLanguageGenerator._generateActionCall (cyclomatic 23) · ×1

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.

D1 · Cyclomatic Complexity · PythonLanguageGenerator._generateActionCall (cyclomatic 23) · ×1

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.

D1 · Cyclomatic Complexity · TraceModernizer._modernize_8_to_9 (cyclomatic 23) · ×1

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.

D1 · Cyclomatic Complexity · TraceLoader.load (cyclomatic 23) · ×1

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.

D1 · Cyclomatic Complexity · FrameSelectors._callOnSelectorInternal (cyclomatic 23) · ×1

FrameSelectors._callOnSelectorInternal (cyclomatic 23) packages/playwright-core/src/server/frameSelectors.ts:243 — 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 literals inside it that branch (lines 261, 258, 285). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · cookieStore.parseRawCookie (cyclomatic 23) · ×1

cookieStore.parseRawCookie (cyclomatic 23) packages/playwright-core/src/server/cookieStore.ts:131 — cookieStore.parseRawCookie 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.

D1 · Cyclomatic Complexity · HarTracer._onRequestFinished (cyclomatic 23) · ×1

HarTracer._onRequestFinished (cyclomatic 23) packages/playwright-core/src/server/har/harTracer.ts:327 — HarTracer._onRequestFinished has cyclomatic complexity 23 (threshold 15). Of this number, 15 points are the body's own statements and 8 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · HarTracer._onWebSocket (cyclomatic 23) · ×1

HarTracer._onWebSocket (cyclomatic 23) packages/playwright-core/src/server/har/harTracer.ts:444 — 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 literals inside it that branch (lines 459, 475, 511, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · HarBackend._harFindResponse (cyclomatic 23) · ×1

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.

D1 · Cyclomatic Complexity · Response.serialize (cyclomatic 23) · ×1

Response.serialize (cyclomatic 23) packages/playwright-core/src/tools/backend/response.ts:172 — 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.

D1 · Cyclomatic Complexity · roleUtils.innerAccumulatedElementText (cyclomatic 22) · ×1

roleUtils.innerAccumulatedElementText (cyclomatic 22) packages/injected/src/roleUtils.ts:1018 — roleUtils.innerAccumulatedElementText has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · Registry.constructor (cyclomatic 22) · ×1

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 literals inside it that branch (lines 516, 747, 512, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · Chromium.launchWithSeleniumHub (cyclomatic 22) · ×1

Chromium.launchWithSeleniumHub (cyclomatic 22) packages/playwright-core/src/server/chromium/chromium.ts:251 — 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.

D1 · Cyclomatic Complexity · consoleTab.format (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · stackTrace.parseStackFrame (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · parseMember (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · selectorGenerator.cssEscapeCharacter (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · WebKit.defaultArgs (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · TextOutput.list (cyclomatic 21) · ×1

TextOutput.list (cyclomatic 21) packages/playwright-core/src/tools/cli-client/output.ts:135 — 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.

D1 · Cyclomatic Complexity · config.resolveCLIConfigForCLI (cyclomatic 21) · ×1

config.resolveCLIConfigForCLI (cyclomatic 21) packages/playwright-core/src/tools/mcp/config.ts:158 — config.resolveCLIConfigForCLI 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.

D1 · Cyclomatic Complexity · config.configFromCLIOptions (cyclomatic 21) · ×1

config.configFromCLIOptions (cyclomatic 21) packages/playwright-core/src/tools/mcp/config.ts:300 — config.configFromCLIOptions 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.

D1 · Cyclomatic Complexity · callTab.propertyToString (cyclomatic 21) · ×1

callTab.propertyToString (cyclomatic 21) packages/trace-viewer/src/ui/callTab.tsx: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.

D1 · Cyclomatic Complexity · resizeView.ResizeView (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · markdown.flattenWrappedLines (cyclomatic 21) · ×1

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.

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

parseOverrides.parseOverrides (cyclomatic 21) utils/generate_types/parseOverrides.js:26 — parseOverrides.parseOverrides 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.

D1 · Cyclomatic Complexity · TypesGenerator.stringifySimpleType (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · sessionSidebar.SessionSidebar (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · RecordActionTool._shouldGenerateKeyPressFor (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · JsonRecordActionTool._shouldGenerateKeyPressFor (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · istanbulCoverage.mergeIstanbulCoverage (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · locatorParser.tokenize (cyclomatic 20) · ×1

locatorParser.tokenize (cyclomatic 20) packages/isomorphic/locatorParser.ts:57 — locatorParser.tokenize has cyclomatic complexity 20 (threshold 15). Of this number, 12 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.

D1 · Cyclomatic Complexity · Frame.expect (cyclomatic 20) · ×1

Frame.expect (cyclomatic 20) packages/playwright-core/src/server/frames.ts:1468 — 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.

D1 · Cyclomatic Complexity · APIRequestContext.fetch (cyclomatic 20) · ×1

APIRequestContext.fetch (cyclomatic 20) packages/playwright-core/src/server/fetch.ts:193 — APIRequestContext.fetch 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.

D1 · Cyclomatic Complexity · browserContext.verifyClientCertificates (cyclomatic 20) · ×1

browserContext.verifyClientCertificates (cyclomatic 20) packages/playwright-core/src/server/browserContext.ts:809 — browserContext.verifyClientCertificates has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · config.validateBrowserConfig (cyclomatic 20) · ×1

config.validateBrowserConfig (cyclomatic 20) packages/playwright-core/src/tools/mcp/config.ts:224 — 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.

D1 · Cyclomatic Complexity · actionList.renderAction (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · ariaModeView.AriaModeView (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · sourceTab.useSources (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · build_deps_true.collectImports (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · api_parser.applyTemplates (cyclomatic 20) · ×1

api_parser.applyTemplates (cyclomatic 20) utils/doclint/api_parser.js:293 — api_parser.applyTemplates has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 298, 332). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · TypesGenerator.classBody (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · Helper.getNetworkErrorStatusText (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · connect.ConnectApp (cyclomatic 19) · ×1

connect.ConnectApp (cyclomatic 19) packages/extension/src/ui/connect.tsx:39 — connect.ConnectApp has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 50, 131, 123). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · InjectedScript.selectOptions (cyclomatic 19) · ×1

InjectedScript.selectOptions (cyclomatic 19) packages/injected/src/injectedScript.ts:843 — 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 literals inside it that branch (lines 856, 859). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · urlMatch.resolveGlobBase (cyclomatic 19) · ×1

urlMatch.resolveGlobBase (cyclomatic 19) packages/isomorphic/urlMatch.ts:214 — urlMatch.resolveGlobBase has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 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.

D1 · Cyclomatic Complexity · BidiConnection._dispatchMessage (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · BidiNetworkManager._onBeforeRequestSent (cyclomatic 19) · ×1

BidiNetworkManager._onBeforeRequestSent (cyclomatic 19) packages/playwright-core/src/server/bidi/bidiNetworkManager.ts:61 — 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.

D1 · Cyclomatic Complexity · ElementHandle._retryAction (cyclomatic 19) · ×1

ElementHandle._retryAction (cyclomatic 19) packages/playwright-core/src/server/dom.ts:317 — 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.

D1 · Cyclomatic Complexity · ElementHandle._setInputFiles (cyclomatic 19) · ×1

ElementHandle._setInputFiles (cyclomatic 19) packages/playwright-core/src/server/dom.ts:718 — ElementHandle._setInputFiles has cyclomatic complexity 19 (threshold 15). Of this number, 10 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.

D1 · Cyclomatic Complexity · attachmentsTab.AttachmentsTab (cyclomatic 19) · ×1

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.

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

_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 ((anonymous), handleListItem). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · selectorGenerator.cssFallback (cyclomatic 18) · ×1

selectorGenerator.cssFallback (cyclomatic 18) packages/injected/src/selectorGenerator.ts:359 — selectorGenerator.cssFallback has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InjectedScript.setupHitTargetInterceptor (cyclomatic 18) · ×1

InjectedScript.setupHitTargetInterceptor (cyclomatic 18) packages/injected/src/injectedScript.ts:1135 — 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 literals inside it that branch (lines 1162, 1188). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · Overlay.setUIState (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · selectorParser.splitSelectorByFrame (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · java.formatContextOptions (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · imageUtils.scaleImageToSize (cyclomatic 18) · ×1

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 literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · urlMatch.globToRegexPattern (cyclomatic 18) · ×1

urlMatch.globToRegexPattern (cyclomatic 18) packages/isomorphic/urlMatch.ts: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.

D1 · Cyclomatic Complexity · Route._innerFulfill (cyclomatic 18) · ×1

Route._innerFulfill (cyclomatic 18) packages/playwright-core/src/client/network.ts:373 — 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.

D1 · Cyclomatic Complexity · dependencies.validateDependenciesWindows (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · FFBrowserContext.initialize (cyclomatic 18) · ×1

FFBrowserContext.initialize (cyclomatic 18) packages/playwright-core/src/server/firefox/ffBrowser.ts:172 — FFBrowserContext.initialize has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · WKPage._onConsoleMessage (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · program.decorateMCPCommand (cyclomatic 18) · ×1

program.decorateMCPCommand (cyclomatic 18) packages/playwright-core/src/tools/mcp/program.ts:34 — program.decorateMCPCommand has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 113, 164, 88, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · callTab.parseSerializedValue (cyclomatic 18) · ×1

callTab.parseSerializedValue (cyclomatic 18) packages/trace-viewer/src/ui/callTab.tsx: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.

D1 · Cyclomatic Complexity · consoleTab.ConsoleTab (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · ariaModeView.collectAriaModeTargets (cyclomatic 18) · ×1

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 literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · snapshotTab.InspectModeController (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · socksProxy.parsePattern (cyclomatic 18) · ×1

socksProxy.parsePattern (cyclomatic 18) packages/utils/socksProxy.ts: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.

D1 · Cyclomatic Complexity · generateDotnetApi.renderMember (cyclomatic 18) · ×1

generateDotnetApi.renderMember (cyclomatic 18) utils/doclint/generateDotnetApi.js:315 — 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.

D1 · Cyclomatic Complexity · patchLinksInText (cyclomatic 18) · ×1

patchLinksInText (cyclomatic 18) utils/doclint/documentation.js:751 — patchLinksInText has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 752, 802, 784, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · selectorUtils.matchesAttributePart (cyclomatic 17) · ×1

selectorUtils.matchesAttributePart (cyclomatic 17) packages/injected/src/selectorUtils.ts:31 — 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.

D1 · Cyclomatic Complexity · selectorUtils.elementText (cyclomatic 17) · ×1

selectorUtils.elementText (cyclomatic 17) packages/injected/src/selectorUtils.ts:67 — 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.

D1 · Cyclomatic Complexity · InjectedScript.querySelectorAll (cyclomatic 17) · ×1

InjectedScript.querySelectorAll (cyclomatic 17) packages/injected/src/injectedScript.ts: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.

D1 · Cyclomatic Complexity · traceModel.adjustMonotonicTime (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · WebSocketTransport._connect (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · Frame.gotoImpl (cyclomatic 17) · ×1

Frame.gotoImpl (cyclomatic 17) packages/playwright-core/src/server/frames.ts:694 — 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 literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WKPage._initializeSessionMayThrow (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · localUtils.zip (cyclomatic 17) · ×1

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 literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · Connection.dispatch (cyclomatic 17) · ×1

Connection.dispatch (cyclomatic 17) packages/playwright-core/src/client/connection.ts:235 — 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.

D1 · Cyclomatic Complexity · treeView.TreeItemHeader (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · Type.fromParsedType (cyclomatic 17) · ×1

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

D1 · Cyclomatic Complexity · ApiParser.parseArgument (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · generate_dotnet_channels.processCustomType (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · create · ×1

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.

D1 · Cyclomatic Complexity · renderMethod · ×1

renderMethod::processArg (cyclomatic 17) utils/doclint/generateDotnetApi.js:570 — 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.

D1 · Cyclomatic Complexity · ExecutionContext.evaluateFunction (cyclomatic 16) · ×1

ExecutionContext.evaluateFunction (cyclomatic 16) browser_patches/firefox/juggler/content/Runtime.js:397 — 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.

D1 · Cyclomatic Complexity · PageHandler.['Page.dispatchMouseEvent'] (cyclomatic 16) · ×1

PageHandler.['Page.dispatchMouseEvent'] (cyclomatic 16) browser_patches/firefox/juggler/protocol/PageHandler.js:484 — 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 literals inside it that branch (lines 524, 486). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · roleUtils.parseCSSContentPropertyAsString (cyclomatic 16) · ×1

roleUtils.parseCSSContentPropertyAsString (cyclomatic 16) packages/injected/src/roleUtils.ts:441 — 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.

D1 · Cyclomatic Complexity · cssTokenizer.escapeIdent (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · JavaScriptLanguageGenerator.generateAction (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · traceModel.mergeActionsAndUpdateTimingSameTrace (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · EventEmitter.removeListener (cyclomatic 16) · ×1

EventEmitter.removeListener (cyclomatic 16) packages/playwright-core/src/client/eventEmitter.ts:185 — 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.

D1 · Cyclomatic Complexity · dependencies.validateDependenciesLinux (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · FrameSelectors._queryFrames (cyclomatic 16) · ×1

FrameSelectors._queryFrames (cyclomatic 16) packages/playwright-core/src/server/frameSelectors.ts:183 — 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 literals inside it that branch (lines 189, 187, 216). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · HarTracer._onResponse (cyclomatic 16) · ×1

HarTracer._onResponse (cyclomatic 16) packages/playwright-core/src/server/har/harTracer.ts:567 — 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.

D1 · Cyclomatic Complexity · input.buildLayoutClosure (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · CRBrowser._onAttachedToTarget (cyclomatic 16) · ×1

CRBrowser._onAttachedToTarget (cyclomatic 16) packages/playwright-core/src/server/chromium/crBrowser.ts:165 — CRBrowser._onAttachedToTarget 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.

D1 · Cyclomatic Complexity · BidiChromium._innerDefaultArgs (cyclomatic 16) · ×1

BidiChromium._innerDefaultArgs (cyclomatic 16) packages/playwright-core/src/server/bidi/bidiChromium.ts:105 — BidiChromium._innerDefaultArgs 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, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Connection.sendMessageToServer (cyclomatic 16) · ×1

Connection.sendMessageToServer (cyclomatic 16) packages/playwright-core/src/client/connection.ts:179 — 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.

D1 · Cyclomatic Complexity · installActions.installBrowsers (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · Session.startDaemon (cyclomatic 16) · ×1

Session.startDaemon (cyclomatic 16) packages/playwright-core/src/tools/cli-client/session.ts:114 — Session.startDaemon has cyclomatic complexity 16 (threshold 15). 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, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · snapshotTab.collectSnapshots (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · compare.compare (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · Member.filterForLanguage (cyclomatic 16) · ×1

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

D1 · Cyclomatic Complexity · generate_channels.inlineType (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · TypesGenerator.generateTypes (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · validate_deps.isEntryUsed (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · applyTemplates · ×1

applyTemplates::visit (cyclomatic 16) utils/doclint/api_parser.js:298 — applyTemplates::visit has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · (computed) (cyclomatic 16) · ×1

(computed) (cyclomatic 16) browser_patches/firefox/juggler/protocol/PageHandler.js:484 — (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 ((anonymous), sendEvents, sendEvents::(anonymous)). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · generate_channels.generateChannels (cognitive 239) · ×1

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.

D2 · Cognitive Complexity · roleUtils.getTextAlternativeInternal (cognitive 228) · ×1

roleUtils.getTextAlternativeInternal (cognitive 228) packages/injected/src/roleUtils.ts:687 — roleUtils.getTextAlternativeInternal has cognitive complexity 228 (threshold 15). Drivers by points: if/else 58 (149 pts), boolean chains 59, loops 4 (12 pts), ternaries 3 (8 pts) (nesting depth added 104). 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 · cssTokenizer.tokenize (cognitive 210) · ×1

cssTokenizer.tokenize (cognitive 210) packages/isomorphic/cssTokenizer.ts:77 — cssTokenizer.tokenize has cognitive complexity 210 (threshold 15). Drivers by points: if/else 125 (160 pts), boolean chains 25, loops 16 (25 pts) (nesting depth added 44). Most of this is not in the body itself: 3 of the 210 points are its own statements and the rest belongs to 18 function literals inside it that branch (lines 143, 342, 470, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · snapshotterInjected.frameSnapshotStreamer (cognitive 179) · ×1

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, 43 points are the body's own statements and 136 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.

D2 · Cognitive Complexity · Streamer.captureSnapshot (cognitive 135) · ×1

Streamer.captureSnapshot (cognitive 135) packages/playwright-core/src/server/trace/recorder/snapshotterInjected.ts:367 — Streamer.captureSnapshot has cognitive complexity 135 (threshold 15). Drivers by points: if/else 55 (81 pts), boolean chains 33, ternaries 7 (15 pts), loops 4 (6 pts) (nesting depth added 36). Most of this is not in the body itself: 10 of the 135 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 384, 455, 464, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · check_deps.innerCheckDeps (cognitive 131) · ×1

check_deps.innerCheckDeps (cognitive 131) utils/check_deps.js:62 — check_deps.innerCheckDeps has cognitive complexity 131 (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). Of this number, 130 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · locatorGenerators.innerAsLocators (cognitive 113) · ×1

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 · dashboard_compressed_v1.compressReports (cognitive 109) · ×1

dashboard_compressed_v1.compressReports (cognitive 109) utils/flakiness-dashboard/processing/dashboard_compressed_v1.js:33 — dashboard_compressed_v1.compressReports has cognitive complexity 109 (threshold 15). Drivers by points: if/else 18 (71 pts), loops 6 (17 pts), boolean chains 11, ternaries 2 (10 pts) (nesting depth added 72). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · 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.

D2 · Cognitive Complexity · generateDotnetApi.renderMethod (cognitive 87) · ×1

generateDotnetApi.renderMethod (cognitive 87) utils/doclint/generateDotnetApi.js:489 — generateDotnetApi.renderMethod has cognitive complexity 87 (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). Of this number, 58 points are the body's own statements and 29 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · uiModeView.UIModeView (cognitive 85) · ×1

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.

D2 · Cognitive Complexity · selectorParser.parseAttributeSelector (cognitive 77) · ×1

selectorParser.parseAttributeSelector (cognitive 77) packages/isomorphic/selectorParser.ts:276 — selectorParser.parseAttributeSelector has cognitive complexity 77 (threshold 15). Drivers by points: if/else 33 (45 pts), boolean chains 22, loops 8 (9 pts), error handling 1 (nesting depth added 13). Of this number, 75 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · cssParser.parseCSS (cognitive 76) · ×1

cssParser.parseCSS (cognitive 76) packages/isomorphic/cssParser.ts:39 — cssParser.parseCSS has cognitive complexity 76 (threshold 15). Drivers by points: if/else 33 (55 pts), boolean chains 12, loops 6 (8 pts), error handling 1 (nesting depth added 24). Of this number, 75 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SnapshotRenderer.render (cognitive 74) · ×1

SnapshotRenderer.render (cognitive 74) packages/isomorphic/trace/snapshotRenderer.ts:87 — SnapshotRenderer.render has cognitive complexity 74 (threshold 15). Drivers by points: if/else 19 (44 pts), boolean chains 20, ternaries 3 (6 pts), loops 2 (4 pts) (nesting depth added 30). Most of this is not in the body itself: 0 of the 74 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 89, 195). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · APIRequestContext._sendRequest (cognitive 74) · ×1

APIRequestContext._sendRequest (cognitive 74) packages/playwright-core/src/server/fetch.ts:326 — APIRequestContext._sendRequest has cognitive complexity 74 (threshold 15). Drivers by points: if/else 25 (33 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 74 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 392, 396, 353, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · minimist.minimist (cognitive 74) · ×1

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). 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 · program.program (cognitive 71) · ×1

program.program (cognitive 71) packages/playwright-core/src/tools/cli-client/program.ts:77 — program.program has cognitive complexity 71 (threshold 15). Drivers by points: if/else 25 (46 pts), ternaries 8 (15 pts), boolean chains 7, loops 1 (2 pts), match/switch 1 (nesting depth added 29). Of this number, 67 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.

D2 · Cognitive Complexity · annotations.Annotations (cognitive 69) · ×1

annotations.Annotations (cognitive 69) packages/dashboard/src/annotations.tsx:137 — annotations.Annotations has cognitive complexity 69 (threshold 15). Drivers by points: if/else 35 (44 pts), boolean chains 16, ternaries 7 (8 pts), loops 1 (nesting depth added 10). Of this number, 46 points are the body's own statements and 23 belong to 18 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · ariaSnapshot.generateAriaTree (cognitive 69) · ×1

ariaSnapshot.generateAriaTree (cognitive 69) packages/injected/src/ariaSnapshot.ts:81 — ariaSnapshot.generateAriaTree has cognitive complexity 69 (threshold 15). Drivers by points: if/else 25 (37 pts), boolean chains 17, loops 6 (12 pts), ternaries 3 (nesting depth added 18). Of this number, 29 points are the body's own statements and 40 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · generateDotnetApi.translateType (cognitive 68) · ×1

generateDotnetApi.translateType (cognitive 68) utils/doclint/generateDotnetApi.js:709 — 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.

D2 · Cognitive Complexity · utilityScriptSerializers.parseEvaluationResultValue (cognitive 67) · ×1

utilityScriptSerializers.parseEvaluationResultValue (cognitive 67) packages/isomorphic/utilityScriptSerializers.ts: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.

D2 · Cognitive Complexity · InjectedScript.expectSingleElement (cognitive 63) · ×1

InjectedScript.expectSingleElement (cognitive 63) packages/injected/src/injectedScript.ts:1518 — 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.

D2 · Cognitive Complexity · utilityScriptSerializers.innerSerialize (cognitive 62) · ×1

utilityScriptSerializers.innerSerialize (cognitive 62) packages/isomorphic/utilityScriptSerializers.ts:253 — utilityScriptSerializers.innerSerialize has cognitive complexity 62 (threshold 15). Drivers by points: if/else 33 (43 pts), loops 5 (9 pts), boolean chains 5, error handling 2 (5 pts) (nesting depth added 17). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · selectorGenerator.buildTextCandidates (cognitive 61) · ×1

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.

D2 · Cognitive Complexity · ariaSnapshot.parseAriaSnapshot (cognitive 61) · ×1

ariaSnapshot.parseAriaSnapshot (cognitive 61) packages/isomorphic/ariaSnapshot.ts:131 — ariaSnapshot.parseAriaSnapshot has cognitive complexity 61 (threshold 15). Drivers by points: if/else 19 (38 pts), boolean chains 19, loops 2, ternaries 1 (2 pts) (nesting depth added 20). Most of this is not in the body itself: 9 of the 61 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 175, 152). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · dashboard.Dashboard (cognitive 60) · ×1

dashboard.Dashboard (cognitive 60) packages/dashboard/src/dashboard.tsx: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, 44 points are the body's own statements and 16 belong to 13 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · ariaSnapshotRenderer.renderAriaSnapshotAsYaml (cognitive 60) · ×1

ariaSnapshotRenderer.renderAriaSnapshotAsYaml (cognitive 60) packages/isomorphic/ariaSnapshotRenderer.ts:27 — ariaSnapshotRenderer.renderAriaSnapshotAsYaml has cognitive complexity 60 (threshold 15). Drivers by points: if/else 30 (37 pts), ternaries 4 (10 pts), boolean chains 7, loops 3 (6 pts) (nesting depth added 16). Most of this is not in the body itself: 3 of the 60 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 83, 38, 32). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · snapshotRenderer.snapshotScript (cognitive 60) · ×1

snapshotRenderer.snapshotScript (cognitive 60) packages/isomorphic/trace/snapshotRenderer.ts:322 — snapshotRenderer.snapshotScript has cognitive complexity 60 (threshold 15). Drivers by points: if/else 14 (22 pts), loops 19 (22 pts), boolean chains 8, error handling 2 (4 pts), ternaries 2 (4 pts) (nesting depth added 15). Most of this is not in the body itself: 2 of the 60 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 357, 473, 553, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · hostPlatform.calculatePlatform (cognitive 59) · ×1

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.

D2 · Cognitive Complexity · webSocketMock.inject (cognitive 57) · ×1

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). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · markdown.buildTree (cognitive 57) · ×1

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 literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FrameSession._initialize (cognitive 54) · ×1

FrameSession._initialize (cognitive 54) REDACTED:472 — FrameSession._initialize has cognitive complexity 54 (threshold 15). Drivers by points: if/else 22 (36 pts), boolean chains 9, loops 4 (6 pts), error handling 1 (2 pts), ternaries 1 (nesting depth added 17). Of this number, 45 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · consoleTab.useConsoleTabModel (cognitive 54) · ×1

consoleTab.useConsoleTabModel (cognitive 54) REDACTED:64 — consoleTab.useConsoleTabModel has cognitive complexity 54 (threshold 15). Drivers by points: if/else 11 (22 pts), ternaries 7 (18 pts), boolean chains 13, loops 1 (nesting depth added 22). Most of this is not in the body itself: 0 of the 54 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 65, 68, 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.

D2 · Cognitive Complexity · APIRequestContext._innerFetch (cognitive 53) · ×1

APIRequestContext._innerFetch (cognitive 53) packages/playwright-core/src/client/fetch.ts:179 — 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). Most of this is not in the body itself: 0 of the 53 points are its own statements and the rest belongs to one function literal inside it that branches (line 180). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · ElementHandle._performPointerAction (cognitive 53) · ×1

ElementHandle._performPointerAction (cognitive 53) packages/playwright-core/src/server/dom.ts:391 — 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 literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SelectorEvaluatorImpl._matchesParents (cognitive 51) · ×1

SelectorEvaluatorImpl._matchesParents (cognitive 51) packages/injected/src/selectorEvaluator.ts: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.

D2 · Cognitive Complexity · Response.serialize (cognitive 50) · ×1

Response.serialize (cognitive 50) packages/playwright-core/src/tools/backend/response.ts:172 — 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.

D2 · Cognitive Complexity · generateNameDefault (cognitive 50) · ×1

generateNameDefault (cognitive 50) utils/doclint/generateDotnetApi.js:391 — 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.

D2 · Cognitive Complexity · HarBackend._harFindResponse (cognitive 49) · ×1

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.

D2 · Cognitive Complexity · traceConsole.traceConsole (cognitive 49) · ×1

traceConsole.traceConsole (cognitive 49) packages/playwright-core/src/tools/trace/traceConsole.ts: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.

D2 · Cognitive Complexity · Response._build (cognitive 48) · ×1

Response._build (cognitive 48) packages/playwright-core/src/tools/backend/response.ts:267 — Response._build has cognitive complexity 48 (threshold 15). Drivers by points: if/else 19 (29 pts), ternaries 6 (11 pts), boolean chains 6, loops 1 (2 pts) (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.

D2 · Cognitive Complexity · selectorGenerator.generateSelectorFor (cognitive 47) · ×1

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 literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · jsonSchema.validate (cognitive 47) · ×1

jsonSchema.validate (cognitive 47) packages/isomorphic/jsonSchema.ts: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.

D2 · Cognitive Complexity · workbench.PartitionedWorkbench (cognitive 47) · ×1

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.

D2 · Cognitive Complexity · selectorUtils.elementText (cognitive 46) · ×1

selectorUtils.elementText (cognitive 46) packages/injected/src/selectorUtils.ts:67 — 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.

D2 · Cognitive Complexity · selectorParser.parseSelector (cognitive 46) · ×1

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.

D2 · Cognitive Complexity · TraceModernizer._modernize_8_to_9 (cognitive 46) · ×1

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.

D2 · Cognitive Complexity · screenshotter.inPagePrepareForScreenshots (cognitive 46) · ×1

screenshotter.inPagePrepareForScreenshots (cognitive 46) packages/playwright-core/src/server/screenshotter.ts:49 — screenshotter.inPagePrepareForScreenshots has cognitive complexity 46 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 7 (13 pts), error handling 3 (11 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 22). Of this number, 16 points are the body's own statements and 30 belong to 5 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TraceLoader.load (cognitive 45) · ×1

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.

D2 · Cognitive Complexity · innerRenderMdNode (cognitive 45) · ×1

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.

D2 · Cognitive Complexity · codeMirrorWrapper.CodeMirrorWrapper (cognitive 44) · ×1

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). Most of this is not in the body itself: 0 of the 44 points are its own statements 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.

D2 · Cognitive Complexity · InjectedScript.elementState (cognitive 42) · ×1

InjectedScript.elementState (cognitive 42) packages/injected/src/injectedScript.ts:783 — InjectedScript.elementState has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 10 (21 pts), if/else 10 (14 pts), boolean chains 7 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · urlMatch.globToRegexPattern (cognitive 42) · ×1

urlMatch.globToRegexPattern (cognitive 42) packages/isomorphic/urlMatch.ts: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.

D2 · Cognitive Complexity · selectorGenerator.buildNoTextCandidates (cognitive 41) · ×1

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.

D2 · Cognitive Complexity · main.doFetch (cognitive 41) · ×1

main.doFetch (cognitive 41) packages/trace-viewer/src/sw/main.ts: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.

D2 · Cognitive Complexity · Filter.matches (cognitive 40) · ×1

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.

D2 · Cognitive Complexity · Frame._expectInternal (cognitive 40) · ×1

Frame._expectInternal (cognitive 40) packages/playwright-core/src/server/frames.ts:1530 — 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.

D2 · Cognitive Complexity · ElementHandle._retryAction (cognitive 40) · ×1

ElementHandle._retryAction (cognitive 40) packages/playwright-core/src/server/dom.ts:317 — ElementHandle._retryAction has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (30 pts), ternaries 2 (6 pts), boolean chains 3, loops 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.

D2 · Cognitive Complexity · Page.expectScreenshot (cognitive 40) · ×1

Page.expectScreenshot (cognitive 40) packages/playwright-core/src/server/page.ts:717 — 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 literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · treeView.TreeView (cognitive 40) · ×1

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.

D2 · Cognitive Complexity · injectedScript.deepEquals (cognitive 39) · ×1

injectedScript.deepEquals (cognitive 39) packages/injected/src/injectedScript.ts:1877 — 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.

D2 · Cognitive Complexity · CRNetworkManager._onRequest (cognitive 39) · ×1

CRNetworkManager._onRequest (cognitive 39) packages/playwright-core/src/server/chromium/crNetworkManager.ts:282 — 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.

D2 · Cognitive Complexity · traceRequests.traceRequest (cognitive 39) · ×1

traceRequests.traceRequest (cognitive 39) packages/playwright-core/src/tools/trace/traceRequests.ts: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.

D2 · Cognitive Complexity · serializers.innerParseSerializedValue (cognitive 39) · ×1

serializers.innerParseSerializedValue (cognitive 39) packages/protocol/src/serializers.ts:58 — serializers.innerParseSerializedValue has cognitive complexity 39 (threshold 15). Drivers by points: if/else 24 (31 pts), loops 4 (8 pts) (nesting depth added 11). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · recorder.Recorder (cognitive 39) · ×1

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.

D2 · Cognitive Complexity · build_deps_true.collectImports (cognitive 39) · ×1

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.

D2 · Cognitive Complexity · roleUtils.innerAccumulatedElementText (cognitive 38) · ×1

roleUtils.innerAccumulatedElementText (cognitive 38) packages/injected/src/roleUtils.ts:1018 — roleUtils.innerAccumulatedElementText has cognitive complexity 38 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 9 (13 pts), boolean chains 7, ternaries 2 (3 pts) (nesting depth added 15). Of this number, 26 points are the body's own statements and 12 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · roleSelectorEngine.queryRole (cognitive 38) · ×1

roleSelectorEngine.queryRole (cognitive 38) packages/injected/src/roleSelectorEngine.ts:143 — roleSelectorEngine.queryRole has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 10, loops 1 (nesting depth added 8). Most of this is not in the body itself: 0 of the 38 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 145, 190). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · ariaSnapshot.renderAriaTreeAsJSON (cognitive 37) · ×1

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

D2 · Cognitive Complexity · browserActions.launchContext (cognitive 37) · ×1

browserActions.launchContext (cognitive 37) packages/playwright-core/src/cli/browserActions.ts:65 — browserActions.launchContext has cognitive complexity 37 (threshold 15). Drivers by points: if/else 25 (29 pts), error handling 2 (4 pts), boolean chains 2, ternaries 2 (nesting depth added 6). Of this number, 36 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.

D2 · Cognitive Complexity · FrameSelectors._callOnSelectorInternal (cognitive 36) · ×1

FrameSelectors._callOnSelectorInternal (cognitive 36) packages/playwright-core/src/server/frameSelectors.ts:243 — 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 literals inside it that branch (lines 261, 258, 285). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · generateDotnetApi.renderMember (cognitive 36) · ×1

generateDotnetApi.renderMember (cognitive 36) utils/doclint/generateDotnetApi.js:315 — 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.

D2 · Cognitive Complexity · selectorGenerator.cssFallback (cognitive 35) · ×1

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). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TextOutput.list (cognitive 35) · ×1

TextOutput.list (cognitive 35) packages/playwright-core/src/tools/cli-client/output.ts:135 — 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.

D2 · Cognitive Complexity · ariaSnapshot.matchesNode (cognitive 34) · ×1

ariaSnapshot.matchesNode (cognitive 34) packages/injected/src/ariaSnapshot.ts:377 — 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.

D2 · Cognitive Complexity · serializers.innerSerializeValue (cognitive 34) · ×1

serializers.innerSerializeValue (cognitive 34) packages/protocol/src/serializers.ts:156 — serializers.innerSerializeValue has cognitive complexity 34 (threshold 15). Drivers by points: if/else 23, loops 4 (8 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · timeline.Timeline (cognitive 34) · ×1

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.

D2 · Cognitive Complexity · workbenchLoader.WorkbenchLoader (cognitive 34) · ×1

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, 148, 56, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · documentation.processCodeGroups (cognitive 34) · ×1

documentation.processCodeGroups (cognitive 34) utils/doclint/documentation.js:908 — 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.

D2 · Cognitive Complexity · BidiConnection._dispatchMessage (cognitive 33) · ×1

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.

D2 · Cognitive Complexity · WVPage._onConsoleMessage (cognitive 33) · ×1

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.

D2 · Cognitive Complexity · BidiNetworkManager._onBeforeRequestSent (cognitive 32) · ×1

BidiNetworkManager._onBeforeRequestSent (cognitive 32) packages/playwright-core/src/server/bidi/bidiNetworkManager.ts:61 — 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.

D2 · Cognitive Complexity · playbackControl.usePlayback (cognitive 32) · ×1

playbackControl.usePlayback (cognitive 32) packages/trace-viewer/src/ui/playbackControl.tsx:48 — playbackControl.usePlayback has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 8, ternaries 7, loops 1 (nesting depth added 1). Most of this is not in the body itself: 10 of the 32 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 96, 150, 124, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · validate_deps.validateDirectory (cognitive 32) · ×1

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.

D2 · Cognitive Complexity · patchLinksInText (cognitive 32) · ×1

patchLinksInText (cognitive 32) utils/doclint/documentation.js:751 — patchLinksInText has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 6 (nesting depth added 13). Most of this is not in the body itself: 0 of the 32 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 752, 802, 784, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · InjectedScript.expectHitTarget (cognitive 31) · ×1

InjectedScript.expectHitTarget (cognitive 31) packages/injected/src/injectedScript.ts:1023 — 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.

D2 · Cognitive Complexity · TraceModel.constructor (cognitive 31) · ×1

TraceModel.constructor (cognitive 31) packages/isomorphic/trace/traceModel.ts:98 — TraceModel.constructor has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 13, loops 8 (12 pts), if/else 3 (6 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · cookieStore.parseRawCookie (cognitive 31) · ×1

cookieStore.parseRawCookie (cognitive 31) packages/playwright-core/src/server/cookieStore.ts:131 — cookieStore.parseRawCookie has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (22 pts), match/switch 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 15). Of this number, 29 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Chromium.launchWithSeleniumHub (cognitive 31) · ×1

Chromium.launchWithSeleniumHub (cognitive 31) packages/playwright-core/src/server/chromium/chromium.ts:251 — 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.

D2 · Cognitive Complexity · (anonymous) (cognitive 31) · ×1

(anonymous) (cognitive 31) utils/linux-browser-dependencies/inside_docker/list_dependencies.js:27 — (anonymous) has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 11 (14 pts), boolean chains 2, ternaries 1 (nesting depth added 9). Of this number, 29 points are the body's own statements and 2 belong to 13 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · istanbulCoverage.mergeIstanbulCoverage (cognitive 30) · ×1

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.

D2 · Cognitive Complexity · traceModel.mergeActionsAndUpdateTimingSameTrace (cognitive 30) · ×1

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.

D2 · Cognitive Complexity · config.validateBrowserConfig (cognitive 30) · ×1

config.validateBrowserConfig (cognitive 30) packages/playwright-core/src/tools/mcp/config.ts:224 — 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.

D2 · Cognitive Complexity · WebKit.defaultArgs (cognitive 29) · ×1

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.

D2 · Cognitive Complexity · program.killAllDaemons (cognitive 29) · ×1

program.killAllDaemons (cognitive 29) packages/playwright-core/src/tools/cli-client/program.ts:357 — 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.

D2 · Cognitive Complexity · stackTrace.parseStackFrame (cognitive 29) · ×1

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.

D2 · Cognitive Complexity · listView.ListView (cognitive 29) · ×1

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.

D2 · Cognitive Complexity · parseOverrides.parseOverrides (cognitive 29) · ×1

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). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · processLauncher.launchProcess (cognitive 28) · ×1

processLauncher.launchProcess (cognitive 28) REDACTED:133 — processLauncher.launchProcess has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 8, error handling 2 (4 pts), loops 2, ternaries 2 (nesting depth added 4). Of this number, 22 points are the body's own statements and 6 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.

D2 · Cognitive Complexity · index.jsonToTS (cognitive 28) · ×1

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). Most of this is not in the body itself: 0 of the 28 points are its own statements 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.

D2 · Cognitive Complexity · InjectedScript.selectOptions (cognitive 27) · ×1

InjectedScript.selectOptions (cognitive 27) packages/injected/src/injectedScript.ts:843 — 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 literals inside it that branch (lines 856, 859). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · PythonLocatorFactory.generateLocator (cognitive 27) · ×1

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.

D2 · Cognitive Complexity · EventEmitter.removeListener (cognitive 27) · ×1

EventEmitter.removeListener (cognitive 27) packages/playwright-core/src/client/eventEmitter.ts:185 — 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.

D2 · Cognitive Complexity · TypesGenerator.classBody (cognitive 27) · ×1

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.

D2 · Cognitive Complexity · validate_deps.isEntryUsed (cognitive 27) · ×1

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.

D2 · Cognitive Complexity · TargetRegistry.constructor (cognitive 26) · ×1

TargetRegistry.constructor (cognitive 26) browser_patches/firefox/juggler/TargetRegistry.js:115 — 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 literals inside it that branch (lines 185, 152, 220, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · reportView.ReportView (cognitive 26) · ×1

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.

D2 · Cognitive Complexity · selectorParser.parseSelectorString (cognitive 26) · ×1

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 literals inside it that branch (lines 189, 232). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · Frame.waitForSelector (cognitive 26) · ×1

Frame.waitForSelector (cognitive 26) packages/playwright-core/src/server/frames.ts:836 — 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 846, 853). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · bisect-chromium.findExecutable (cognitive 26) · ×1

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.

D2 · Cognitive Complexity · ApiParser.parseArgument (cognitive 26) · ×1

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.

D2 · Cognitive Complexity · api_parser.applyTemplates (cognitive 26) · ×1

api_parser.applyTemplates (cognitive 26) utils/doclint/api_parser.js:293 — api_parser.applyTemplates has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 6, loops 4 (5 pts) (nesting depth added 7). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 298, 332). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · (anonymous) (cognitive 26) · ×1

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

D2 · Cognitive Complexity · parseMember (cognitive 26) · ×1

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.

D2 · Cognitive Complexity · InjectedScript.dispatchEvent (cognitive 25) · ×1

InjectedScript.dispatchEvent (cognitive 25) packages/injected/src/injectedScript.ts:1205 — 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 literals inside it that branch (lines 1214, 1226, 1238, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · webAuthn.inject (cognitive 25) · ×1

webAuthn.inject (cognitive 25) packages/injected/src/webAuthn.ts:57 — webAuthn.inject has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 14, if/else 6, loops 4, ternaries 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.

D2 · Cognitive Complexity · selectorParser.splitSelectorByFrame (cognitive 25) · ×1

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.

D2 · Cognitive Complexity · JavaLocatorFactory.generateLocator (cognitive 25) · ×1

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.

D2 · Cognitive Complexity · protocolFormatter._formatProtocolParam (cognitive 25) · ×1

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.

D2 · Cognitive Complexity · urlMatch.resolveGlobBase (cognitive 25) · ×1

urlMatch.resolveGlobBase (cognitive 25) packages/isomorphic/urlMatch.ts: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: 11 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 232). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · HarTracer._onRequestFinished (cognitive 25) · ×1

HarTracer._onRequestFinished (cognitive 25) packages/playwright-core/src/server/har/harTracer.ts:327 — HarTracer._onRequestFinished has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 8, ternaries 1 (nesting depth added 4). Of this number, 13 points are the body's own statements and 12 belong to 5 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.

D2 · Cognitive Complexity · HarTracer._onWebSocket (cognitive 25) · ×1

HarTracer._onWebSocket (cognitive 25) packages/playwright-core/src/server/har/harTracer.ts:444 — 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 literals inside it that branch (lines 459, 511, 475, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · Connection.dispatch (cognitive 25) · ×1

Connection.dispatch (cognitive 25) packages/playwright-core/src/client/connection.ts:235 — 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.

D2 · Cognitive Complexity · callTab.parseSerializedValue (cognitive 25) · ×1

callTab.parseSerializedValue (cognitive 25) packages/trace-viewer/src/ui/callTab.tsx: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.

D2 · Cognitive Complexity · snapshotTab.collectSnapshots (cognitive 25) · ×1

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.

D2 · Cognitive Complexity · compare.compare (cognitive 25) · ×1

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.

D2 · Cognitive Complexity · roleSelectorEngine.validateAttributes (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · JavaScriptLocatorFactory.generateLocator (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · CSharpLocatorFactory.generateLocator (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · Frame.gotoImpl (cognitive 24) · ×1

Frame.gotoImpl (cognitive 24) packages/playwright-core/src/server/frames.ts:694 — 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 literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Frame.expect (cognitive 24) · ×1

Frame.expect (cognitive 24) packages/playwright-core/src/server/frames.ts:1468 — 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.

D2 · Cognitive Complexity · input.buildLayoutClosure (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · APIRequestContext.fetch (cognitive 24) · ×1

APIRequestContext.fetch (cognitive 24) packages/playwright-core/src/server/fetch.ts:193 — APIRequestContext.fetch has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 3 (6 pts), boolean chains 4, ternaries 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · consoleTab.format (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · ariaModeView.collectAriaModeTargets (cognitive 24) · ×1

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 literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · snapshotTab.InspectModeController (cognitive 24) · ×1

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). Most of this is not in the body itself: 0 of the 24 points are its own statements 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.

D2 · Cognitive Complexity · documentation.patchCSharpOptionOverloads (cognitive 24) · ×1

documentation.patchCSharpOptionOverloads (cognitive 24) utils/doclint/documentation.js:830 — 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.

D2 · Cognitive Complexity · generate_channels.inlineType (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · debuggerPanel.DebuggerPanel (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · InjectedScript.querySelectorAll (cognitive 23) · ×1

InjectedScript.querySelectorAll (cognitive 23) packages/injected/src/injectedScript.ts: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.

D2 · Cognitive Complexity · JavaScriptLanguageGenerator._generateActionCall (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · PythonLanguageGenerator.generateHeader (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · SnapshotRenderer.resourceByUrl (cognitive 23) · ×1

SnapshotRenderer.resourceByUrl (cognitive 23) packages/isomorphic/trace/snapshotRenderer.ts:215 — 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.

D2 · Cognitive Complexity · HarTracer._onResponse (cognitive 23) · ×1

HarTracer._onResponse (cognitive 23) packages/playwright-core/src/server/har/harTracer.ts:567 — 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.

D2 · Cognitive Complexity · browserContext.verifyClientCertificates (cognitive 23) · ×1

browserContext.verifyClientCertificates (cognitive 23) packages/playwright-core/src/server/browserContext.ts:809 — browserContext.verifyClientCertificates has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 6, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · installActions.installBrowsers (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · sourceTab.useSources (cognitive 23) · ×1

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). Most of this is not in the body itself: 0 of the 23 points are its own statements 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.

D2 · Cognitive Complexity · RecordActionTool._shouldGenerateKeyPressFor (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · JsonRecordActionTool._shouldGenerateKeyPressFor (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · locatorParser.tokenize (cognitive 22) · ×1

locatorParser.tokenize (cognitive 22) packages/isomorphic/locatorParser.ts:57 — locatorParser.tokenize has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 3, loops 2 (nesting depth added 3). Of this number, 12 points are the body's own statements and 10 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · TraceModernizer._innerAppendEvent (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · elementHandle.convertInputFiles (cognitive 22) · ×1

elementHandle.convertInputFiles (cognitive 22) packages/playwright-core/src/client/elementHandle.ts:285 — 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.

D2 · Cognitive Complexity · Registry.constructor (cognitive 22) · ×1

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 literals inside it that branch (lines 516, 747, 512, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · WKPage._onConsoleMessage (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · localUtils.zip (cognitive 22) · ×1

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

D2 · Cognitive Complexity · config.configFromCLIOptions (cognitive 22) · ×1

config.configFromCLIOptions (cognitive 22) packages/playwright-core/src/tools/mcp/config.ts:300 — config.configFromCLIOptions has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 2, ternaries 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · program.decorateMCPCommand (cognitive 22) · ×1

program.decorateMCPCommand (cognitive 22) packages/playwright-core/src/tools/mcp/program.ts:34 — program.decorateMCPCommand has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4, error handling 2, ternaries 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 0 of the 22 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 113, 164, 88, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · generate_dotnet_channels.inlineType (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · TypesGenerator.stringifySimpleType (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · setCookies (cognitive 22) · ×1

setCookies (cognitive 22) browser_patches/firefox/juggler/TargetRegistry.js:1172 — 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.

D2 · Cognitive Complexity · sessionSidebar.SessionSidebar (cognitive 21) · ×1

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.

D2 · Cognitive Complexity · connect.ConnectApp (cognitive 21) · ×1

connect.ConnectApp (cognitive 21) packages/extension/src/ui/connect.tsx:39 — connect.ConnectApp has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12, boolean chains 6, error handling 2, ternaries 1. Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 50, 131, 123). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · bidiInsertText.bidiInsertText (cognitive 21) · ×1

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.

D2 · Cognitive Complexity · Route._innerFulfill (cognitive 21) · ×1

Route._innerFulfill (cognitive 21) packages/playwright-core/src/client/network.ts:373 — 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.

D2 · Cognitive Complexity · BidiChromium._innerDefaultArgs (cognitive 21) · ×1

BidiChromium._innerDefaultArgs (cognitive 21) packages/playwright-core/src/server/bidi/bidiChromium.ts:105 — BidiChromium._innerDefaultArgs has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). Of this number, 18 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.

D2 · Cognitive Complexity · traceActions.traceAction (cognitive 21) · ×1

traceActions.traceAction (cognitive 21) packages/playwright-core/src/tools/trace/traceActions.ts: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.

D2 · Cognitive Complexity · traceRequests.traceRequests (cognitive 21) · ×1

traceRequests.traceRequests (cognitive 21) packages/playwright-core/src/tools/trace/traceRequests.ts: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.

D2 · Cognitive Complexity · consoleTab.ConsoleTab (cognitive 21) · ×1

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.

D2 · Cognitive Complexity · ansi2html.ansi2html (cognitive 21) · ×1

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.

D2 · Cognitive Complexity · splitView.SplitView (cognitive 21) · ×1

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.

D2 · Cognitive Complexity · renderMethod · ×1

renderMethod::processArg (cognitive 21) utils/doclint/generateDotnetApi.js:570 — 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.

D2 · Cognitive Complexity · fromParsedType (cognitive 21) · ×1

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.

D2 · Cognitive Complexity · applyTemplates · ×1

applyTemplates::visit (cognitive 21) utils/doclint/api_parser.js:298 — applyTemplates::visit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5, 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.

D2 · Cognitive Complexity · PageHandler.['Page.dispatchMouseEvent'] (cognitive 20) · ×1

PageHandler.['Page.dispatchMouseEvent'] (cognitive 20) browser_patches/firefox/juggler/protocol/PageHandler.js:484 — 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). Most of this is not in the body itself: 0 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 524, 486). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · Filter.tokenize (cognitive 20) · ×1

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.

D2 · Cognitive Complexity · ariaSnapshot.toAriaNode (cognitive 20) · ×1

ariaSnapshot.toAriaNode (cognitive 20) packages/injected/src/ariaSnapshot.ts:235 — 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.

D2 · Cognitive Complexity · traceModel.adjustMonotonicTime (cognitive 20) · ×1

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.

D2 · Cognitive Complexity · bidiExecutionContext.renderPreview (cognitive 20) · ×1

bidiExecutionContext.renderPreview (cognitive 20) packages/playwright-core/src/server/bidi/bidiExecutionContext.ts: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.

D2 · Cognitive Complexity · Chromium._innerDefaultArgs (cognitive 20) · ×1

Chromium._innerDefaultArgs (cognitive 20) packages/playwright-core/src/server/chromium/chromium.ts:366 — 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.

D2 · Cognitive Complexity · BrowserContextDispatcher.constructor (cognitive 20) · ×1

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.

D2 · Cognitive Complexity · ElementHandle._setInputFiles (cognitive 20) · ×1

ElementHandle._setInputFiles (cognitive 20) packages/playwright-core/src/server/dom.ts:718 — ElementHandle._setInputFiles has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, if/else 8, ternaries 2 (4 pts) (nesting depth added 2). Of this number, 12 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.

D2 · Cognitive Complexity · (computed) (cognitive 20) · ×1

(computed) (cognitive 20) browser_patches/firefox/juggler/protocol/PageHandler.js:484 — (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). Most of this is not in the body itself: 0 of the 20 points are its own statements and the rest belongs to 3 function items inside it that branch ((anonymous), sendEvents, sendEvents::(anonymous)). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · InjectedScript.fill (cognitive 19) · ×1

InjectedScript.fill (cognitive 19) packages/injected/src/injectedScript.ts:892 — InjectedScript.fill has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 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.

D2 · Cognitive Complexity · InjectedScript.previewNode (cognitive 19) · ×1

InjectedScript.previewNode (cognitive 19) packages/injected/src/injectedScript.ts:1272 — 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.

D2 · Cognitive Complexity · ariaSnapshot.findNewNode (cognitive 19) · ×1

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). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · EventEmitter._removeAllListeners (cognitive 19) · ×1

EventEmitter._removeAllListeners (cognitive 19) packages/playwright-core/src/client/eventEmitter.ts:261 — 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.

D2 · Cognitive Complexity · BrowserContext.constructor (cognitive 19) · ×1

BrowserContext.constructor (cognitive 19) packages/playwright-core/src/client/browserContext.ts:99 — 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). Most of this is not in the body itself: 0 of the 19 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 121, 143, 171, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · crCoverage.convertToDisjointRanges (cognitive 19) · ×1

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.

D2 · Cognitive Complexity · FrameSession._updateViewport (cognitive 19) · ×1

FrameSession._updateViewport (cognitive 19) REDACTED:970 — FrameSession._updateViewport has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 2 (3 pts), 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.

D2 · Cognitive Complexity · WKPage._onTargetCreated (cognitive 19) · ×1

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.

D2 · Cognitive Complexity · BrowserContext.setStorageState (cognitive 19) · ×1

BrowserContext.setStorageState (cognitive 19) packages/playwright-core/src/server/browserContext.ts:684 — 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.

D2 · Cognitive Complexity · Session.deleteData (cognitive 19) · ×1

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.

D2 · Cognitive Complexity · SimpleChannel._onMessageInternal (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · roleUtils.getCSSContent (cognitive 18) · ×1

roleUtils.getCSSContent (cognitive 18) packages/injected/src/roleUtils.ts:408 — 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.

D2 · Cognitive Complexity · Highlight.updateHighlight (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · SelectorEvaluatorImpl._querySimple (cognitive 18) · ×1

SelectorEvaluatorImpl._querySimple (cognitive 18) packages/injected/src/selectorEvaluator.ts: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.

D2 · Cognitive Complexity · selectorEvaluator.sortInDOMOrder (cognitive 18) · ×1

selectorEvaluator.sortInDOMOrder (cognitive 18) packages/injected/src/selectorEvaluator.ts: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). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · selectorGenerator.generateSelector (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · selectorGenerator.isGuidLike (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · InjectedScript.retarget (cognitive 18) · ×1

InjectedScript.retarget (cognitive 18) packages/injected/src/injectedScript.ts:669 — 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.

D2 · Cognitive Complexity · InjectedScript.setupHitTargetInterceptor (cognitive 18) · ×1

InjectedScript.setupHitTargetInterceptor (cognitive 18) packages/injected/src/injectedScript.ts:1135 — 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 literals inside it that branch (lines 1162, 1188). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · RecordActionTool.onInput (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · dependencies.validateDependenciesLinux (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · Registry.resolveBrowsers (cognitive 18) · ×1

Registry.resolveBrowsers (cognitive 18) packages/playwright-core/src/server/registry/index.ts:1280 — 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 literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FrameSelectors._queryFrames (cognitive 18) · ×1

FrameSelectors._queryFrames (cognitive 18) packages/playwright-core/src/server/frameSelectors.ts:183 — 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 literals inside it that branch (lines 189, 187, 216). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · HarTracer.stop (cognitive 18) · ×1

HarTracer.stop (cognitive 18) packages/playwright-core/src/server/har/harTracer.ts:657 — 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.

D2 · Cognitive Complexity · InterceptableRequest.createResponseBodyCallback (cognitive 18) · ×1

InterceptableRequest.createResponseBodyCallback (cognitive 18) packages/playwright-core/src/server/chromium/crNetworkManager.ts:594 — 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). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 595, 619). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · Electron.launch (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · FFBrowserContext.initialize (cognitive 18) · ×1

FFBrowserContext.initialize (cognitive 18) packages/playwright-core/src/server/firefox/ffBrowser.ts:172 — FFBrowserContext.initialize has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, 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.

D2 · Cognitive Complexity · callTab.propertyToString (cognitive 18) · ×1

callTab.propertyToString (cognitive 18) packages/trace-viewer/src/ui/callTab.tsx: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.

D2 · Cognitive Complexity · ariaModeView.AriaModeView (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · imageDiffView.ImageDiffView (cognitive 18) · ×1

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 literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D2 · Cognitive Complexity · Member.filterForLanguage (cognitive 18) · ×1

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.

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

_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). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch ((anonymous), handleListItem). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

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

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.

D2 · Cognitive Complexity · NetworkObserver.responseHead (cognitive 17) · ×1

NetworkObserver.responseHead (cognitive 17) browser_patches/firefox/juggler/NetworkObserver.js:971 — 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.

D2 · Cognitive Complexity · selectorUtils.matchesAttributePart (cognitive 17) · ×1

selectorUtils.matchesAttributePart (cognitive 17) packages/injected/src/selectorUtils.ts:31 — 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.

D2 · Cognitive Complexity · injectedScript.createTextMatcher (cognitive 17) · ×1

injectedScript.createTextMatcher (cognitive 17) packages/injected/src/injectedScript.ts:1780 — 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 literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · ClockController._replayLogOnce (cognitive 17) · ×1

ClockController._replayLogOnce (cognitive 17) packages/injected/src/clock.ts:439 — ClockController._replayLogOnce has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, 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.

D2 · Cognitive Complexity · java.formatContextOptions (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · imageUtils.scaleImageToSize (cognitive 17) · ×1

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

D2 · Cognitive Complexity · ChannelOwner._wrapApiCall (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · FrameSelectors.resolveFramesForSelector (cognitive 17) · ×1

FrameSelectors.resolveFramesForSelector (cognitive 17) packages/playwright-core/src/server/frameSelectors.ts:136 — 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.

D2 · Cognitive Complexity · DispatcherConnection.dispatch (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · Credentials._handleGet (cognitive 17) · ×1

Credentials._handleGet (cognitive 17) packages/playwright-core/src/server/credentials.ts:180 — 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.

D2 · Cognitive Complexity · traceViewer.startTraceViewerServer (cognitive 17) · ×1

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 literals inside it that branch (lines 94, 134, 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.

D2 · Cognitive Complexity · ContextDebugger._updateSource (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · network.httpRequest (cognitive 17) · ×1

network.httpRequest (cognitive 17) packages/utils/network.ts:48 — network.httpRequest has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, ternaries 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · Type.parse (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · constructor (cognitive 17) · ×1

constructor (cognitive 17) browser_patches/firefox/juggler/content/PageAgent.js:55 — 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.

D2 · Cognitive Complexity · observe (cognitive 17) · ×1

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, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · roleUtils.isElementHiddenForAria (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · Highlight._ensureElementHighlightRaf (cognitive 16) · ×1

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 literal inside it that branches (line 145). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · clock.install (cognitive 16) · ×1

clock.install (cognitive 16) packages/injected/src/clock.ts:815 — 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.

D2 · Cognitive Complexity · KeyParser._readAttributes (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · TraceModernizer._modernize_9_to_10 (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · EventEmitter._addListener (cognitive 16) · ×1

EventEmitter._addListener (cognitive 16) packages/playwright-core/src/client/eventEmitter.ts:110 — 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.

D2 · Cognitive Complexity · Registry.install (cognitive 16) · ×1

Registry.install (cognitive 16) packages/playwright-core/src/server/registry/index.ts:934 — Registry.install has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1, 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.

D2 · Cognitive Complexity · fileUploadUtils.prepareFilesForUpload (cognitive 16) · ×1

fileUploadUtils.prepareFilesForUpload (cognitive 16) packages/playwright-core/src/server/fileUploadUtils.ts:36 — fileUploadUtils.prepareFilesForUpload has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 4). 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 into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · instrumentation.createInstrumentation (cognitive 16) · ×1

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). Most of this is not in the body itself: 0 of the 16 points are its own statements and the rest belongs 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.

D2 · Cognitive Complexity · program.collectList (cognitive 16) · ×1

program.collectList (cognitive 16) packages/playwright-core/src/tools/cli-client/program.ts:408 — 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.

D2 · Cognitive Complexity · attachmentsTab.AttachmentsTab (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · networkResourceDetails.dumpHex (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · networkTab.renderCell (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · snapshotTab.SnapshotView (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · ImageChannel.intoRGB (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · comparators.compareImages (cognitive 16) · ×1

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

D2 · Cognitive Complexity · socksProxy.parsePattern (cognitive 16) · ×1

socksProxy.parsePattern (cognitive 16) packages/utils/socksProxy.ts: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.

D2 · Cognitive Complexity · treeView.TreeItemHeader (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · markdown.flattenWrappedLines (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · linkUtils.renderJSSignature (cognitive 16) · ×1

linkUtils.renderJSSignature (cognitive 16) utils/doclint/linkUtils.js:124 — 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.

D2 · Cognitive Complexity · TypesGenerator.generateTypes (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · Workspace.ensureConsistent (cognitive 16) · ×1

Workspace.ensureConsistent (cognitive 16) utils/workspace.js:80 — 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 literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · (computed) (cognitive 16) · ×1

(computed) (cognitive 16) browser_patches/firefox/juggler/protocol/PageHandler.js:316 — (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.

D2 · Cognitive Complexity · constructor (cognitive 16) · ×1

constructor (cognitive 16) browser_patches/firefox/juggler/content/FrameTree.js:397 — 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.

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

REDACTED

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

REDACTED

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

REDACTED

D30 · Dependency Vulnerabilities · Medium vulnerability · ×1

REDACTED

D35 · Change Coupling · Change coupling clique · ×1

Change coupling clique: bidiExecutionContext.ts, crExecutionContext.ts, wkExecutionContext.ts packages/playwright-core/src/server/bidi/bidiExecutionContext.ts — 3 files — `packages/playwright-core/src/server/bidi/bidiExecutionContext.ts`, `packages/playwright-core/src/server/chromium/crExecutionContext.ts`, `packages/playwright-core/src/server/webkit/wkExecutionContext.ts` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.

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

REDACTED

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

REDACTED

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

REDACTED

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — .NET and JavaScript/TypeScript suite — Coverage NOT MEASURED: the .NET half could not be measured — the repository wires up no coverage collector for `--collect:"XPlat Code Coverage"` to use; 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. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.

R10 · Code Duplication · Duplication concentrated across 9 sibling directories (78 clone groups) · ×1

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

R10 · Code Duplication · Duplication concentrated across 13 sibling directories (32 clone groups) · ×1

Duplication concentrated across 13 sibling directories (32 clone groups) packages/isomorphic/utilityScriptSerializers.ts:253 — 32 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 10 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 5 sibling directories (16 clone groups) · ×1

Duplication concentrated across 5 sibling directories (16 clone groups) packages/playwright-core/src/client/network.ts:234 — 16 duplicated blocks under packages/playwright-core/src/ have copies in at least two of the sibling directories cli, client, remote, server, tools — 9 of them are reported below, and 7 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.

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

Duplication concentrated across 3 sibling directories (6 clone groups) browser_patches/firefox/juggler/NetworkObserver.js:832 — 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.

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

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.

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

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.

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

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.

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

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.

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

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.

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

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.

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

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.

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

Duplicated block (115 lines × 2 locations) packages/playwright-core/src/server/webkit/webview/wvPage.ts:1065 — packages/playwright-core/src/server/webkit/webview/wvPage.ts:1065 · packages/playwright-core/src/server/webkit/wkPage.ts:1093 — 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 (112 lines × 2 locations) · ×1

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.

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

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.

R10 · Code Duplication · Duplicated block with local edits (98 matched lines × 2 locations) · ×1

Duplicated block with local edits (98 matched lines × 2 locations) packages/playwright-core/src/client/browserContext.ts:179 — packages/playwright-core/src/client/browserContext.ts:179 · packages/playwright-core/src/client/page.ts:178 — the two spans are one implementation copied and then locally edited — 780 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

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

Wholesale file copy (88 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 — 88 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

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

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.

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

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.

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

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.

R10 · Code Duplication · Duplicated block with local edits (68 matched lines × 2 locations) · ×1

Duplicated block with local edits (68 matched lines × 2 locations) packages/isomorphic/utilityScriptSerializers.ts:253 — packages/isomorphic/utilityScriptSerializers.ts:253 · packages/protocol/src/serializers.ts:156 — the two spans are one implementation copied and then locally edited — 621 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

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

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.

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

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

Duplicated block with local edits (60 matched lines × 2 locations) utils/build_deps_true.js:31 — utils/build_deps_true.js:31 · utils/check_deps.js:25 — the two spans are one implementation copied and then locally edited — 487 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (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 (53 lines × 2 locations) · ×1

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:366 — packages/playwright-core/src/server/chromium/crBrowser.ts:366 · 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.

R10 · Code Duplication · Duplicated block with local edits (45 matched lines × 2 locations) · ×1

Duplicated block with local edits (45 matched lines × 2 locations) REDACTED:735 — REDACTED:735 · packages/playwright-core/src/server/firefox/ffPage.ts:210 — the two spans are one implementation copied and then locally edited — 347 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (43 lines × 4 locations) · ×1

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

Duplicated block (42 lines × 2 locations) packages/playwright-core/src/tools/cli-client/channelSessions.ts:88 — packages/playwright-core/src/tools/cli-client/channelSessions.ts:88 · packages/utils/chromiumChannels.ts:25 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.

R10 · Code Duplication · Duplicated block with local edits (40 matched lines × 2 locations) · ×1

Duplicated block with local edits (40 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:87 — the two spans are one implementation copied and then locally edited — 261 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 (39 lines × 2 locations) · ×1

Duplicated block (39 lines × 2 locations) packages/playwright-core/src/server/webkit/webview/wvPage.ts:1217 — packages/playwright-core/src/server/webkit/webview/wvPage.ts:1217 · packages/playwright-core/src/server/webkit/wkPage.ts:1301 — 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 (37 lines × 2 locations) · ×1

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.

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

Duplicated block (35 lines × 2 locations) packages/playwright-core/src/client/browserContext.ts:420 — packages/playwright-core/src/client/browserContext.ts:420 · packages/playwright-core/src/client/page.ts:589 — 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 (34 lines × 3 locations) · ×1

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.

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

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:911 — 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 (31 lines × 2 locations) · ×1

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.

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

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.

R2 · Cyclomatic Complexity · Complex function getTextAlternativeInternal (cyclomatic 137, cognitive 232) · ×1

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

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 92, cognitive 118) · ×1

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.

R2 · Cyclomatic Complexity · Complex function generateChannels (cyclomatic 81, cognitive 239) · ×1

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.

R2 · Cyclomatic Complexity · Complex function validateConfig (cyclomatic 79, cognitive 96) · ×1

Complex function validateConfig (cyclomatic 79, cognitive 96) packages/playwright/src/common/configLoader.ts:128 — 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 65, cognitive 79) · ×1

Complex function program (cyclomatic 65, cognitive 79) packages/playwright-core/src/tools/cli-client/program.ts:77 — program has cyclomatic complexity 65 and cognitive complexity 79; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 expectSingleElement (cyclomatic 58, cognitive 81) · ×1

Complex function expectSingleElement (cyclomatic 58, cognitive 81) packages/injected/src/injectedScript.ts:1518 — 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.

R2 · Cyclomatic Complexity · Complex function ansi2html (cyclomatic 56, cognitive 21) · ×1

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.

R2 · Cyclomatic Complexity · Complex function consumeAToken (cyclomatic 49, cognitive 75) · ×1

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.

R2 · Cyclomatic Complexity · Complex function innerAsLocators (cyclomatic 46, cognitive 113) · ×1

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.

R2 · Cyclomatic Complexity · Complex function validateProject (cyclomatic 45, cognitive 57) · ×1

Complex function validateProject (cyclomatic 45, cognitive 57) packages/playwright/src/common/configLoader.ts:258 — validateProject has cyclomatic complexity 45 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.

R2 · Cyclomatic Complexity · Complex function visit (cyclomatic 44, cognitive 72) · ×1

Complex function visit (cyclomatic 44, cognitive 72) packages/isomorphic/trace/snapshotRenderer.ts:89 — 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.

R2 · Cyclomatic Complexity · Complex function innerSerialize (cyclomatic 44, cognitive 62) · ×1

Complex function innerSerialize (cyclomatic 44, cognitive 62) packages/isomorphic/utilityScriptSerializers.ts:253 — innerSerialize has cyclomatic complexity 44 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 innerRenderMdNode (cyclomatic 44, cognitive 42) · ×1

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.

R2 · Cyclomatic Complexity · Complex function translateType (cyclomatic 42, cognitive 68) · ×1

Complex function translateType (cyclomatic 42, cognitive 68) utils/doclint/generateDotnetApi.js:709 — 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.

R2 · Cyclomatic Complexity · Complex function Dashboard (cyclomatic 40, cognitive 37) · ×1

Complex function Dashboard (cyclomatic 40, cognitive 37) packages/dashboard/src/dashboard.tsx: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.

R2 · Cyclomatic Complexity · Complex function generateLocator (cyclomatic 40, cognitive 25) · ×1

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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 39, cognitive 61) · ×1

Complex function (anonymous) (cyclomatic 39, cognitive 61) packages/playwright-core/src/client/fetch.ts:180 — (anonymous) 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.

R2 · Cyclomatic Complexity · Complex function generateLocator (cyclomatic 39, cognitive 31) · ×1

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.

R2 · Cyclomatic Complexity · Complex function compressReports (cyclomatic 37, cognitive 109) · ×1

Complex function compressReports (cyclomatic 37, cognitive 109) utils/flakiness-dashboard/processing/dashboard_compressed_v1.js:33 — compressReports has cyclomatic complexity 37 and cognitive complexity 109; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 _onRequest (cyclomatic 37, cognitive 41) · ×1

Complex function _onRequest (cyclomatic 37, cognitive 41) packages/playwright-core/src/server/chromium/crNetworkManager.ts:282 — _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.

R3 · Large Files · Large Files · ×1

Large Files — 92 file(s) over 400 lines (counted as significant lines — blank lines excluded — over production source only, tests excluded), largest first: packages/injected/src/injectedScript.ts (1743), packages/playwright-core/src/server/frames.ts (1715), packages/injected/src/recorder/recorder.ts (1609), REDACTED (1499), packages/playwright-core/src/tools/cli-daemon/commands.ts (1308), packages/playwright-core/src/server/registry/index.ts (1295) (+86 more).

R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1

The declared test suite includes a file that cannot be loaded tests/config/proxy.ts — This repository declares test tooling, and the ✓ above records that declaration — but tests/config/proxy.ts and 3 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.

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

Dead file (~1346 LoC) browser_patches/firefox/juggler/TargetRegistry.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~1103 LoC) browser_patches/firefox/juggler/NetworkObserver.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~890 LoC) utils/doclint/generateDotnetApi.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~656 LoC) utils/generate_types/index.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~253 LoC) browser_patches/firefox/juggler/SimpleChannel.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~234 LoC) browser_patches/firefox/juggler/Helper.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~169 LoC) utils/doclint/dotnetXmlDocumentation.js — no import path from any entry point (269 application, 82 tooling, 811 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

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

Dead file (~161 LoC) browser_patches/firefox/juggler/components/Juggler.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~139 LoC) utils/generate_types/parseOverrides.js — no import path from any entry point (269 application, 82 tooling, 811 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

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

Dead file (~135 LoC) utils/doclint/generateApiJson.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~116 LoC) utils/generate_chromium_default_font_families.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~112 LoC) browser_patches/firefox/juggler/content/main.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~99 LoC) browser_patches/firefox/juggler/ChannelEventSink.sys.mjs — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~78 LoC) utils/render_release_notes.mjs — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~48 LoC) packages/trace-viewer/src/ui/clickPointer.tsx — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~38 LoC) packages/html-reporter/src/chip.story.tsx — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~37 LoC) packages/dashboard/src/screencast.tsx — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~35 LoC) packages/html-reporter/src/headerView.story.tsx — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~33 LoC) packages/html-reporter/src/testCaseView.story.tsx — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~29 LoC) packages/playwright-client/src/nodeStubs/path.ts — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~27 LoC) packages/playwright-client/src/nodeStubs/async_hooks.ts — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~25 LoC) packages/playwright-client/src/nodeStubs/fs.ts — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~22 LoC) packages/playwright-client/src/nodeStubs/processShim.ts — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~3 LoC) browser_patches/firefox/preferences/00-playwright-prefs.js — no import path from any entry point (269 application, 82 tooling, 811 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R8 · Dependency Hygiene · Unlisted import 'source-map' · ×1

Unlisted import 'source-map' packages/playwright/src/runner/loadUtils.ts:30 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.

R8 · Dependency Hygiene · Unused dependency '@actions/github' · ×1

Unused dependency '@actions/github' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency 'istanbul-lib-instrument' · ×1

Unused dependency 'istanbul-lib-instrument' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency 'yaml' · ×1

Unused dependency 'yaml' — Declared in packages/web/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

SC1 · Supply-chain hygiene · 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.

Minor — 19 finding(s)

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

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 9 significant file(s) lose their only recent owner: packages/playwright/src/reporters/perfetto.ts, packages/trace-viewer/src/ui/filmStrip.tsx, packages/utils/crypto.ts, packages/playwright-core/src/tools/backend/find.ts, packages/playwright-core/src/server/overlay.ts, packages/trace-viewer/src/ui/videoThumbnails.ts, packages/playwright-core/src/server/webkit/webview/syncServer.ts, packages/dashboard/src/transport.ts (+1 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 8 significant file(s) lose their only recent owner: packages/extension/src/relayConnection.ts, packages/extension/src/connectedTabGroup.ts, packages/playwright-core/src/tools/mcp/browserModel.ts, packages/extension/src/background.ts, packages/utils/webp/webp.ts, packages/playwright-core/src/tools/mcp/cdpRelayV2.ts, packages/playwright-core/src/tools/mcp/protocol.ts, packages/extension/src/ui/status.tsx. 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, packages/playwright/src/transform/esmLoaderSync.ts. Pair on, review, or document these before any departure.

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

Further sole-owners (lower concentration) — 3 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 (24 single-owned of 553 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 553 of the 788 production source files in this repository met that bar). They are anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — 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/`.

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

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

REDACTED

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

REDACTED

D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1

Orphaned files with no living knowledge — 11 of 553 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 and example/demo trees and test files identified by path convention, largest first; 553 of the 788 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, browser_patches/firefox/juggler/SimpleChannel.js, browser_patches/firefox/juggler/Helper.js, utils/flakiness-dashboard/processing/dashboard_compressed_v1.js, packages/utils/image_tools/stats.ts, utils/doclint/dotnetXmlDocumentation.js, browser_patches/firefox/juggler/protocol/Dispatcher.js, browser_patches/firefox/juggler/protocol/PrimitiveTypes.js (and 3 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

M2 · Architecture documentation · No ADRs · ×1

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

P2 · Observability · Logging is not universal · ×1

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.

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

No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 72451 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.

P6 · Release Hygiene · No changelog · ×1

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

R7 · Dead Code · Unused export 'CloseIcon' · ×1

Unused export 'CloseIcon' packages/dashboard/src/icons.tsx:78 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'PlusIcon' · ×1

Unused export 'PlusIcon' packages/dashboard/src/icons.tsx:85 — Nothing imports this binding — it is safe to review for removal.

Minor — 628 finding(s)

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

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
Skipped (documented): (unnamed test) tests/config/browserTest.ts:151 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/config/browserTest.ts:167 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/electron/electron-webcontentsview.spec.ts:22 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/electron/electron-tracing.spec.ts:21 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/electron/electron-app.spec.ts:371 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): chromium tests/extension/extension-fixtures.ts:59 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/extension/extension-fixtures.ts:118 — 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/installation/playwright-should-work-with-relative-home-path.spec.ts:20 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/installation/npx-global.spec.ts:35 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/installation/driver-should-work.spec.ts:25 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/installation/connect-to-selenium.spec.ts:21 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/installation/fixture-scripts/playwright-test-types.ts:32 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/library/video.spec.ts:99 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): (unnamed test) tests/library/video.spec.ts:103 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): (unnamed test) tests/library/video.spec.ts:522 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): (unnamed test) tests/library/video.spec.ts:763 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): (unnamed test) tests/library/tracing.spec.ts:26 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/library/trace-viewer.spec.ts:34 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/library/trace-viewer.spec.ts:35 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/library/trace-viewer.spec.ts:522 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/library/trace-viewer.spec.ts:1173 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/library/trace-viewer.spec.ts:1196 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/library/trace-viewer.spec.ts:1824 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): (unnamed test) tests/library/trace-viewer.spec.ts:2083 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
+ 603 more in this group — see findings.md.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6f506e33eecd43d99f69668ffa67d5f1/history.json --exit-code 0 --source .	2	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6f506e33eecd43d99f69668ffa67d5f1/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	36	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	nuget	—	nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan	0	—
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	11	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	24	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 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.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	nuget	—	nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a0e58c-76e4-7007-8667-10f5b0d18028 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Microsoft/playwright

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency matrix

At a glance — Code Health · 71% · Adequate · gated by D2 ·

At a glance — Architecture · 60% · Adequate · gated by R9 ·

At a glance — Maturity · 80% · Strong ·

At a glance — Readiness · 54% · Adequate · gated by P3 ·

At a glance — Security · 65% · Adequate · gated by D29, D36 ·

At a glance — Accessibility · 41% · Weak · gated by AC4 ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts