Public report of SeleniumHQ/selenium, published 13 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 13 November 2026, 13:34 UTC · Survey ID cd_026a9672b3ea44bab372d80ee4810da3
SeleniumHQ/selenium
Measured 13 November 2026, 13:30 UTC, at code version 72e603c
Code coverage is not measured: .NET and JavaScript/TypeScript suite (CouldNotMeasureNoCollector, CouldNotMeasureTestRunFailed).
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 283,447 lines of product code in 12 projects, tests not counted · Estimated rebuild effort: about 3.2 person-years · Weakest lens: Code Health, 49
Findings by how serious they are
190 critical1394 serious145 minor
23 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 13:30 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
64of 64 dimensions measured by tools.
1704of 1729 findings point to an exact file and line, so you can open each one in the code. The other 25 concern the repository as a whole, such as missing documentation.
64dimensions across 7 lenses, read from 283,447 lines of product code in 12 projects.
SeleniumHQ/selenium falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 54 out of 100 and is rated Adequate, and 169 of its 190 critical findings are security problems.
Code Health, at 49, is the weakest lens and counts most in the score. The best first step is handling the discarded errors, worth about 4 points. Removing the unused code would lift Code Health itself, worth about 3 points. Raising Code Health to 70 would lift the score to about 58.
100 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-six secrets can leak from the build pipeline, and ten settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Passing outside input through environment variables would fix the nine pipeline steps that put outside input straight into a shell command, and updating the vulnerable packages would deal with the six packages with a known security hole. The 18 errors that are caught and ignored need handling or logging instead of being ignored.
The product code is 283,447 lines, about €460,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Code Health rose from 49 to 70, the lowest score rated Strong, the score would rise from 54 to about 58.
Code composition: what the lines of code are
Business logic 4%Supporting code 9%Tests 87%
New since the last survey: 400 findings
These 400 critical or serious findings weren't in the previous survey, on 24 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · FunctionTooLong: roles.implicitRole javascript/atoms/typescript/core/accessibility/roles.ts
God Classes · ClassTooLong: JsonInput java/src/org/openqa/selenium/json/JsonInput.java
Code Duplication · Near-duplicate member pair (45 shared lines) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java
Code Duplication · Edited copy of a member (43 corresponding lines) java/src/org/openqa/selenium/bidi/BiDiGenerator.java
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) java/src/org/openqa/selenium/bidi/BiDiGenerator.java
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) rust/src/chrome.rs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) java/src/org/openqa/selenium/ImmutableCapabilities.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) java/src/org/openqa/selenium/bidi/module/Script.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java
Code Duplication · Edited copy of a member (113 corresponding lines) java/src/org/openqa/selenium/grid/commands/Hub.java
Code Duplication · Edited copy of a member (92 corresponding lines) java/src/org/openqa/selenium/docker/client/V148Adapter.java
Code Duplication · Edited copy of a member (60 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java
Code Duplication · Edited copy of a member (52 corresponding lines) java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java
Code Duplication · Edited copy of a member (54 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java
Code Duplication · Edited copy of a member (48 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java
Code Duplication · Edited copy of a member (46 corresponding lines) java/src/org/openqa/selenium/bidi/Connection.java
Code Duplication · Edited copy of a member (42 corresponding lines) java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java
Code Duplication · Edited copy of a member (54 corresponding lines) java/src/org/openqa/selenium/grid/graphql/Types.java
Code Duplication · Edited copy of a member (35 corresponding lines) java/src/org/openqa/selenium/chrome/ChromeDriverService.java
Code Duplication · Edited copy of a member (46 corresponding lines) java/src/org/openqa/selenium/net/UrlChecker.java
Code Duplication · Edited copies of one member (3 members, 38+ corresponding lines) java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java
Code Duplication · Edited copies of one member (3 members, 32+ corresponding lines) java/src/org/openqa/selenium/devtools/v155/v155Events.java
Code Duplication · Edited copies of one member (4 members, 49+ corresponding lines) java/src/org/openqa/selenium/bidi/log/ConsoleLogEntry.java
Code Duplication · Edited copy of a member (31 corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerOptions.java
Code Duplication · Edited copy of a member (47 corresponding lines) java/src/org/openqa/selenium/grid/distributor/httpd/DistributorServer.java
Code Duplication · Edited copy of a member (36 corresponding lines) java/src/org/openqa/selenium/remote/ElementLocation.java
Code Duplication · Edited copies of one member (3 members, 45+ corresponding lines) java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java
Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java
Code Duplication · Edited copy of a member (37 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java
Code Duplication · Edited copies of one member (3 members, 43+ corresponding lines) java/src/org/openqa/selenium/grid/data/SessionClosedData.java
Code Duplication · Edited copy of a member (40 corresponding lines) java/src/org/openqa/selenium/devtools/idealized/target/model/TargetInfo.java
Code Duplication · Edited copy of a member (26 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java
Code Duplication · Edited copy of a member (36 corresponding lines) py/generate_bidi.py
Code Duplication · Edited copy of a member (27 corresponding lines) java/src/org/openqa/selenium/grid/data/DefaultSlotMatcher.java
Code Duplication · Edited copy of a member (34 corresponding lines) rb/support/rbs_collection_update.rb
Code Duplication · Edited copy of a member (18 corresponding lines) java/src/org/openqa/selenium/firefox/FirefoxOptions.java
Code Duplication · Edited copy of a member (36 corresponding lines) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java
Code Duplication · Edited copy of a member (18 corresponding lines) java/src/org/openqa/selenium/bidi/module/Script.java
Code Duplication · Edited copy of a member (24 corresponding lines) java/src/org/openqa/selenium/remote/NewSessionPayload.java
Code Duplication · Edited copies of one member (3 members, 34+ corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java
Code Duplication · Edited copy of a member (34 corresponding lines) java/src/org/openqa/selenium/bidi/browsingcontext/UserPromptOpened.java
Code Duplication · Edited copy of a member (18 corresponding lines) rust/src/rules.rs
Code Duplication · Edited copy of a member (23 corresponding lines) java/src/org/openqa/selenium/grid/distributor/selector/DefaultSlotSelector.java
Code Duplication · Edited copy of a member (38 corresponding lines) REDACTED
Code Duplication · Edited copy of a member (19 corresponding lines) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java
Code Duplication · Edited copy of a member (20 corresponding lines) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java
Code Duplication · Edited copy of a member (14 corresponding lines) java/src/org/openqa/selenium/bidi/BiDiGenerator.java
Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) java/src/org/openqa/selenium/devtools/v155/v155Target.java
Code Duplication · Edited copy of a member (25 corresponding lines) java/src/org/openqa/selenium/json/InstanceCoercer.java
Code Duplication · Edited copy of a member (16 corresponding lines) py/private/_network_handlers.py
Code Duplication · Edited copy of a member (24 corresponding lines) java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java
Code Duplication · Edited copy of a member (31 corresponding lines) dotnet/src/webdriver/IE/InternetExplorerDriver.cs
Code Duplication · Edited copy of a member (26 corresponding lines) java/src/org/openqa/selenium/docker/client/V140Adapter.java
Code Duplication · Edited copies of one member (4 members, 32+ corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java
Code Duplication · Edited copy of a member (18 corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java
Code Duplication · Edited copy of a member (15 corresponding lines) java/src/org/openqa/selenium/bidi/BiDiGenerator.java
Code Duplication · Edited copy of a member (28 corresponding lines) rust/src/edge.rs
Code Duplication · Edited copy of a member (28 corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java
Code Duplication · Edited copy of a member (26 corresponding lines) dotnet/src/webdriver/Interactions/PointerInputDevice.cs
Code Duplication · Edited copy of a member (17 corresponding lines) java/src/org/openqa/selenium/bidi/Connection.java
Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) dotnet/src/support/Events/EventFiringWebDriver.cs
Code Duplication · Edited copy of a member (16 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java
Code Duplication · Edited copy of a member (13 corresponding lines) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java
Code Duplication · Edited copy of a member (14 corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java
Code Duplication · Edited copy of a member (12 corresponding lines) java/src/org/openqa/selenium/firefox/FirefoxOptions.java
Code Duplication · Edited copy of a member (29 corresponding lines) java/src/org/openqa/selenium/grid/data/NewSessionResponse.java
Code Duplication · Edited copy of a member (18 corresponding lines) java/src/org/openqa/selenium/grid/jmx/MBean.java
Code Duplication · Edited copy of a member (17 corresponding lines) dotnet/src/webdriver/Interactions/Actions.cs
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 449 findings
These 449 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one. The first 100 are listed here.
€150,000 to €770,000, for 2,559 to 8,126 hours of work, about 3.2 person-years for 1 to 7 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 283,447 lines of product code
Comment lines
The estimate prices 260,556 lines. Comment lines count towards the size of 283,447 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 18 EmptyCatchBlock finding(s) in Explicit Debt — start with WebDriver.cs (7), SeleniumManager.cs (4), ChromiumDriver.cs.
Raises the score by about 4 points · Medium effort · Explicit Debt
2
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
Raises the score by about 3 points · Medium effort · Dead Code
3
Resolve the 1 finding(s) in Type Safety.
Raises the score by about 3 points · Medium effort · Type Safety
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €460,000 to build again, about 3.2 person-years of work. Its weakest lens is Code Health, at 49 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 18 EmptyCatchBlock finding(s) in Explicit Debt. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for medium effort, because it clears the 18 Explicit Debt findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
564 modules, with 808 dependencies between them. 6 loops run through 40 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 524 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
OpenQA.Selenium.BiDi.Browser uses OpenQA.Selenium.BiDi, so a change to OpenQA.Selenium.BiDi can break OpenQA.Selenium.BiDi.Browser, while a change to OpenQA.Selenium.BiDi.Browser can't break OpenQA.Selenium.BiDi.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.openqa.selenium.json uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.json, while a change to org.openqa.selenium.json can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.json uses a module listed above it, which is the healthy direction.
py.selenium.webdriver.remote.webdriver uses py.selenium.webdriver.remote.webelement, so a change to py.selenium.webdriver.remote.webelement can break py.selenium.webdriver.remote.webdriver, while a change to py.selenium.webdriver.remote.webdriver can't break py.selenium.webdriver.remote.webelement.
Position
Below the diagonal: py.selenium.webdriver.remote.webdriver uses a module listed above it, which is the healthy direction.
30 pairs of types, where a type in OpenQA.Selenium.BiDi.BrowsingContext uses a type in OpenQA.Selenium.BiDi.Browser. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
OpenQA.Selenium.BiDi.BrowsingContext uses OpenQA.Selenium.BiDi.Browser, so a change to OpenQA.Selenium.BiDi.Browser can break OpenQA.Selenium.BiDi.BrowsingContext, while a change to OpenQA.Selenium.BiDi.BrowsingContext can't break OpenQA.Selenium.BiDi.Browser.
Position
Below the diagonal: OpenQA.Selenium.BiDi.BrowsingContext uses a module listed above it, which is the healthy direction.
10→15 OpenQA.Selenium.BiDi.BrowsingContext uses OpenQA.Selenium.BiDipart of a loop✕
Connections
94 pairs of types, where a type in OpenQA.Selenium.BiDi.BrowsingContext uses a type in OpenQA.Selenium.BiDi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
OpenQA.Selenium.BiDi.BrowsingContext uses OpenQA.Selenium.BiDi, so a change to OpenQA.Selenium.BiDi can break OpenQA.Selenium.BiDi.BrowsingContext, while a change to OpenQA.Selenium.BiDi.BrowsingContext can't break OpenQA.Selenium.BiDi.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.openqa.selenium.bidi.module uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.bidi.module, while a change to org.openqa.selenium.bidi.module can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.bidi.module uses a module listed above it, which is the healthy direction.
org.openqa.selenium.bidi.module uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.bidi.module, while a change to org.openqa.selenium.bidi.module can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.bidi.module uses a module listed above it, which is the healthy direction.
11→23 org.openqa.selenium.bidi.module uses org.openqa.selenium.bidipart of a loop✕
Connections
14 pairs of types, where a type in org.openqa.selenium.bidi.module uses a type in org.openqa.selenium.bidi.
org.openqa.selenium.bidi.module uses org.openqa.selenium.bidi, so a change to org.openqa.selenium.bidi can break org.openqa.selenium.bidi.module, while a change to org.openqa.selenium.bidi.module can't break org.openqa.selenium.bidi.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.openqa.selenium.events uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.events, while a change to org.openqa.selenium.events can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.events uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.config uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.config, while a change to org.openqa.selenium.grid.config can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.remote.http uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.remote.http, while a change to org.openqa.selenium.remote.http can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.remote.http uses a module listed above it, which is the healthy direction.
org.openqa.selenium.remote.http uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.remote.http, while a change to org.openqa.selenium.remote.http can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.remote.http uses a module listed above it, which is the healthy direction.
OpenQA.Selenium.BiDi uses OpenQA.Selenium.BiDi.Browser, so a change to OpenQA.Selenium.BiDi.Browser can break OpenQA.Selenium.BiDi, while a change to OpenQA.Selenium.BiDi can't break OpenQA.Selenium.BiDi.Browser.
Position
Below the diagonal: OpenQA.Selenium.BiDi uses a module listed above it, which is the healthy direction.
OpenQA.Selenium.BiDi uses OpenQA.Selenium.BiDi.BrowsingContext, so a change to OpenQA.Selenium.BiDi.BrowsingContext can break OpenQA.Selenium.BiDi, while a change to OpenQA.Selenium.BiDi can't break OpenQA.Selenium.BiDi.BrowsingContext.
Position
Below the diagonal: OpenQA.Selenium.BiDi uses a module listed above it, which is the healthy direction.
15→21 OpenQA.Selenium.BiDi uses OpenQA.Seleniumpart of a loop✕
Connections
1 pair of types, where a type in OpenQA.Selenium.BiDi uses a type in OpenQA.Selenium.
OpenQA.Selenium.BiDi uses OpenQA.Selenium, so a change to OpenQA.Selenium can break OpenQA.Selenium.BiDi, while a change to OpenQA.Selenium.BiDi can't break OpenQA.Selenium.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.openqa.selenium.devtools.idealized uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.devtools.idealized, while a change to org.openqa.selenium.devtools.idealized can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.devtools.idealized uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.idealized uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.devtools.idealized, while a change to org.openqa.selenium.devtools.idealized can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.devtools.idealized uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.idealized uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.devtools.idealized, while a change to org.openqa.selenium.devtools.idealized can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.devtools.idealized uses a module listed above it, which is the healthy direction.
16→24 org.openqa.selenium.devtools.idealized uses org.openqa.selenium.devtoolspart of a loop✕
Connections
9 pairs of types, where a type in org.openqa.selenium.devtools.idealized uses a type in org.openqa.selenium.devtools.
org.openqa.selenium.devtools.idealized uses org.openqa.selenium.devtools, so a change to org.openqa.selenium.devtools can break org.openqa.selenium.devtools.idealized, while a change to org.openqa.selenium.devtools.idealized can't break org.openqa.selenium.devtools.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.openqa.selenium.grid uses org.openqa.selenium.grid.config, so a change to org.openqa.selenium.grid.config can break org.openqa.selenium.grid, while a change to org.openqa.selenium.grid can't break org.openqa.selenium.grid.config.
Position
Below the diagonal: org.openqa.selenium.grid uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid, while a change to org.openqa.selenium.grid can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.security uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.security, while a change to org.openqa.selenium.grid.security can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.security uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.security uses org.openqa.selenium.grid.config, so a change to org.openqa.selenium.grid.config can break org.openqa.selenium.grid.security, while a change to org.openqa.selenium.grid.security can't break org.openqa.selenium.grid.config.
Position
Below the diagonal: org.openqa.selenium.grid.security uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.security uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.security, while a change to org.openqa.selenium.grid.security can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.security uses a module listed above it, which is the healthy direction.
org.openqa.selenium.remote.service uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.remote.service, while a change to org.openqa.selenium.remote.service can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.remote.service uses a module listed above it, which is the healthy direction.
org.openqa.selenium.remote.service uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.remote.service, while a change to org.openqa.selenium.remote.service can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.remote.service uses a module listed above it, which is the healthy direction.
19→22 org.openqa.selenium.remote.service uses org.openqa.selenium.remotepart of a loop✕
Connections
4 pairs of types, where a type in org.openqa.selenium.remote.service uses a type in org.openqa.selenium.remote.
org.openqa.selenium.remote.service uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.remote.service, while a change to org.openqa.selenium.remote.service can't break org.openqa.selenium.remote.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.openqa.selenium.remote.tracing uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.remote.tracing, while a change to org.openqa.selenium.remote.tracing can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.remote.tracing uses a module listed above it, which is the healthy direction.
OpenQA.Selenium uses OpenQA.Selenium.BiDi.BrowsingContext, so a change to OpenQA.Selenium.BiDi.BrowsingContext can break OpenQA.Selenium, while a change to OpenQA.Selenium can't break OpenQA.Selenium.BiDi.BrowsingContext.
Position
Below the diagonal: OpenQA.Selenium uses a module listed above it, which is the healthy direction.
OpenQA.Selenium uses OpenQA.Selenium.BiDi, so a change to OpenQA.Selenium.BiDi can break OpenQA.Selenium, while a change to OpenQA.Selenium can't break OpenQA.Selenium.BiDi.
Position
Below the diagonal: OpenQA.Selenium uses a module listed above it, which is the healthy direction.
109 pairs of types, where a type in org.openqa.selenium.remote uses a type in org.openqa.selenium. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
org.openqa.selenium.remote uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.remote, while a change to org.openqa.selenium.remote can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.remote uses a module listed above it, which is the healthy direction.
org.openqa.selenium.remote uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.remote, while a change to org.openqa.selenium.remote can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.remote uses a module listed above it, which is the healthy direction.
org.openqa.selenium.remote uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.remote, while a change to org.openqa.selenium.remote can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.remote uses a module listed above it, which is the healthy direction.
org.openqa.selenium.remote uses org.openqa.selenium.bidi.module, so a change to org.openqa.selenium.bidi.module can break org.openqa.selenium.remote, while a change to org.openqa.selenium.remote can't break org.openqa.selenium.bidi.module.
Position
Below the diagonal: org.openqa.selenium.remote uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in org.openqa.selenium.remote uses a type in org.openqa.selenium.remote.http. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
org.openqa.selenium.remote uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.remote, while a change to org.openqa.selenium.remote can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.remote uses a module listed above it, which is the healthy direction.
org.openqa.selenium.remote uses org.openqa.selenium.remote.service, so a change to org.openqa.selenium.remote.service can break org.openqa.selenium.remote, while a change to org.openqa.selenium.remote can't break org.openqa.selenium.remote.service.
Position
Below the diagonal: org.openqa.selenium.remote uses a module listed above it, which is the healthy direction.
org.openqa.selenium.remote uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.remote, while a change to org.openqa.selenium.remote can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.remote uses a module listed above it, which is the healthy direction.
22→23 org.openqa.selenium.remote uses org.openqa.selenium.bidipart of a loop✕
Connections
5 pairs of types, where a type in org.openqa.selenium.remote uses a type in org.openqa.selenium.bidi.
org.openqa.selenium.remote uses org.openqa.selenium.bidi, so a change to org.openqa.selenium.bidi can break org.openqa.selenium.remote, while a change to org.openqa.selenium.remote can't break org.openqa.selenium.bidi.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.openqa.selenium.bidi uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.bidi, while a change to org.openqa.selenium.bidi can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.bidi uses a module listed above it, which is the healthy direction.
org.openqa.selenium.bidi uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.bidi, while a change to org.openqa.selenium.bidi can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.bidi uses a module listed above it, which is the healthy direction.
org.openqa.selenium.bidi uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.bidi, while a change to org.openqa.selenium.bidi can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.bidi uses a module listed above it, which is the healthy direction.
org.openqa.selenium.bidi uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.bidi, while a change to org.openqa.selenium.bidi can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.bidi uses a module listed above it, which is the healthy direction.
org.openqa.selenium.bidi uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.bidi, while a change to org.openqa.selenium.bidi can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.bidi uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.devtools, while a change to org.openqa.selenium.devtools can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.devtools uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.devtools, while a change to org.openqa.selenium.devtools can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.devtools uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.devtools, while a change to org.openqa.selenium.devtools can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.devtools uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.devtools, while a change to org.openqa.selenium.devtools can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.devtools uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools uses org.openqa.selenium.devtools.idealized, so a change to org.openqa.selenium.devtools.idealized can break org.openqa.selenium.devtools, while a change to org.openqa.selenium.devtools can't break org.openqa.selenium.devtools.idealized.
Position
Below the diagonal: org.openqa.selenium.devtools uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.devtools, while a change to org.openqa.selenium.devtools can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.devtools uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.data uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.data, while a change to org.openqa.selenium.grid.data can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.data uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.data uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.data, while a change to org.openqa.selenium.grid.data can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.data uses a module listed above it, which is the healthy direction.
35 pairs of types, where a type in org.openqa.selenium.grid.data uses a type in org.openqa.selenium.events. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
org.openqa.selenium.grid.data uses org.openqa.selenium.events, so a change to org.openqa.selenium.events can break org.openqa.selenium.grid.data, while a change to org.openqa.selenium.grid.data can't break org.openqa.selenium.events.
Position
Below the diagonal: org.openqa.selenium.grid.data uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.data uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.data, while a change to org.openqa.selenium.grid.data can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.data uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.data uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.data, while a change to org.openqa.selenium.grid.data can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.data uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.data uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.data, while a change to org.openqa.selenium.grid.data can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.data uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v155 uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.devtools.v155, while a change to org.openqa.selenium.devtools.v155 can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.devtools.v155 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v155 uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.devtools.v155, while a change to org.openqa.selenium.devtools.v155 can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.devtools.v155 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v155 uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.devtools.v155, while a change to org.openqa.selenium.devtools.v155 can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.devtools.v155 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v155 uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.devtools.v155, while a change to org.openqa.selenium.devtools.v155 can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.devtools.v155 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v155 uses org.openqa.selenium.devtools.idealized, so a change to org.openqa.selenium.devtools.idealized can break org.openqa.selenium.devtools.v155, while a change to org.openqa.selenium.devtools.v155 can't break org.openqa.selenium.devtools.idealized.
Position
Below the diagonal: org.openqa.selenium.devtools.v155 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v155 uses org.openqa.selenium.devtools, so a change to org.openqa.selenium.devtools can break org.openqa.selenium.devtools.v155, while a change to org.openqa.selenium.devtools.v155 can't break org.openqa.selenium.devtools.
Position
Below the diagonal: org.openqa.selenium.devtools.v155 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v156 uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.devtools.v156, while a change to org.openqa.selenium.devtools.v156 can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.devtools.v156 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v156 uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.devtools.v156, while a change to org.openqa.selenium.devtools.v156 can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.devtools.v156 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v156 uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.devtools.v156, while a change to org.openqa.selenium.devtools.v156 can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.devtools.v156 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v156 uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.devtools.v156, while a change to org.openqa.selenium.devtools.v156 can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.devtools.v156 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v156 uses org.openqa.selenium.devtools.idealized, so a change to org.openqa.selenium.devtools.idealized can break org.openqa.selenium.devtools.v156, while a change to org.openqa.selenium.devtools.v156 can't break org.openqa.selenium.devtools.idealized.
Position
Below the diagonal: org.openqa.selenium.devtools.v156 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v156 uses org.openqa.selenium.devtools, so a change to org.openqa.selenium.devtools can break org.openqa.selenium.devtools.v156, while a change to org.openqa.selenium.devtools.v156 can't break org.openqa.selenium.devtools.
Position
Below the diagonal: org.openqa.selenium.devtools.v156 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v157 uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.devtools.v157, while a change to org.openqa.selenium.devtools.v157 can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.devtools.v157 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v157 uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.devtools.v157, while a change to org.openqa.selenium.devtools.v157 can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.devtools.v157 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v157 uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.devtools.v157, while a change to org.openqa.selenium.devtools.v157 can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.devtools.v157 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v157 uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.devtools.v157, while a change to org.openqa.selenium.devtools.v157 can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.devtools.v157 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v157 uses org.openqa.selenium.devtools.idealized, so a change to org.openqa.selenium.devtools.idealized can break org.openqa.selenium.devtools.v157, while a change to org.openqa.selenium.devtools.v157 can't break org.openqa.selenium.devtools.idealized.
Position
Below the diagonal: org.openqa.selenium.devtools.v157 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.devtools.v157 uses org.openqa.selenium.devtools, so a change to org.openqa.selenium.devtools can break org.openqa.selenium.devtools.v157, while a change to org.openqa.selenium.devtools.v157 can't break org.openqa.selenium.devtools.
Position
Below the diagonal: org.openqa.selenium.devtools.v157 uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.node, while a change to org.openqa.selenium.grid.node can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.node uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.grid.node, while a change to org.openqa.selenium.grid.node can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.grid.node uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.node, while a change to org.openqa.selenium.grid.node can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.node uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node uses org.openqa.selenium.events, so a change to org.openqa.selenium.events can break org.openqa.selenium.grid.node, while a change to org.openqa.selenium.grid.node can't break org.openqa.selenium.events.
Position
Below the diagonal: org.openqa.selenium.grid.node uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node uses org.openqa.selenium.grid.config, so a change to org.openqa.selenium.grid.config can break org.openqa.selenium.grid.node, while a change to org.openqa.selenium.grid.node can't break org.openqa.selenium.grid.config.
Position
Below the diagonal: org.openqa.selenium.grid.node uses a module listed above it, which is the healthy direction.
63 pairs of types, where a type in org.openqa.selenium.grid.node uses a type in org.openqa.selenium.remote.http. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
org.openqa.selenium.grid.node uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.node, while a change to org.openqa.selenium.grid.node can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.node uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node uses org.openqa.selenium.grid.security, so a change to org.openqa.selenium.grid.security can break org.openqa.selenium.grid.node, while a change to org.openqa.selenium.grid.node can't break org.openqa.selenium.grid.security.
Position
Below the diagonal: org.openqa.selenium.grid.node uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.node, while a change to org.openqa.selenium.grid.node can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.node uses a module listed above it, which is the healthy direction.
30 pairs of types, where a type in org.openqa.selenium.grid.node uses a type in org.openqa.selenium.remote. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
org.openqa.selenium.grid.node uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.node, while a change to org.openqa.selenium.grid.node can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.node uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.node, while a change to org.openqa.selenium.grid.node can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.node uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionmap uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.sessionmap, while a change to org.openqa.selenium.grid.sessionmap can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.sessionmap uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionmap uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.sessionmap, while a change to org.openqa.selenium.grid.sessionmap can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.sessionmap uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionmap uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.sessionmap, while a change to org.openqa.selenium.grid.sessionmap can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.sessionmap uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionmap uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.sessionmap, while a change to org.openqa.selenium.grid.sessionmap can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.sessionmap uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionmap uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.sessionmap, while a change to org.openqa.selenium.grid.sessionmap can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.sessionmap uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.sessionqueue, while a change to org.openqa.selenium.grid.sessionqueue can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.grid.sessionqueue, while a change to org.openqa.selenium.grid.sessionqueue can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.sessionqueue, while a change to org.openqa.selenium.grid.sessionqueue can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in org.openqa.selenium.grid.sessionqueue uses a type in org.openqa.selenium.remote.http. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
org.openqa.selenium.grid.sessionqueue uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.sessionqueue, while a change to org.openqa.selenium.grid.sessionqueue can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue uses org.openqa.selenium.grid.security, so a change to org.openqa.selenium.grid.security can break org.openqa.selenium.grid.sessionqueue, while a change to org.openqa.selenium.grid.sessionqueue can't break org.openqa.selenium.grid.security.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.sessionqueue, while a change to org.openqa.selenium.grid.sessionqueue can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.sessionqueue, while a change to org.openqa.selenium.grid.sessionqueue can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.distributor, while a change to org.openqa.selenium.grid.distributor can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.distributor uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.grid.distributor, while a change to org.openqa.selenium.grid.distributor can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.grid.distributor uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.distributor, while a change to org.openqa.selenium.grid.distributor can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.distributor uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.distributor, while a change to org.openqa.selenium.grid.distributor can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.distributor uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor uses org.openqa.selenium.grid.security, so a change to org.openqa.selenium.grid.security can break org.openqa.selenium.grid.distributor, while a change to org.openqa.selenium.grid.distributor can't break org.openqa.selenium.grid.security.
Position
Below the diagonal: org.openqa.selenium.grid.distributor uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.distributor, while a change to org.openqa.selenium.grid.distributor can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.distributor uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.distributor, while a change to org.openqa.selenium.grid.distributor can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.distributor uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.distributor, while a change to org.openqa.selenium.grid.distributor can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.distributor uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor uses org.openqa.selenium.grid.node, so a change to org.openqa.selenium.grid.node can break org.openqa.selenium.grid.distributor, while a change to org.openqa.selenium.grid.distributor can't break org.openqa.selenium.grid.node.
Position
Below the diagonal: org.openqa.selenium.grid.distributor uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.config uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.node.config, while a change to org.openqa.selenium.grid.node.config can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.node.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.config uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.grid.node.config, while a change to org.openqa.selenium.grid.node.config can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.grid.node.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.config uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.node.config, while a change to org.openqa.selenium.grid.node.config can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.node.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.config uses org.openqa.selenium.grid.config, so a change to org.openqa.selenium.grid.config can break org.openqa.selenium.grid.node.config, while a change to org.openqa.selenium.grid.node.config can't break org.openqa.selenium.grid.config.
Position
Below the diagonal: org.openqa.selenium.grid.node.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.config uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.node.config, while a change to org.openqa.selenium.grid.node.config can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.node.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.config uses org.openqa.selenium.remote.service, so a change to org.openqa.selenium.remote.service can break org.openqa.selenium.grid.node.config, while a change to org.openqa.selenium.grid.node.config can't break org.openqa.selenium.remote.service.
Position
Below the diagonal: org.openqa.selenium.grid.node.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.config uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.node.config, while a change to org.openqa.selenium.grid.node.config can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.node.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.config uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.node.config, while a change to org.openqa.selenium.grid.node.config can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.node.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.config uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.node.config, while a change to org.openqa.selenium.grid.node.config can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.node.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.config uses org.openqa.selenium.grid.node, so a change to org.openqa.selenium.grid.node can break org.openqa.selenium.grid.node.config, while a change to org.openqa.selenium.grid.node.config can't break org.openqa.selenium.grid.node.
Position
Below the diagonal: org.openqa.selenium.grid.node.config uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium.events, so a change to org.openqa.selenium.events can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.events.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium.grid.config, so a change to org.openqa.selenium.grid.config can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.grid.config.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium.grid.security, so a change to org.openqa.selenium.grid.security can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.grid.security.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.k8s uses org.openqa.selenium.grid.node, so a change to org.openqa.selenium.grid.node can break org.openqa.selenium.grid.node.k8s, while a change to org.openqa.selenium.grid.node.k8s can't break org.openqa.selenium.grid.node.
Position
Below the diagonal: org.openqa.selenium.grid.node.k8s uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.events, so a change to org.openqa.selenium.events can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.events.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.grid.config, so a change to org.openqa.selenium.grid.config can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.grid.config.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.grid.security, so a change to org.openqa.selenium.grid.security can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.grid.security.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.remote.service, so a change to org.openqa.selenium.remote.service can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.remote.service.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.local uses org.openqa.selenium.grid.node, so a change to org.openqa.selenium.grid.node can break org.openqa.selenium.grid.node.local, while a change to org.openqa.selenium.grid.node.local can't break org.openqa.selenium.grid.node.
Position
Below the diagonal: org.openqa.selenium.grid.node.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue.redis uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.sessionqueue.redis, while a change to org.openqa.selenium.grid.sessionqueue.redis can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue.redis uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.grid.sessionqueue.redis, while a change to org.openqa.selenium.grid.sessionqueue.redis can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue.redis uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.sessionqueue.redis, while a change to org.openqa.selenium.grid.sessionqueue.redis can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue.redis uses org.openqa.selenium.grid.config, so a change to org.openqa.selenium.grid.config can break org.openqa.selenium.grid.sessionqueue.redis, while a change to org.openqa.selenium.grid.sessionqueue.redis can't break org.openqa.selenium.grid.config.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue.redis uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.sessionqueue.redis, while a change to org.openqa.selenium.grid.sessionqueue.redis can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue.redis uses org.openqa.selenium.grid.security, so a change to org.openqa.selenium.grid.security can break org.openqa.selenium.grid.sessionqueue.redis, while a change to org.openqa.selenium.grid.sessionqueue.redis can't break org.openqa.selenium.grid.security.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue.redis uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.sessionqueue.redis, while a change to org.openqa.selenium.grid.sessionqueue.redis can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue.redis uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.sessionqueue.redis, while a change to org.openqa.selenium.grid.sessionqueue.redis can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.sessionqueue.redis uses org.openqa.selenium.grid.sessionqueue, so a change to org.openqa.selenium.grid.sessionqueue can break org.openqa.selenium.grid.sessionqueue.redis, while a change to org.openqa.selenium.grid.sessionqueue.redis can't break org.openqa.selenium.grid.sessionqueue.
Position
Below the diagonal: org.openqa.selenium.grid.sessionqueue.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.events, so a change to org.openqa.selenium.events can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.events.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.grid.config, so a change to org.openqa.selenium.grid.config can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.grid.config.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.grid.security, so a change to org.openqa.selenium.grid.security can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.grid.security.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.grid.node, so a change to org.openqa.selenium.grid.node can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.grid.node.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.grid.sessionmap, so a change to org.openqa.selenium.grid.sessionmap can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.grid.sessionmap.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.grid.sessionqueue, so a change to org.openqa.selenium.grid.sessionqueue can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.grid.sessionqueue.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.local uses org.openqa.selenium.grid.distributor, so a change to org.openqa.selenium.grid.distributor can break org.openqa.selenium.grid.distributor.local, while a change to org.openqa.selenium.grid.distributor.local can't break org.openqa.selenium.grid.distributor.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.local uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.events, so a change to org.openqa.selenium.events can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.events.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.grid.config, so a change to org.openqa.selenium.grid.config can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.grid.config.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.grid.security, so a change to org.openqa.selenium.grid.security can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.grid.security.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.grid.node, so a change to org.openqa.selenium.grid.node can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.grid.node.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.grid.sessionmap, so a change to org.openqa.selenium.grid.sessionmap can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.grid.sessionmap.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.grid.sessionqueue, so a change to org.openqa.selenium.grid.sessionqueue can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.grid.sessionqueue.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.distributor.redis uses org.openqa.selenium.grid.distributor, so a change to org.openqa.selenium.grid.distributor can break org.openqa.selenium.grid.distributor.redis, while a change to org.openqa.selenium.grid.distributor.redis can't break org.openqa.selenium.grid.distributor.
Position
Below the diagonal: org.openqa.selenium.grid.distributor.redis uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.docker uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.node.docker, while a change to org.openqa.selenium.grid.node.docker can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.node.docker uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.docker uses org.openqa.selenium.internal, so a change to org.openqa.selenium.internal can break org.openqa.selenium.grid.node.docker, while a change to org.openqa.selenium.grid.node.docker can't break org.openqa.selenium.internal.
Position
Below the diagonal: org.openqa.selenium.grid.node.docker uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.docker uses org.openqa.selenium.json, so a change to org.openqa.selenium.json can break org.openqa.selenium.grid.node.docker, while a change to org.openqa.selenium.grid.node.docker can't break org.openqa.selenium.json.
Position
Below the diagonal: org.openqa.selenium.grid.node.docker uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.docker uses org.openqa.selenium.grid.config, so a change to org.openqa.selenium.grid.config can break org.openqa.selenium.grid.node.docker, while a change to org.openqa.selenium.grid.node.docker can't break org.openqa.selenium.grid.config.
Position
Below the diagonal: org.openqa.selenium.grid.node.docker uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.docker uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.node.docker, while a change to org.openqa.selenium.grid.node.docker can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.node.docker uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.docker uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.node.docker, while a change to org.openqa.selenium.grid.node.docker can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.node.docker uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.docker uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.node.docker, while a change to org.openqa.selenium.grid.node.docker can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.node.docker uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.docker uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.node.docker, while a change to org.openqa.selenium.grid.node.docker can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.node.docker uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.docker uses org.openqa.selenium.grid.node, so a change to org.openqa.selenium.grid.node can break org.openqa.selenium.grid.node.docker, while a change to org.openqa.selenium.grid.node.docker can't break org.openqa.selenium.grid.node.
Position
Below the diagonal: org.openqa.selenium.grid.node.docker uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.node.docker uses org.openqa.selenium.grid.node.config, so a change to org.openqa.selenium.grid.node.config can break org.openqa.selenium.grid.node.docker, while a change to org.openqa.selenium.grid.node.docker can't break org.openqa.selenium.grid.node.config.
Position
Below the diagonal: org.openqa.selenium.grid.node.docker uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.router uses org.openqa.selenium, so a change to org.openqa.selenium can break org.openqa.selenium.grid.router, while a change to org.openqa.selenium.grid.router can't break org.openqa.selenium.
Position
Below the diagonal: org.openqa.selenium.grid.router uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.router uses org.openqa.selenium.remote.http, so a change to org.openqa.selenium.remote.http can break org.openqa.selenium.grid.router, while a change to org.openqa.selenium.grid.router can't break org.openqa.selenium.remote.http.
Position
Below the diagonal: org.openqa.selenium.grid.router uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.router uses org.openqa.selenium.remote.tracing, so a change to org.openqa.selenium.remote.tracing can break org.openqa.selenium.grid.router, while a change to org.openqa.selenium.grid.router can't break org.openqa.selenium.remote.tracing.
Position
Below the diagonal: org.openqa.selenium.grid.router uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.router uses org.openqa.selenium.remote, so a change to org.openqa.selenium.remote can break org.openqa.selenium.grid.router, while a change to org.openqa.selenium.grid.router can't break org.openqa.selenium.remote.
Position
Below the diagonal: org.openqa.selenium.grid.router uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.router uses org.openqa.selenium.grid.data, so a change to org.openqa.selenium.grid.data can break org.openqa.selenium.grid.router, while a change to org.openqa.selenium.grid.router can't break org.openqa.selenium.grid.data.
Position
Below the diagonal: org.openqa.selenium.grid.router uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.router uses org.openqa.selenium.grid.sessionmap, so a change to org.openqa.selenium.grid.sessionmap can break org.openqa.selenium.grid.router, while a change to org.openqa.selenium.grid.router can't break org.openqa.selenium.grid.sessionmap.
Position
Below the diagonal: org.openqa.selenium.grid.router uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.router uses org.openqa.selenium.grid.sessionqueue, so a change to org.openqa.selenium.grid.sessionqueue can break org.openqa.selenium.grid.router, while a change to org.openqa.selenium.grid.router can't break org.openqa.selenium.grid.sessionqueue.
Position
Below the diagonal: org.openqa.selenium.grid.router uses a module listed above it, which is the healthy direction.
org.openqa.selenium.grid.router uses org.openqa.selenium.grid.distributor, so a change to org.openqa.selenium.grid.distributor can break org.openqa.selenium.grid.router, while a change to org.openqa.selenium.grid.router can't break org.openqa.selenium.grid.distributor.
Position
Below the diagonal: org.openqa.selenium.grid.router uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 49% · Weak · gated by R1, R7 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
216
High / Critical
A03:2025 — Software Supply Chain Failures
30
High / Critical
A02:2025 — Security Misconfiguration
17
High / Critical
A07:2025 — Authentication Failures
8
High / Critical
Roadmap
Top priorities: Resolve the 18 EmptyCatchBlock finding(s) in Explicit Debt — start with WebDriver.cs (7), SeleniumManager.cs (4), ChromiumDriver.cs; Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; Resolve the 1 finding(s) in Type Safety.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 18 EmptyCatchBlock finding(s) in Explicit Debt — start with WebDriver.cs (7), SeleniumManager.cs (4), ChromiumDriver.cs.
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
Test Quality: Assertions commented out: GetSetDeleteAndClearAllCookies
dotnet/src/webdriver/Manager/SeleniumManager.cs
3.3
Slop
Explicit Debt: EmptyCatchBlock
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.0
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.4
Mixed
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
dotnet/src/webdriver/Chromium/ChromiumDriver.cs
4.6
Mixed
Explicit Debt: EmptyCatchBlock
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
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 — 190
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 — 1394
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 — 145
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 23
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 64 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 64 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1704 of 1729 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1,516 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 893 test source file(s) (.rs, .rb, .py, .tsx, .java) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: this repository's test suite spans .NET and JavaScript/TypeScript, and the JavaScript/TypeScript half could not be re-run — unit: measured (0 flaky); e2e: measured (0 flaky); JavaScript/TypeScript (jest via `pnpm install --frozen-lockfile --ignore-scripts` in javascript/grid-ui/): not included — the jest run in javascript/grid-ui/ produced no per-test report (● Multiple configurations found:). No partial figure is published as if it were the whole: reliability is excluded from the score rather than counted as a near-zero.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in javascript/grid-ui/ was NOT MEASURED: the jest run in javascript/grid-ui/ produced no per-test report (● Multiple configurations found:). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares 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.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Cargo manifest, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Cargo dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Bundler dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'dotnet/src/webdriver/Selenium.WebDriver.csproj' with message: The command "bazel build //dotnet/src/webdriver:manager-linux-x86_64 //dotnet/src/webdriver:manager-linux-arm64 //dotnet/src/webdriver:manager-windows //dotnet/src/webdriver:manager-macos //dotnet/src/webdriver:resource-utilities //dot….
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 51 deducted marker(s) and the 0.5/KLoC density on this row were taken over this repository's .NET projects ALONE: .java (102,192 lines, 42% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 65 task marker(s) (TODO/FIXME/HACK/XXX) across 38 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (210,271 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet/src/webdriver/BiDi/Browser/BrowserModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextInputModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextLogModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextNetworkModule.cs`, … (+36 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.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — kage: * Pin: origin packages.mozilla.org Pin-Priority: 1000 ' | tee /etc/apt/preferences.d/mozilla > /dev/null && apt-get update -qqy && apt-get -qy install firefox google-chrome-stable && dpkg -r --force-depends firefox google-chrome-stable && apt-get -qy remove wget gnupg2 && rm -rf /var/lib/apt/lists/* /var/cache/apt/*" did not complete successfully: exit code: 2; runtime evidence skipped.
DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 2 further occurrence(s) are not listed individually; the score already reflects all 42.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P10 Library API & versioning — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 48 further occurrence(s) are not listed individually; the score already reflects all 88.
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.
PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 68 further occurrence(s) are not listed individually; the score already reflects all 108.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 58 further occurrence(s) are not listed individually; the score already reflects all 98.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 103 further occurrence(s) are not listed individually; the score already reflects all 143.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 33 further occurrence(s) are not listed individually; the score already reflects all 73.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 7 further occurrence(s) are not listed individually; the score already reflects all 47.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 111 further occurrence(s) are not listed individually; the score already reflects all 151.
X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Document value interpolated into markup unescaped could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index').
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D25 ADR Conformance: ADR conformance checks only decisions stated in a checkable form (a ruled-out element, package or dependency, an adr-rules block, a declared delivery status): a decision written only as prose is unverifiable, and decisions never written down are not checked.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
115 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was roles.implicitRole at 82. 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 RemoteValueConverter.Read at 29 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: java/src/org/openqa/selenium/grid/web/ResourceHandler.java (ResourceHandler.mediaType at 20). 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.
+ 82 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with roles.implicitRole (cyclomatic 82), checkSchema (cyclomatic 71), CddlModule.generate_code (cyclomatic 62). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 182 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 9 bodies over 60 down to 60 or less in Cognitive Complexity — start with checkSchema (cognitive 118), CddlModule.generate_code (cognitive 97), Generator.appendRecordBody (cognitive 96). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 9 together lifts Cognitive Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 25 TooManyMethods finding(s) in God Classes — start with bidi_generate.rb (2), bridge.rb, RemoteWebDriver.java. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 22 FileTooLong finding(s) in God Classes — start with BiDiGenerator.java, lib.rs, LocalNode.java. — One of this dimension's main actionable groups (22 warning-level).
Resolve the 16 ClassTooLong finding(s) in God Classes — start with lib.rs, LocalNode.java, CdpClientGenerator.java. — One of this dimension's main actionable groups (16 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
272 duplicated block group(s) detected. A further 306 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 4 of the 578 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (18 corresponding lines) · ×11java/src/org/openqa/selenium/firefox/FirefoxOptions.java:533
+ 192 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 19 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with DockerSessionFactory.java (3), LocalNodeRegistry.java (2), LocalDistributor.java (2). — One of this dimension's main actionable groups (19 warning-level).
Resolve the 16 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with LocalNodeRegistry.java (4), BiDiGenerator.java, Connection.java. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 13 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with LocalNodeRegistry.java (2), BiDiGenerator.java, ChromiumOptions.java. — One of this dimension's main actionable groups (13 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with GraphqlHandler.java, JdkHttpClient.java, PersistentCapabilities.java. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.0 / 10Adequategated by 1 critical finding✓ 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.
22 skipped (11 with a documented reason), 84 zero-assertion, 3 mock references across 1516 tests. Measured on the C# suite only — at least 893 test source file(s) (.rs, .rb, .py, .tsx, .java) went unread, so its test quality is unmeasured and is not in these counts.
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with DevToolsNetworkTests.cs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 83 No assertions finding(s) in Test Quality — start with FrameSwitchingTests.cs (9), BasicMouseInterfaceTests.cs (9), ClickTests.cs (7). — One of this dimension's main actionable groups (83 warning-level).
Resolve the 11 Skipped test finding(s) in Test Quality — start with FirefoxDriverTests.cs (10), DevToolsSecurityTests.cs. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
1 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
REDACTED
What to do
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 129 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 15 direct `PackageReference`(s), and 99 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, a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Cargo manifest and a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 9 Hotspot finding(s) in Churn × Complexity Hotspots — start with project_bidi_schema.mjs, record.js, generate_bidi.mjs. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.3 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
36 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is dotnet/src/webdriver/BiDi/Broker.cs. Counted over 215 of the 519 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
51 deducted debt markers + unmeasured dead symbols across 48575 LoC in the .NET projects (0.5/KLoC) → score 9.1. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .java (42% of production source) was not read, and carries at least 65 uncounted task marker(s) in 38 file(s).
Whole file has no live code — 4 debt markers inside it · ×2dotnet/test/webdriver/BiDi/Input/DefaultKeyboardTests.cs:31
What to do
Resolve the 18 EmptyCatchBlock finding(s) in Explicit Debt — start with WebDriver.cs (7), SeleniumManager.cs (4), ChromiumDriver.cs. — One of this dimension's main actionable groups (18 issue-level).
Resolve the 21 TodoComment finding(s) in Explicit Debt — start with WebElement.cs (2), ElementSelectingTests.cs (2), ResponseData.cs. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 7 CommentedOutCode finding(s) in Explicit Debt — start with DevToolsNetworkTests.cs (6), DriverServiceCommandExecutor.cs. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 4 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Each binding ADR read for checkable forms: a backticked element its Decision section rules out, a ruled-out package the manifests declare, a forbidden module dependency, an opt-in adr-rules block, and a declared delivery status the code does not yet carry. A prose decision with no checkable form is unverifiable, neither a finding nor a pass. Deterministic, no model. Advisory.
1 of 1 checkable records are broken by the code or by their own declared delivery (1 of 4 binding records state a rule in checkable form or declare their delivery; prose decisions are unverifiable).
ADR not followed: 17685. The network async/event APIdocs/decisions/17685-network-handler-behavior.md:146detected by adr-prohibition
What to do
Resolve the 1 ADR not followed finding(s) in ADR Conformance — start with 17685-network-handler-behavior.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d25_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 9 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesiondotnet/src/webdriver/Selenium.WebDriver.csproj:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Selenium.WebDriver.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
77 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
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.
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
216 finding(s): 0 critical, 146 high, 68 medium, 2 low. 100 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 53 file(s) — `common/src/web/cn-test.html` (line 156), `common/src/web/cookies.html` (lines 17–18, lines 18–19, lines 19–20, …), `common/src/web/proxy/page2.html` (lines 5–6, lines 6–7, line 7), `cpp/iedriverserver/resource.h` (line 1), `REDACTED` (line 72), … (+48 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. In 18 of those file(s) — `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextInputModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextLogModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextNetworkModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextScriptModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextStorageModule.cs`, … (+13 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. Separately, one or more rules could not re-parse an embedded snippet in 6 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 19 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 20 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (20 issue-level).
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
No action in Static Analysis (SAST) — all 100 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (100 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 10 High IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (4). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
4 of 215 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is dotnet/src/webdriver/Edge/EdgeOptions.cs. Counted over 215 of the 519 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with Broker.cs, SafariDriverInfo.java, DistributorFlags.java. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Change coupling finding(s) in Change Coupling — start with EdgeDriverInfo.java, ChromeDriverInfo.java. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 13 platform declaration(s) and 106 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`TemplatesManager` is a singleton (one shared instance) but mutates instance state outside any lock (m_templateGenerators; e.g. `m_templateGenerators` at line 134). — third_party/dotnet/devtools/src/generator/CodeGen/TemplatesManager.cs:15
`CodeGenerationSettings` is a singleton (one shared instance) but mutates instance state outside any lock (TemplatesPath; e.g. `TemplatesPath` at third_party/dotnet/devtools/src/generator/CodeGen/ProtocolGenerator.cs line 26, through the shared instance). — third_party/dotnet/devtools/src/generator/CodeGen/CodeGenerationSettings.cs:9
`Parameters` keeps one instance of itself in the static `Empty`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (RawAdditionalData; e.g. `RawAdditionalData` at line 42). — dotnet/src/webdriver/BiDi/Command.cs:26
`LogContext` is not registered, but the singleton `LogContextManager` creates it and keeps it in `GlobalContext`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_level, _truncationLength; e.g. `_level` at line 115). — dotnet/src/webdriver/Internal/Logging/LogContext.cs:30
`Keys` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (descriptions; e.g. `descriptions` at line 365). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — dotnet/src/webdriver/Keys.cs:27
`Platform` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (current; e.g. `current` at line 133). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — dotnet/src/webdriver/Platform.cs:83
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
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.
The namespaces OpenQA.Selenium ↔ OpenQA.Selenium.BiDi ↔ OpenQA.Selenium.BiDi.Browser ↔ OpenQA.Selenium.BiDi.BrowsingContext ↔ OpenQA.Selenium.BiDi.Emulation ↔ OpenQA.Selenium.BiDi.Input ↔ OpenQA.Selenium.BiDi.Json.Converters ↔ OpenQA.Selenium.BiDi.Log ↔ OpenQA.Selenium.BiDi.Network ↔ OpenQA.Selenium.BiDi.Script ↔ OpenQA.Selenium.BiDi.Session ↔ OpenQA.Selenium.BiDi.Storage ↔ OpenQA.Selenium.BiDi.WebExtension ↔ OpenQA.Selenium.Chromium ↔ OpenQA.Selenium.DevTools ↔ OpenQA.Selenium.Interactions ↔ OpenQA.Selenium.Internal ↔ OpenQA.Selenium.Remote depend on each other. The lightest dependency in the cycle is OpenQA.Selenium → OpenQA.Selenium.Chromium (OpenQA.Selenium.CommandJsonSerializerContext → OpenQA.Selenium.Chromium.ChromiumNetworkConditions, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — dotnet/src/webdriver/Command.cs:127
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`IJavaScriptEngine` declares 20 members: `JavaScriptCallbackExecuted`, `JavaScriptExceptionThrown`, `JavaScriptConsoleApiCalled`, `DomMutated`, `InitializationScripts`, `ScriptCallbackBindings`, `StartEventMonitoring`, `StopEventMonitoring`, `EnableDomMutationMonitoring`, `DisableDomMutationMonitoring`, `AddInitializationScript`, `RemoveInitializationScript`, `ClearInitializationScripts`, `PinScript`, `UnpinScript`, `AddScriptCallbackBinding`, `RemoveScriptCallbackBinding`, `ClearScriptCallbackBindings`, `ClearAll`, `Reset`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — dotnet/src/webdriver/IJavaScriptEngine.cs:27
`IWebElement` declares 16 members: `TagName`, `Text`, `Enabled`, `Selected`, `Location`, `Size`, `Displayed`, `Clear`, `SendKeys`, `Submit`, `Click`, `GetAttribute`, `GetDomAttribute`, `GetDomProperty`, `GetCssValue`, `GetShadowRoot`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — dotnet/src/webdriver/IWebElement.cs:31
`IBiDi` declares 19 members under just 15 distinct name(s): `Browser`, `BrowsingContext`, `Emulation`, `Input`, `Log`, `Network`, `Script`, `Storage`, `WebExtension`, `StatusAsync`, `NewAsync`, `EndAsync`, `SubscribeAsync`, `SubscribeAsync`, `SubscribeAsync`, `SubscribeAsync`, `StreamAsync`, `StreamAsync`, `AsModule`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — dotnet/src/webdriver/BiDi/IBiDi.cs:34
`IBrowsingContextModule` declares 28 members: `ActivateAsync`, `CaptureScreenshotAsync`, `CloseAsync`, `CreateAsync`, `GetTreeAsync`, `HandleUserPromptAsync`, `LocateNodesAsync`, `NavigateAsync`, `ContextCreated`, `ContextDestroyed`, `DomContentLoaded`, `DownloadEnd`, `DownloadWillBegin`, `FragmentNavigated`, `HistoryUpdated`, `Load`, `NavigationAborted`, `NavigationCommitted`, `NavigationFailed`, `NavigationStarted`, `UserPromptClosed`, `UserPromptOpened`, `PrintAsync`, `ReloadAsync`, `SetViewportAsync`, `StartScreencastAsync`, `StopScreencastAsync`, `TraverseHistoryAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — dotnet/src/webdriver/BiDi/BrowsingContext/IBrowsingContextModule.cs:22
`INetworkModule` declares 18 members: `AddDataCollectorAsync`, `AddInterceptAsync`, `DisownDataAsync`, `ContinueRequestAsync`, `ContinueResponseAsync`, `ContinueWithAuthAsync`, `FailRequestAsync`, `GetDataAsync`, `AuthRequired`, `BeforeRequestSent`, `FetchError`, `ResponseCompleted`, `ResponseStarted`, `ProvideResponseAsync`, `RemoveDataCollectorAsync`, `RemoveInterceptAsync`, `SetCacheBehaviorAsync`, `SetExtraHeadersAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — dotnet/src/webdriver/BiDi/Network/INetworkModule.cs:22
`NodeRegistry` declares 18 abstract methods: `add`, `drain`, `getActiveSlots`, `getAvailableNodes`, `getDownNodeCount`, `getIdleSlots`, `getNode`, `getNode`, `getStatus`, `getUpNodeCount`, `getUpNodes`, `refresh`, `register`, `remove`, `reserve`, `runHealthChecks`, `setSession`, `updateNodeAvailability`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 18 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — java/src/org/openqa/selenium/grid/distributor/NodeRegistry.java:38
`WebElement` declares 16 abstract methods: `clear`, `click`, `findElement`, `findElements`, `getAttribute`, `getCssValue`, `getLocation`, `getRect`, `getSize`, `getTagName`, `getText`, `isDisplayed`, `isEnabled`, `isSelected`, `sendKeys`, `submit`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — java/src/org/openqa/selenium/WebElement.java:32
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
OpenQA.Selenium.DriverService's [DriverPathFromEnvironment, DriverServicePath] are judged in OpenQA.Selenium.Chromium.ChromiumDriver, OpenQA.Selenium.Firefox.FirefoxDriver, OpenQA.Selenium.IE.InternetExplorerDriver, OpenQA.Selenium.Safari.SafariDriver — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
javascript.atoms.typescript.core.geometry.Rect's [height, width] are judged in javascript.atoms.typescript.click, javascript.atoms.typescript.core.overflow, javascript.atoms.typescript.core.shown — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
org.openqa.selenium.Dimension's [height, width] are built independently in org.openqa.selenium.Rectangle, org.openqa.selenium.grid.node.docker.DockerSessionFactory, org.openqa.selenium.grid.node.kubernetes.KubernetesSessionFactory, org.openqa.selenium.remote.RemoteWebElement, org.openqa.selenium.remote.RemoteWindow — the same reading, produced twice. Two producers can disagree without either looking wrong on its own: whichever population, filter or rounding one of them applies, the other need not, and nothing compares them. Give the measurement ONE producer and let the other call it.
org.openqa.selenium.Point's [x, y] are built independently in org.openqa.selenium.Rectangle, org.openqa.selenium.remote.RemoteWebElement, org.openqa.selenium.remote.RemoteWindow — the same reading, produced twice. Two producers can disagree without either looking wrong on its own: whichever population, filter or rounding one of them applies, the other need not, and nothing compares them. Give the measurement ONE producer and let the other call it.
What to do
Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
Give each measurement ONE producer — the others call it. Centralising the judgement is not enough on its own: two producers of the same numbers can disagree while every rule reading them is correct.
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.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×10) — dotnet/src/webdriver/BiDi/BrowsingContext/DownloadEndEvent.cs:68, dotnet/src/webdriver/BiDi/Input/Origin.cs:31, dotnet/src/webdriver/BiDi/Json/Converters/PrintPageRangeConverter.cs:28, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
common/src/web/accessibility/README.md links to `../../../../docs/decisions/18205-accessibility-tree-snapshot.md`, but `docs/decisions/18205-accessibility-tree-snapshot.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — common/src/web/accessibility/README.md:4
What to do
Reconcile the README with reality: common/src/web/accessibility/README.md links to `../../../../docs/decisions/18205-accessibility-tree-snapshot.md`, but `docs/decisions/18205-accessibility-tree-snapshot.md` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning9.5 / 10Exemplary✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
3 public types in `OpenQA.Selenium.Interactions.Internal` are marked as implementation by their own namespace, folder or name: `ICoordinates` (dotnet/src/webdriver/Interactions/ICoordinates.cs:27, `Internal`), `ICoordinates` (dotnet/src/webdriver/Interactions/ICoordinates.cs:27, `Internal`), `ICoordinates` (dotnet/src/webdriver/Interactions/ICoordinates.cs:27, `Internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — dotnet/src/webdriver/Interactions/ICoordinates.cs:27
15 public types in `OpenQA.Selenium.Internal` are marked as implementation by their own namespace, folder or name: `AndroidOptions` (dotnet/src/webdriver/Internal/AndroidOptions.cs:25, `Internal`), `AndroidOptions` (dotnet/src/webdriver/Internal/AndroidOptions.cs:25, `Internal`), `AndroidOptions` (dotnet/src/webdriver/Internal/AndroidOptions.cs:25, `Internal`), `Base64UrlEncoder` (dotnet/src/webdriver/Internal/Base64UrlEncoder.cs:32, `Internal`), `Base64UrlEncoder` (dotnet/src/webdriver/Internal/Base64UrlEncoder.cs:32, `Internal`), `Base64UrlEncoder` (dotnet/src/webdriver/Internal/Base64UrlEncoder.cs:32, `Internal`), `IFindsElement` (dotnet/src/webdriver/Internal/IFindsElement.cs:27, `Internal`), `IFindsElement` (dotnet/src/webdriver/Internal/IFindsElement.cs:27, `Internal`), and 7 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — dotnet/src/webdriver/Internal/AndroidOptions.cs:25
45 public types in `OpenQA.Selenium.Internal.Logging` are marked as implementation by their own namespace, folder or name: `FileLogHandler` (dotnet/src/webdriver/Internal/Logging/FileLogHandler.cs:25, `Internal`), `FileLogHandler` (dotnet/src/webdriver/Internal/Logging/FileLogHandler.cs:25, `Internal`), `FileLogHandler` (dotnet/src/webdriver/Internal/Logging/FileLogHandler.cs:25, `Internal`), `ILogContext` (dotnet/src/webdriver/Internal/Logging/ILogContext.cs:25, `Internal`), `ILogContext` (dotnet/src/webdriver/Internal/Logging/ILogContext.cs:25, `Internal`), `ILogContext` (dotnet/src/webdriver/Internal/Logging/ILogContext.cs:25, `Internal`), `ILogHandler` (dotnet/src/webdriver/Internal/Logging/ILogHandler.cs:25, `Internal`), `ILogHandler` (dotnet/src/webdriver/Internal/Logging/ILogHandler.cs:25, `Internal`), and 37 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — dotnet/src/webdriver/Internal/Logging/FileLogHandler.cs:25
`OpenQA.Selenium.BiDi.BiDi` (dotnet/src/webdriver/BiDi/BiDi.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/BiDi.cs:25
`OpenQA.Selenium.BiDi.BrowsingContext.BrowsingContextEvent` (dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextEvent.cs:24
`OpenQA.Selenium.BiDi.BrowsingContext.BrowsingContextEvent` (dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextEvent.cs:24
`OpenQA.Selenium.BiDi.Input.InputEvent` (dotnet/src/webdriver/BiDi/Input/InputEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Input/InputEvent.cs:24
`OpenQA.Selenium.BiDi.Input.InputEvent` (dotnet/src/webdriver/BiDi/Input/InputEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Input/InputEvent.cs:24
`OpenQA.Selenium.BiDi.Json.Converters.CamelCaseEnumConverter` (dotnet/src/webdriver/BiDi/Json/Converters/CamelCaseEnumConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Json/Converters/CamelCaseEnumConverter.cs:25
`OpenQA.Selenium.BiDi.Json.Converters.CamelCaseEnumConverter` (dotnet/src/webdriver/BiDi/Json/Converters/CamelCaseEnumConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Json/Converters/CamelCaseEnumConverter.cs:25
`OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetConverter` (dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:25
`OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetSecondsConverter` (dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:38) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:38
`OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetConverter` (dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:25
`OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetSecondsConverter` (dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:38) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:38
`OpenQA.Selenium.BiDi.Json.Converters.KebabCaseEnumConverter` (dotnet/src/webdriver/BiDi/Json/Converters/KebabCaseEnumConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Json/Converters/KebabCaseEnumConverter.cs:25
`OpenQA.Selenium.BiDi.Json.Converters.KebabCaseEnumConverter` (dotnet/src/webdriver/BiDi/Json/Converters/KebabCaseEnumConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Json/Converters/KebabCaseEnumConverter.cs:25
`OpenQA.Selenium.BiDi.Json.Converters.OptionalConverter` (dotnet/src/webdriver/BiDi/Json/Converters/OptionalConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Json/Converters/OptionalConverter.cs:25
`OpenQA.Selenium.BiDi.Json.Converters.OptionalConverter` (dotnet/src/webdriver/BiDi/Json/Converters/OptionalConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Json/Converters/OptionalConverter.cs:25
`OpenQA.Selenium.BiDi.Log.LogEvent` (dotnet/src/webdriver/BiDi/Log/LogEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Log/LogEvent.cs:24
`OpenQA.Selenium.BiDi.Network.NetworkEvent` (dotnet/src/webdriver/BiDi/Network/NetworkEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Network/NetworkEvent.cs:24
`OpenQA.Selenium.BiDi.Script.ScriptEvent` (dotnet/src/webdriver/BiDi/Script/ScriptEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Script/ScriptEvent.cs:24
`OpenQA.Selenium.BiDi.Script.ScriptEvent` (dotnet/src/webdriver/BiDi/Script/ScriptEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Script/ScriptEvent.cs:24
`OpenQA.Selenium.BiDi.Speculation.SpeculationEvent` (dotnet/src/webdriver/BiDi/Speculation/SpeculationEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Speculation/SpeculationEvent.cs:24
`OpenQA.Selenium.BiDi.Speculation.SpeculationEvent` (dotnet/src/webdriver/BiDi/Speculation/SpeculationEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/BiDi/Speculation/SpeculationEvent.cs:24
`OpenQA.Selenium.DefaultFileDetector` (dotnet/src/webdriver/DefaultFileDetector.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DefaultFileDetector.cs:28
`OpenQA.Selenium.DefaultFileDetector` (dotnet/src/webdriver/DefaultFileDetector.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DefaultFileDetector.cs:28
`OpenQA.Selenium.DevTools.CommandResponseTypeMap` (dotnet/src/webdriver/DevTools/CommandResponseTypeMap.cs:27) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/CommandResponseTypeMap.cs:27
`OpenQA.Selenium.DevTools.CommandResponseTypeMap` (dotnet/src/webdriver/DevTools/CommandResponseTypeMap.cs:27) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/CommandResponseTypeMap.cs:27
`OpenQA.Selenium.DevTools.DevToolsCommandData` (dotnet/src/webdriver/DevTools/DevToolsCommandData.cs:29) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/DevToolsCommandData.cs:29
`OpenQA.Selenium.DevTools.DevToolsCommandData` (dotnet/src/webdriver/DevTools/DevToolsCommandData.cs:29) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/DevToolsCommandData.cs:29
`OpenQA.Selenium.DevTools.DevToolsVersionInfo` (dotnet/src/webdriver/DevTools/DevToolsVersionInfo.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/DevToolsVersionInfo.cs:28
`OpenQA.Selenium.DevTools.DevToolsVersionInfo` (dotnet/src/webdriver/DevTools/DevToolsVersionInfo.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/DevToolsVersionInfo.cs:28
`OpenQA.Selenium.DevTools.WebSocketConnection` (dotnet/src/webdriver/DevTools/WebSocketConnection.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/WebSocketConnection.cs:28
`OpenQA.Selenium.DevTools.WebSocketConnection` (dotnet/src/webdriver/DevTools/WebSocketConnection.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/WebSocketConnection.cs:28
`OpenQA.Selenium.DevTools.V155.V155Domains` (dotnet/src/webdriver/DevTools/v155/V155Domains.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/v155/V155Domains.cs:25
`OpenQA.Selenium.DevTools.V155.V155Domains` (dotnet/src/webdriver/DevTools/v155/V155Domains.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/v155/V155Domains.cs:25
`OpenQA.Selenium.DevTools.V155.V155JavaScript` (dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:28
`OpenQA.Selenium.DevTools.V155.V155JavaScript` (dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:28
`OpenQA.Selenium.DevTools.V155.V155Log` (dotnet/src/webdriver/DevTools/v155/V155Log.cs:27) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/v155/V155Log.cs:27
`OpenQA.Selenium.DevTools.V155.V155Log` (dotnet/src/webdriver/DevTools/v155/V155Log.cs:27) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — dotnet/src/webdriver/DevTools/v155/V155Log.cs:27
What to do
Hide `OpenQA.Selenium.Interactions.Internal` (`ICoordinates`, `ICoordinates`, `ICoordinates`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `OpenQA.Selenium.Internal` (`AndroidOptions`, `AndroidOptions`, `AndroidOptions`, `Base64UrlEncoder`, `Base64UrlEncoder`, `Base64UrlEncoder`, `IFindsElement`, `IFindsElement`, and 7 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `OpenQA.Selenium.Internal.Logging` (`FileLogHandler`, `FileLogHandler`, `FileLogHandler`, `ILogContext`, `ILogContext`, `ILogContext`, `ILogHandler`, `ILogHandler`, and 37 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Make `OpenQA.Selenium.BiDi.BiDi` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.BrowsingContext.BrowsingContextEvent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.BrowsingContext.BrowsingContextEvent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Input.InputEvent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Input.InputEvent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Json.Converters.CamelCaseEnumConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Json.Converters.CamelCaseEnumConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetSecondsConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetSecondsConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Json.Converters.KebabCaseEnumConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Json.Converters.KebabCaseEnumConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Json.Converters.OptionalConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Json.Converters.OptionalConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Log.LogEvent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Network.NetworkEvent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Script.ScriptEvent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Script.ScriptEvent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Speculation.SpeculationEvent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.BiDi.Speculation.SpeculationEvent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DefaultFileDetector` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DefaultFileDetector` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.CommandResponseTypeMap` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.CommandResponseTypeMap` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.DevToolsCommandData` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.DevToolsCommandData` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.DevToolsVersionInfo` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.DevToolsVersionInfo` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.WebSocketConnection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.WebSocketConnection` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V155.V155Domains` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V155.V155Domains` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V155.V155JavaScript` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V155.V155JavaScript` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V155.V155Log` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V155.V155Log` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V155.V155Network` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V155.V155Network` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V155.V155Target` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V155.V155Target` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V156.V156Domains` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V156.V156Domains` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V156.V156JavaScript` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V156.V156JavaScript` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V156.V156Log` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V156.V156Log` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V156.V156Network` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V156.V156Network` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V156.V156Target` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V156.V156Target` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V157.V157Domains` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V157.V157Domains` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V157.V157JavaScript` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V157.V157JavaScript` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V157.V157Log` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V157.V157Log` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V157.V157Network` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V157.V157Network` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V157.V157Target` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DevTools.V157.V157Target` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DriverFinder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.DriverFinder` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.ErrorResponse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.ErrorResponse` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.HttpCommandInfo` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.HttpCommandInfo` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Keys` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Logs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Logs` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Manager.SeleniumManager` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Manager.SeleniumManager` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.NetworkManager` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.NetworkManager` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.PasswordCredentials` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Remote.DriverServiceCommandExecutor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Remote.DriverServiceCommandExecutor` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Remote.ReadOnlyDesiredCapabilities` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Remote.ReadOnlyDesiredCapabilities` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.RemoteSessionSettings` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Remote.RemoteWebDriver` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Remote.W3CWireProtocolCommandInfoRepository` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.Remote.W3CWireProtocolCommandInfoRepository` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.ShadowRoot` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `OpenQA.Selenium.ShadowRoot` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
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.
`REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
What to do
Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. (×3) — REDACTED:394, REDACTED:456, REDACTED:517
What to do
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.statSync` in `installAddon` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — javascript/selenium-webdriver/firefox.js:566
`fs.readFileSync` in `addDomMutationHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — javascript/selenium-webdriver/lib/script.js:84
`fs.readFileSync` in `logMutationEvents` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — REDACTED:1555, REDACTED:1558
`fs.mkdirSync` in `downloadFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:1765
`fs.writeFileSync` in `downloadFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:1767
`fs.readFileSync` in `downloadFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:1769
`fs.writeFileSync` in `callback to forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:1775
30 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×29) — dotnet/src/support/Events/EventFiringWebDriver.cs:822, dotnet/src/support/Events/EventFiringWebDriver.cs:854, dotnet/src/support/Events/EventFiringWebDriver.cs:886, …
`this.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — dotnet/src/support/UI/SlowLoadableComponent{T}.cs:102
`await this.BackAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — dotnet/src/support/Events/EventFiringWebDriver.cs:821
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.
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Do you agree with this assessment?
R1 · Type Safety3.4 / 10Weak✓ 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.
145 typed · 282 plain JS — the untyped files are common/extensions/webextensions-selenium-example-signed/inject.js, common/extensions/webextensions-selenium-example/inject.js, common/src/web/devtools_request_interception_test/one.js, common/src/web/devtools_request_interception_test/two.js, common/src/web/html5/database.js, common/src/web/html5/geolocation.js (+276 more). 0 production file(s) opt out entirely with @ts-nocheck · 1 @ts-ignore suppression(s).
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.
9 duplicated blocks under javascript/ have copies in at least two of the sibling directories atoms, bidi-support, cdp-support, chrome-driver, ie-driver, selenium-webdriver (+1 more sibling(s) not listed) — 6 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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. — javascript/bidi-support/bidi-mutation-listener.js:18
javascript/selenium-webdriver/bidi/networkTypes.js:247 · javascript/selenium-webdriver/bidi/networkTypes.js:698 — the two spans are one implementation copied and then locally edited — 251 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. — javascript/selenium-webdriver/bidi/networkTypes.js:247
javascript/selenium-webdriver/bidi/continueRequestParameters.js:24 · javascript/selenium-webdriver/bidi/provideResponseParameters.js:25 — 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. — javascript/selenium-webdriver/bidi/continueRequestParameters.js:24
javascript/selenium-webdriver/project_bidi_schema_test.mjs:351 · javascript/selenium-webdriver/project_bidi_schema_test.mjs:517 — the two spans are one implementation copied and then locally edited — 327 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. — javascript/selenium-webdriver/project_bidi_schema_test.mjs:351
javascript/selenium-webdriver/bidi/network.js:53 · javascript/selenium-webdriver/bidi/scriptManager.js:46 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — javascript/selenium-webdriver/bidi/network.js:53
REDACTED:2729 · REDACTED:3254 — 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. — REDACTED:2729
javascript/atoms/typescript/core/locators.ts:618 · javascript/atoms/typescript/core/locators.ts:665 — 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. — javascript/atoms/typescript/core/locators.ts:618
javascript/selenium-webdriver/bidi/browsingContextInspector.js:139 · javascript/selenium-webdriver/bidi/network.js:394 — 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. — javascript/selenium-webdriver/bidi/browsingContextInspector.js:139
javascript/selenium-webdriver/bidi/logInspector.js:57 · javascript/selenium-webdriver/bidi/network.js:59 · javascript/selenium-webdriver/bidi/scriptManager.js:50 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — javascript/selenium-webdriver/bidi/logInspector.js:57
javascript/selenium-webdriver/bidi/continueResponseParameters.js:83 · javascript/selenium-webdriver/bidi/provideResponseParameters.js:77 — 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. — javascript/selenium-webdriver/bidi/continueResponseParameters.js:83
javascript/webdriver/atoms/inject/local_storage.js:22 · javascript/webdriver/atoms/inject/session_storage.js:22 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — javascript/webdriver/atoms/inject/local_storage.js:22
javascript/selenium-webdriver/bidi/network.js:155 · javascript/selenium-webdriver/bidi/networkInspector.js:62 — 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. — javascript/selenium-webdriver/bidi/network.js:155
javascript/selenium-webdriver/bidi/browsingContextInspector.js:89 · javascript/selenium-webdriver/bidi/networkInspector.js:40 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — javascript/selenium-webdriver/bidi/browsingContextInspector.js:89
javascript/atoms/dom.js:1219 · javascript/atoms/typescript/get-text.ts:117 — the two spans are one implementation copied and then locally edited — 121 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. — javascript/atoms/dom.js:1219
javascript/webdriver/atoms/storage/local_storage.js:25 · javascript/webdriver/atoms/storage/session_storage.js:25 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — javascript/webdriver/atoms/storage/local_storage.js:25
javascript/atoms/action.js:398 · javascript/atoms/action.js:458 — 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. — javascript/atoms/action.js:398
javascript/selenium-webdriver/bidi/storage.js:52 · javascript/selenium-webdriver/bidi/storage.js:117 · javascript/selenium-webdriver/bidi/storage.js:159 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — javascript/selenium-webdriver/bidi/storage.js:52
REDACTED:131 · REDACTED:247 — 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. — REDACTED:131
javascript/selenium-webdriver/bidi/cookieFilter.js:62 · javascript/selenium-webdriver/bidi/partialCookie.js:42 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — javascript/selenium-webdriver/bidi/cookieFilter.js:62
javascript/atoms/typescript/core/locators.ts:233 · javascript/atoms/typescript/core/locators.ts:385 — 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. — javascript/atoms/typescript/core/locators.ts:233
javascript/selenium-webdriver/bidi/browsingContext.js:167 · javascript/selenium-webdriver/bidi/browsingContext.js:424 — 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. — javascript/selenium-webdriver/bidi/browsingContext.js:167
REDACTED:822 · REDACTED:841 — 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. — REDACTED:822
javascript/grid-ui/src/components/Node/NodeDetailsDialog.tsx:94 · javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx:731 — 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. — javascript/grid-ui/src/components/Node/NodeDetailsDialog.tsx:94
javascript/selenium-webdriver/generate_bidi.mjs:788 · javascript/selenium-webdriver/project_bidi_schema.mjs:615 — the two spans are one implementation copied and then locally edited — 136 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. — javascript/selenium-webdriver/generate_bidi.mjs:788
javascript/webdriver/atoms/inject/action.js:224 · javascript/webdriver/atoms/inject/dom.js:152 — 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. — javascript/webdriver/atoms/inject/action.js:224
javascript/atoms/locators/classname.js:36 · javascript/atoms/locators/classname.js:72 — 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. — javascript/atoms/locators/classname.js:36
javascript/selenium-webdriver/bidi/logInspector.js:102 · javascript/selenium-webdriver/bidi/logInspector.js:152 · javascript/selenium-webdriver/bidi/logInspector.js:228 — 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. — javascript/selenium-webdriver/bidi/logInspector.js:102
javascript/selenium-webdriver/bidi/network.js:298 · javascript/selenium-webdriver/bidi/network.js:331 — 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. — javascript/selenium-webdriver/bidi/network.js:298
javascript/selenium-webdriver/bidi/scriptManager.js:344 · javascript/selenium-webdriver/bidi/scriptManager.js:378 — 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. — javascript/selenium-webdriver/bidi/scriptManager.js:344
javascript/selenium-webdriver/http/util.js:56 · javascript/selenium-webdriver/http/util.js:112 — the two spans are one implementation copied and then locally edited — 83 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. — javascript/selenium-webdriver/http/util.js:56
javascript/atoms/locators/link_text.js:26 · javascript/atoms/locators/link_text.js:61 — the two spans are one implementation copied and then locally edited — 129 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. — javascript/atoms/locators/link_text.js:26
javascript/bidi-support/bidi-mutation-listener.js:18 · javascript/cdp-support/mutation-listener.js:18 — the two spans are one implementation copied and then locally edited — 112 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — javascript/bidi-support/bidi-mutation-listener.js:18
javascript/grid-ui/src/components/QueuedSessions/QueuedSessions.tsx:52 · javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx:326 — 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. — javascript/grid-ui/src/components/QueuedSessions/QueuedSessions.tsx:52
javascript/selenium-webdriver/bidi/storage.js:133 · javascript/selenium-webdriver/bidi/storage.js:175 — 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. — javascript/selenium-webdriver/bidi/storage.js:133
javascript/selenium-webdriver/lib/script.js:89 · REDACTED:1575 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — javascript/selenium-webdriver/lib/script.js:89
javascript/selenium-webdriver/lib/select.js:183 · javascript/selenium-webdriver/lib/select.js:399 — 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. — javascript/selenium-webdriver/lib/select.js:183
javascript/selenium-webdriver/normalize_bidi_ast_test.mjs:119 · javascript/selenium-webdriver/normalize_bidi_ast_test.mjs:177 — 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. — javascript/selenium-webdriver/normalize_bidi_ast_test.mjs:119
javascript/grid-ui/src/components/QueuedSessions/QueuedSessions.tsx:84 · javascript/grid-ui/src/components/QueuedSessions/QueuedSessions.tsx:116 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — javascript/grid-ui/src/components/QueuedSessions/QueuedSessions.tsx:84
javascript/selenium-webdriver/bidi/serialization/record.js:254 · javascript/selenium-webdriver/bidi/serialization/record.js:298 — the two spans are one implementation copied and then locally edited — 104 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. — javascript/selenium-webdriver/bidi/serialization/record.js:254
javascript/selenium-webdriver/testing/index.js:325 · javascript/selenium-webdriver/testing/index.js:339 — 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. — javascript/selenium-webdriver/testing/index.js:325
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
javascript/grid-ui/src/components/LiveView/LiveView.tsx:19 imports @novnc/novnc/lib/rfb, 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. — javascript/grid-ui/src/components/LiveView/LiveView.tsx:19
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
implicitRole has cyclomatic complexity 82 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/typescript/core/accessibility/roles.ts:248
validateValue has cyclomatic complexity 51 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/selenium-webdriver/bidi/serialization/record.js:50
checkSchema has cyclomatic complexity 43 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/selenium-webdriver/project_bidi_schema.mjs:873
diffAgainstCddl2ts has cyclomatic complexity 43 and cognitive complexity 86; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — javascript/selenium-webdriver/bidi_schema_diff_test.mjs:253
build has cyclomatic complexity 39 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/selenium-webdriver/index.js:601
getOverflowState has cyclomatic complexity 32 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/typescript/core/overflow.ts:40
getOverflowState has cyclomatic complexity 31 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — javascript/atoms/dom.js:667
get has cyclomatic complexity 29 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/typescript/get-attribute.ts:28
nativeName has cyclomatic complexity 28 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/typescript/core/accessibility/accname.ts:420
validate has cyclomatic complexity 27 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — javascript/atoms/typescript/testing/corpus-consistent.mjs:68
projectEntry has cyclomatic complexity 26 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/selenium-webdriver/project_bidi_schema.mjs:224
escapeCss has cyclomatic complexity 26 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/selenium-webdriver/lib/by.js:67
get has cyclomatic complexity 25 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/webdriver/atoms/attribute.js:110
(anonymous) has cyclomatic complexity 25 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/selenium-webdriver/test/http/http_test.js:29
computeTextAlternative has cyclomatic complexity 24 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — javascript/atoms/typescript/core/accessibility/accname.ts:499
generateDomainFile has cyclomatic complexity 21 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/selenium-webdriver/generate_bidi.mjs:942
evaluate_ has cyclomatic complexity 19 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — javascript/atoms/locators/xpath.js:90
computeContentText has cyclomatic complexity 19 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — javascript/atoms/typescript/core/accessibility/accname.ts:328
isShown_ has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/dom.js:460
isShownInternal has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/typescript/core/shown.ts:86
projectSchema has cyclomatic complexity 18 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 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. — javascript/selenium-webdriver/project_bidi_schema.mjs:677
focusOnElement has cyclomatic complexity 18 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:456
editContent has cyclomatic complexity 18 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 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. — javascript/atoms/typescript/core/keyboard.ts:325
positiveSize has cyclomatic complexity 18 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 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. — javascript/atoms/typescript/core/shown.ts:127
appendVisibleTextLinesFromElementCommon_ has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/dom.js:1049
appendTextFromElementCommon has cyclomatic complexity 18 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/typescript/get-text.ts:161
type has cyclomatic complexity 17 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/typescript/type.ts:118
dedupeDefs has cyclomatic complexity 17 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/selenium-webdriver/normalize_bidi_ast.mjs:530
getArgument has cyclomatic complexity 17 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/selenium-webdriver/bidi/protocolValue.js:192
clear has cyclomatic complexity 16 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/action.js:86
collectUnionMembers has cyclomatic complexity 16 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/selenium-webdriver/generate_bidi.mjs:394
displayed has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/dom.js:600
displayed has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/typescript/core/shown.ts:191
appendVisibleTextLinesFromNodeInComposedDom_ has cyclomatic complexity 15 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — javascript/atoms/dom.js:1363
extractVendor has cyclomatic complexity 15 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — javascript/selenium-webdriver/project_bidi_schema.mjs:805
moveCaret has cyclomatic complexity 15 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 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. — javascript/atoms/typescript/core/keyboard.ts:280
hoistInlineRecords has cyclomatic complexity 15 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 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. — javascript/selenium-webdriver/normalize_bidi_ast.mjs:233
clickElement has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:385
(anonymous) has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/typescript/core/inject.ts:132
getSize has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — javascript/atoms/window.js:221
Do you agree with this assessment?
R3 · Large Files5.1 / 10Adequate✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
REDACTED has 3211 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
javascript/atoms/dom.js has 1303 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/atoms/dom.js:1
javascript/selenium-webdriver/project_bidi_schema_test.mjs has 1172 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/project_bidi_schema_test.mjs:1
javascript/selenium-webdriver/generate_bidi.mjs has 1121 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/generate_bidi.mjs:1
javascript/selenium-webdriver/project_bidi_schema.mjs has 1080 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/project_bidi_schema.mjs:1
javascript/selenium-webdriver/lib/input.js has 978 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/lib/input.js:1
javascript/atoms/keyboard.js has 938 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/atoms/keyboard.js:1
REDACTED has 863 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
javascript/selenium-webdriver/chromium.js has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/chromium.js:1
javascript/selenium-webdriver/bidi/networkTypes.js has 765 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/bidi/networkTypes.js:1
javascript/selenium-webdriver/index.js has 745 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/index.js:1
javascript/selenium-webdriver/firefox.js has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/firefox.js:1
javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx has 698 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx:1
javascript/atoms/events.js has 687 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/atoms/events.js:1
javascript/atoms/action.js has 685 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/atoms/action.js:1
javascript/atoms/typescript/core/locators.ts has 653 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/atoms/typescript/core/locators.ts:1
javascript/selenium-webdriver/testing/index.js has 640 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/testing/index.js:1
javascript/selenium-webdriver/lib/logging.js has 637 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/lib/logging.js:1
javascript/selenium-webdriver/bidi/browsingContext.js has 584 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/bidi/browsingContext.js:1
javascript/selenium-webdriver/remote/index.js has 557 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/remote/index.js:1
javascript/selenium-webdriver/lib/error.js has 552 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/lib/error.js:1
javascript/atoms/typescript/core/accessibility/accname.ts has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/atoms/typescript/core/accessibility/accname.ts:1
javascript/selenium-webdriver/lib/http.js has 517 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/lib/http.js:1
javascript/selenium-webdriver/normalize_bidi_ast.mjs has 517 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/normalize_bidi_ast.mjs:1
REDACTED has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
javascript/selenium-webdriver/bidi/scriptManager.js has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/bidi/scriptManager.js:1
javascript/selenium-webdriver/lib/capabilities.js has 495 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/lib/capabilities.js:1
javascript/selenium-webdriver/lib/accessibility_snapshot.js has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/lib/accessibility_snapshot.js:1
javascript/atoms/inject.js has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/atoms/inject.js:1
javascript/selenium-webdriver/bidi/index.js has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/bidi/index.js:1
javascript/atoms/mouse.js has 455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/atoms/mouse.js:1
javascript/webdriver/http/http.js has 452 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/webdriver/http/http.js:1
javascript/selenium-webdriver/ie.js has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/ie.js:1
javascript/selenium-webdriver/lib/by.js has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/lib/by.js:1
javascript/selenium-webdriver/lib/select.js has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/lib/select.js:1
javascript/selenium-webdriver/bidi/protocolValue.js has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/bidi/protocolValue.js:1
javascript/selenium-webdriver/lib/until.js has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/selenium-webdriver/lib/until.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage4.6 / 10Weak✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — javascript/atoms/dom.js:1, javascript/selenium-webdriver/project_bidi_schema_test.mjs:1, javascript/selenium-webdriver/generate_bidi.mjs:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code1.6 / 10Critical✓ 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.
Unreachable from the 83 application, 15 tooling and 132 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (83 application, 15 tooling, 132 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 (×39) — javascript/atoms/dom.js, javascript/selenium-webdriver/project_bidi_schema_test.mjs, javascript/atoms/keyboard.js, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in javascript/selenium-webdriver/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Cryptographic hygiene (weak hash/cipher, password key-derivation). This codebase has no web surface, so transport/header/cookie/CSRF controls are N/A and only crypto is scored. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself — a page handed to a consumer runs in that consumer's origin.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — third_party/dotnet/devtools/src/generator/Program.cs:85
`https://selenium.dev/selenium/web/js/jquery-3.5.1.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 7 such include(s) across the repository's markup. — common/src/web/mouse_interaction.html:12
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
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.
The guard on line 117 rejects `commandName` and line 119 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(commandName)` is true of a value that is NOT null: it is satisfied by an EMPTY `commandName`, and on that path `commandName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — dotnet/src/webdriver/CommandInfoRepository.cs:119
The guard on line 69 rejects `endpointAddress` and line 71 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(endpointAddress)` is true of a value that is NOT null: it is satisfied by an EMPTY `endpointAddress`, and on that path `endpointAddress` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — REDACTED:71
The guard on line 299 rejects `addOnDirectoryToInstall` and line 301 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(addOnDirectoryToInstall)` is true of a value that is NOT null: it is satisfied by an EMPTY `addOnDirectoryToInstall`, and on that path `addOnDirectoryToInstall` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — dotnet/src/webdriver/Firefox/FirefoxDriver.cs:301
The guard on line 328 rejects `addOnFileToInstall` and line 330 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(addOnFileToInstall)` is true of a value that is NOT null: it is satisfied by an EMPTY `addOnFileToInstall`, and on that path `addOnFileToInstall` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — dotnet/src/webdriver/Firefox/FirefoxDriver.cs:330
The guard on line 357 rejects `base64EncodedAddOn` and line 359 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(base64EncodedAddOn)` is true of a value that is NOT null: it is satisfied by an EMPTY `base64EncodedAddOn`, and on that path `base64EncodedAddOn` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — dotnet/src/webdriver/Firefox/FirefoxDriver.cs:359
The guard on line 379 rejects `addOnId` and line 381 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(addOnId)` is true of a value that is NOT null: it is satisfied by an EMPTY `addOnId`, and on that path `addOnId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — dotnet/src/webdriver/Firefox/FirefoxDriver.cs:381
The guard on line 39 rejects `fileName` and line 41 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — dotnet/src/webdriver/Firefox/Internal/IniFileReader.cs:41
The guard on line 108 rejects `sectionName` and line 110 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(sectionName)` is true of a value that is NOT null: it is satisfied by an EMPTY `sectionName`, and on that path `sectionName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — dotnet/src/webdriver/Firefox/Internal/IniFileReader.cs:110
The guard on line 115 rejects `valueName` and line 117 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(valueName)` is true of a value that is NOT null: it is satisfied by an EMPTY `valueName`, and on that path `valueName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — dotnet/src/webdriver/Firefox/Internal/IniFileReader.cs:117
The guard on line 318 rejects `direction` and line 320 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(direction)` is true of a value that is NOT null: it is satisfied by an EMPTY `direction`, and on that path `direction` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — dotnet/src/webdriver/RelativeBy.cs:320
The guard on line 218 rejects `permissionName` and line 220 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(permissionName)` is true of a value that is NOT null: it is satisfied by an EMPTY `permissionName`, and on that path `permissionName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — dotnet/src/webdriver/Safari/SafariDriver.cs:220
What to do
Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.6 `!` suppressions per 1k syntax nodes — 6 suppression(s) across the 10181 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 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.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — AX1 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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) — kage: * Pin: origin packages.mozilla.org Pin-Priority: 1000 ' | tee /etc/apt/preferences.d/mozilla > /dev/null && apt-get update -qqy && apt-get -qy install firefox google-chrome-stable && dpkg -r --force-depends firefox google-chrome-stable && apt-get -qy remove wget gnupg2 && rm -rf /var/lib/apt/lists/* /var/cache/apt/*" did not complete successfully: exit code: 2; 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 — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D11 Test Reliability — Test reliability not measured — polyglot suite, one half not re-run
D12 Dependency Hygiene — Dependency hygiene not measured
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .c, .cc, .cpp, .java, .py, .rb, .rs, .ts, .tsx, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, JavaScript, Python, Ruby, Rust, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, Python, Ruby, Rust, TypeScript surface was not measured.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D32 Data Compliance (PII/GDPR) — 41 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — the repository's tests run on Microsoft.Testing.Platform (its build files say so) and wire up no coverage extension for it; the JavaScript/TypeScript half could not be measured — the jest suite in javascript/grid-ui/ ran and not one test passed (● Multiple configurations found:), so the coverage would describe the failed run, not the code. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — IC1 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
X1 Async correctness — X1 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — X13 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X14 Bypassable address classification — X14 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — X18 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — X2 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X21 Side-effecting pattern guard — X21 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X22 Contradicted release guard — X22 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X23 Unguarded diagnostic materialisation — X23 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X24 Document value interpolated into markup unescaped — Document value interpolated into markup unescaped could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X28 Index access outside its own emptiness guard — X28 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X29 Per-element action decided by a fixed element — X29 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X3 Exception handling — X3 reached only 17% of this repository's production lines — java (102,192 lines), javascript (41,369 lines), cpp (24,227 lines), python (23,878 lines), ruby (16,927 lines), typescript (11,885 lines), rust (7,884 lines), c (7,580 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message — its own wrapper, log4net, Console or Debug — so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
EmptyCatchBlock dotnet/src/webdriver/Chromium/ChromiumDriver.cs:181— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:341— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:126— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/Firefox/FirefoxDriver.cs:227— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/IE/InternetExplorerDriver.cs:184— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/Manager/SeleniumManager.cs:334— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/Manager/SeleniumManager.cs:350— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/Manager/SeleniumManager.cs:502— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/Manager/SeleniumManager.cs:303— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/Safari/SafariDriver.cs:189— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/TargetLocator.cs:156— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/WebDriver.cs:87— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/WebDriver.cs:819— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/WebDriver.cs:822— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/WebDriver.cs:825— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/WebDriver.cs:852— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/WebDriver.cs:855— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock dotnet/src/webdriver/WebDriver.cs:858— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
Namespace dependency cycle dotnet/src/webdriver/Command.cs:127— The namespaces OpenQA.Selenium ↔ OpenQA.Selenium.BiDi ↔ OpenQA.Selenium.BiDi.Browser ↔ OpenQA.Selenium.BiDi.BrowsingContext ↔ OpenQA.Selenium.BiDi.Emulation ↔ OpenQA.Selenium.BiDi.Input ↔ OpenQA.Selenium.BiDi.Json.Converters ↔ OpenQA.Selenium.BiDi.Log ↔ OpenQA.Selenium.BiDi.Network ↔ OpenQA.Selenium.BiDi.Script ↔ OpenQA.Selenium.BiDi.Session ↔ OpenQA.Selenium.BiDi.Storage ↔ OpenQA.Selenium.BiDi.WebExtension ↔ OpenQA.Selenium.Chromium ↔ OpenQA.Selenium.DevTools ↔ OpenQA.Selenium.Interactions ↔ OpenQA.Selenium.Internal ↔ OpenQA.Selenium.Remote depend on each other. The lightest dependency in the cycle is OpenQA.Selenium → OpenQA.Selenium.Chromium (OpenQA.Selenium.CommandJsonSerializerContext → OpenQA.Selenium.Chromium.ChromiumNetworkConditions, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Assertions commented out: GetSetDeleteAndClearAllCookies dotnet/test/webdriver/DevTools/DevToolsNetworkTests.cs:27— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
No assertions: ShouldBeAbleToCreateRemoteWebDriverWithNoSlashAtEndOfUri dotnet/test/remote/RemoteWebDriverSpecificTests.cs:51— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldBeAbleToWrapSubclassesOfSomethingImplementingTheWebDriverInterface dotnet/test/support/Events/EventFiringWebDriverTests.cs:218— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldHaveIdempotentDisposal dotnet/test/unit/webdriver/BiDi/SessionUnitTests.cs:57— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanCreateAWellFormedCookie dotnet/test/unit/webdriver/CookieTests.cs:27— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldAllowExpiryToBeNull dotnet/test/unit/webdriver/CookieTests.cs:106— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldBeAbleToOverrideTheWindowAlertMethod dotnet/test/webdriver/AlertsTests.cs: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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanQuitWhenAnAlertIsPresent dotnet/test/webdriver/AlertsTests.cs:446— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanActivate dotnet/test/webdriver/BiDi/BrowsingContext/BrowsingContextTests.cs:161— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanHandleUserPrompt dotnet/test/webdriver/BiDi/BrowsingContext/BrowsingContextTests.cs:198— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanAcceptUserPrompt dotnet/test/webdriver/BiDi/BrowsingContext/BrowsingContextTests.cs:208— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanDismissUserPrompt dotnet/test/webdriver/BiDi/BrowsingContext/BrowsingContextTests.cs:221— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanPassUserTextToPrompt dotnet/test/webdriver/BiDi/BrowsingContext/BrowsingContextTests.cs:234— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanSetViewportWithDevicePixelRatio dotnet/test/webdriver/BiDi/BrowsingContext/BrowsingContextTests.cs:331— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanUninstallExtension dotnet/test/webdriver/BiDi/WebExtension/WebExtensionTests.cs:76— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldFindGrandChildren dotnet/test/webdriver/ChildrenFindingTests.cs:313— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldScrollToClickOnAnElementHiddenByOverflow dotnet/test/webdriver/ClickScrollingTests.cs:51— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldBeAbleToClickOnAnElementHiddenByDoubleOverflow dotnet/test/webdriver/ClickScrollingTests.cs:73— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldBeAbleToClickOnAnElementHiddenByYOverflow dotnet/test/webdriver/ClickScrollingTests.cs:83— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldBeAbleToClickOnAnElementPartiallyHiddenByOverflow dotnet/test/webdriver/ClickScrollingTests.cs:92— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldBeAbleToClickRadioButtonScrolledIntoView dotnet/test/webdriver/ClickScrollingTests.cs:125— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanClickOnALinkThatOverflowsAndFollowIt dotnet/test/webdriver/ClickTests.cs:45— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldBeAbleToClickOnAnElementInTheViewport dotnet/test/webdriver/ClickTests.cs:211— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ClicksASurroundingStrongTag dotnet/test/webdriver/ClickTests.cs:221— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CanClickAnImageMapArea dotnet/test/webdriver/ClickTests.cs:229— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ShouldBeAbleToClickOnAnElementGreaterThanTwoViewports dotnet/test/webdriver/ClickTests.cs:246— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 58 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file javascript/atoms/dom.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/selenium-webdriver/project_bidi_schema_test.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/selenium-webdriver/generate_bidi.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/selenium-webdriver/project_bidi_schema.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/keyboard.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/events.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/action.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/typescript/core/locators.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/typescript/core/accessibility/accname.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/selenium-webdriver/normalize_bidi_ast.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/inject.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/mouse.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/webdriver/http/http.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/locators/relative.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/window.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/selenium-webdriver/normalize_bidi_ast_test.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/touchscreen.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/webdriver/capabilities.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/typescript/core/accessibility/roles.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/typescript/core/keyboard.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/chrome-driver/atoms.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/atoms/typescript/get-text.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file javascript/selenium-webdriver/bidi_schema_diff_test.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Sync-over-async blocking javascript/selenium-webdriver/firefox.js:566— `fs.statSync` in `installAddon` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking javascript/selenium-webdriver/lib/script.js:84— `fs.readFileSync` in `addDomMutationHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:1555— `fs.readFileSync` in `logMutationEvents` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:1558— `fs.readFileSync` in `logMutationEvents` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:1765— `fs.mkdirSync` in `downloadFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:1767— `fs.writeFileSync` in `downloadFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:1769— `fs.readFileSync` in `downloadFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:1775— `fs.writeFileSync` in `callback to forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking — 30 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/support/Events/EventFiringWebDriver.cs:822— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/support/Events/EventFiringWebDriver.cs:854— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/support/Events/EventFiringWebDriver.cs:886— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/support/Events/EventFiringWebDriver.cs:924— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/support/Events/EventFiringWebDriver.cs:950— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/support/UI/SlowLoadableComponent{T}.cs:102— `this.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/webdriver/Chromium/ChromiumDriver.cs:144— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/webdriver/Chromium/ChromiumDriver.cs:348— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/webdriver/Chromium/ChromiumDriver.cs:369— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking REDACTED:380— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking REDACTED:474— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/webdriver/DevTools/Network.cs:165— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/webdriver/DevTools/Network.cs:182— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/webdriver/DevTools/Network.cs:199— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking REDACTED:304— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking dotnet/src/webdriver/Firefox/FirefoxDriver.cs:197— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
TooManyMethods: Bridge rb/lib/selenium/webdriver/remote/bridge.rb:23— TooManyMethods — 105 methods. The bar is 30 methods; this is 75 over it, 3.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: RemoteWebDriver java/src/org/openqa/selenium/remote/RemoteWebDriver.java:114— TooManyMethods — 82 methods. The bar is 30 methods; this is 52 over it, 2.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: Schema rb/lib/selenium/webdriver/bidi/support/bidi_generate.rb:551— TooManyMethods — 81 methods. The bar is 30 methods; this is 51 over it, 2.70× 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: WebDriver py/selenium/webdriver/remote/webdriver.py:281— 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: ExpectedConditions java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:45— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WebDriver REDACTED:661— TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.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: Generator java/src/org/openqa/selenium/bidi/BiDiGenerator.java:165— TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.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.
TooManyMethods: LocalNode java/src/org/openqa/selenium/grid/node/local/LocalNode.java:137— 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: WebDriver dotnet/src/webdriver/WebDriver.cs— TooManyMethods — 458 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Actions java/src/org/openqa/selenium/interactions/Actions.java:48— 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: KubernetesSessionFactory java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:116— 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: BrowsingContext java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:44— 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: JsonInput java/src/org/openqa/selenium/json/JsonInput.java:45— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Schema py/generate_bidi_protocol.py:306— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Actions dotnet/src/webdriver/Interactions/Actions.cs— TooManyMethods — 202 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RemoteWebElement java/src/org/openqa/selenium/remote/RemoteWebElement.java:51— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× 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: EventFiringWebDriver dotnet/src/support/Events/EventFiringWebDriver.cs— TooManyMethods — 225 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NodeOptions java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:71— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GridRedisClient java/src/org/openqa/selenium/redis/GridRedisClient.java:44— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Deserializer rb/lib/selenium/webdriver/bidi/serialization/record.rb:73— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Driver rb/lib/selenium/webdriver/common/driver.rb:31— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RemoteWebDriver REDACTED— TooManyMethods — 149 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Script java/src/org/openqa/selenium/bidi/module/Script.java:58— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RedisBackedGridModel java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:63— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BiDiGenerate rb/lib/selenium/webdriver/bidi/support/bidi_generate.rb:39— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: bidi/BiDiGenerator.java java/src/org/openqa/selenium/bidi/BiDiGenerator.java— FileTooLong — 1675 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1175 over it, 3.35× 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/lib.rs rust/src/lib.rs— FileTooLong — 1299 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: SeleniumManager (115-1745). The bar is 500 significant lines; this is 799 over it, 2.60× 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: local/LocalNode.java java/src/org/openqa/selenium/grid/node/local/LocalNode.java— FileTooLong — 1136 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: LocalNode (137-1605). The bar is 500 significant lines; this is 636 over it, 2.27× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1120 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 620 over it, 2.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: kubernetes/KubernetesSessionFactory.java java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java— FileTooLong — 1019 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: KubernetesSessionFactory (116-1393). The bar is 500 significant lines; this is 519 over it, 2.04× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: devtools/CdpClientGenerator.java java/src/org/openqa/selenium/devtools/CdpClientGenerator.java— FileTooLong — 1016 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: CdpClientGenerator (61-1446). The bar is 500 significant lines; this is 516 over it, 2.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: support/bidi_generate.rb rb/lib/selenium/webdriver/bidi/support/bidi_generate.rb— FileTooLong — 978 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 478 over it, 1.96× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: remote/RemoteWebDriver.java java/src/org/openqa/selenium/remote/RemoteWebDriver.java— FileTooLong — 963 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: RemoteWebDriver (114-1529). The bar is 500 significant lines; this is 463 over it, 1.93× 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: ui/ExpectedConditions.java java/src/org/openqa/selenium/support/ui/ExpectedConditions.java— FileTooLong — 956 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: ExpectedConditions (45-1852). The bar is 500 significant lines; this is 456 over it, 1.91× 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: py/generate_bidi_protocol.py py/generate_bidi_protocol.py— FileTooLong — 914 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 414 over it, 1.83× 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: remote/webdriver.py py/selenium/webdriver/remote/webdriver.py— FileTooLong — 910 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 410 over it, 1.82× 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: py/generate_bidi.py py/generate_bidi.py— FileTooLong — 875 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 375 over it, 1.75× 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: selenium-webdriver/generate_bidi.mjs javascript/selenium-webdriver/generate_bidi.mjs— FileTooLong — 669 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 169 over it, 1.34× 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: atoms/dom.js javascript/atoms/dom.js— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 124 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Events/EventFiringWebDriver.cs dotnet/src/support/Events/EventFiringWebDriver.cs— FileTooLong — 618 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 118 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: selenium-webdriver/project_bidi_schema.mjs javascript/selenium-webdriver/project_bidi_schema.mjs— FileTooLong — 605 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 105 over it, 1.21× 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: RunningSessions/RunningSessions.tsx javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx— FileTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded), about 79% of them inside a single declaration: RunningSessions (175-746). The bar is 500 significant lines; this is 105 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/files.rs rust/src/files.rs— FileTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 69 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: redis/RedisBackedDistributor.java java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java— FileTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: RedisBackedDistributor (127-719). The bar is 500 significant lines; this is 49 over it, 1.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: config/NodeOptions.java java/src/org/openqa/selenium/grid/node/config/NodeOptions.java— FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: NodeOptions (71-796). The bar is 500 significant lines; this is 40 over it, 1.08× 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: local/LocalDistributor.java java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: LocalDistributor (108-684). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: private/_network_handlers.py py/private/_network_handlers.py— FileTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2 over it, 1.00× 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.
TodoComment dotnet/src/webdriver/BiDi/Network/ResponseData.cs:24— // TODO: should be unit — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/BiDi/Script/LocalValue.cs:52— // TODO: Extend converting from types — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/By.cs:372— // TODO(dawagner): This isn't ideal — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:113— // TODO handle nullability for this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:155— // TODO: Collect stack trace elements — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/DevTools/v156/V156JavaScript.cs:155— // TODO: Collect stack trace elements — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/DevTools/v157/V157JavaScript.cs:155— // TODO: Collect stack trace elements — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:538— // TODO: Consider checking the content of the response to ensure that the service is fully initialized — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/ErrorResponse.cs:93— // TODO: (JimEvans) Change this to return an Image. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/Proxy.cs:481— // TODO: this is probably inaccurate as to how this is supposed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/Response.cs:75— // TODO: Remove this if statement altogether; there should — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/WebDriver.cs:942— // TODO(JimEvans): Handle the case where the unexpected alert setting — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/WebElement.cs:276— // TODO: Returning this as a string is incorrect. The W3C WebDriver Specification — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/src/webdriver/WebElement.cs:611— // TODO: Remove either "keysToSend" or "value" property, whichever is not the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/test/webdriver/BiDi/BrowsingContext/BrowsingContextTests.cs:166— // TODO: Add assertion when https://w3c.github.io/webdriver-bidi/#type-browser-ClientWindowInfo is implemented
TodoComment dotnet/test/webdriver/CookieTests.cs:904— // TODO(JimEvan): Some coverage is better than none, so we — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/test/webdriver/DriverElementFindingTests.cs:87— //TODO(andre.nogueira): We're not checking the right elements are being returned! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/test/webdriver/ElementElementFindingTests.cs:24— // TODO(andre.nogueira): Find better name. This class is to distinguish — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/test/webdriver/ElementSelectingTests.cs:266— //TODO: Test disabled multi-selects — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/test/webdriver/ElementSelectingTests.cs:267— //TODO: Test selecting options — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment dotnet/test/webdriver/Interactions/CombinedInputActionsTests.cs:295— //TODO: Figure out why calling sendKey(Key.CONTROL + "a") and then — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/bidi/Connection.java:118— java/src/org/openqa/selenium/bidi/Connection.java:118-127 | java/src/org/openqa/selenium/devtools/Connection.java:149-158 — `java/src/org/openqa/selenium/bidi/Connection.java` and `java/src/org/openqa/selenium/devtools/Connection.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 38 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/Connection.java:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:92— java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:92-101 | java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:104-113 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:742— java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:742-751 | java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:753-762 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:742` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:392— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:392-401 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:463-472 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:548— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:548-557 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:607-616 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:206— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:206-215 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:418-427 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:206` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:514— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:514-523 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1376-1385 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:514` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:576— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:576-585 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1286-1295 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:422— java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:422-431 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:455-464 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/net/UrlChecker.java:85— java/src/org/openqa/selenium/net/UrlChecker.java:85-94 | java/src/org/openqa/selenium/net/UrlChecker.java:136-145 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/net/UrlChecker.java:85` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/remote/NewSessionPayload.java:316— java/src/org/openqa/selenium/remote/NewSessionPayload.java:316-325 | java/src/org/openqa/selenium/remote/NewSessionPayload.java:341-350 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/remote/NewSessionPayload.java:316` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/remote/RemoteWebDriver.java:429— java/src/org/openqa/selenium/remote/RemoteWebDriver.java:429-438 | java/src/org/openqa/selenium/remote/RemoteWebElement.java:373-382 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/remote/RemoteWebDriver.java:429` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:224— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:224-233 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:269-278 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/docker/client/V148Adapter.java:73— java/src/org/openqa/selenium/docker/client/V148Adapter.java:73-82 | java/src/org/openqa/selenium/docker/client/V148Adapter.java:211-220 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/docker/client/V148Adapter.java:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/docker/client/V148Adapter.java:221` calls `get` and `java/src/org/openqa/selenium/docker/client/V148Adapter.java:83` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:482— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:482-492 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:522-531 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/support/AbstractFindByBuilder.java:30— java/src/org/openqa/selenium/support/AbstractFindByBuilder.java:30-39 | java/src/org/openqa/selenium/support/FindBy.java:79-88 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/chrome/ChromeOptions.java:61— java/src/org/openqa/selenium/chrome/ChromeOptions.java:61-70 | java/src/org/openqa/selenium/edge/EdgeOptions.java:73-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) java/src/org/openqa/selenium/chromium/ChromiumDriverLogLevel.java:55— java/src/org/openqa/selenium/chromium/ChromiumDriverLogLevel.java:55-64 | java/src/org/openqa/selenium/firefox/FirefoxDriverLogLevel.java:56-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) rb/lib/selenium/webdriver/chrome/service.rb:30— rb/lib/selenium/webdriver/chrome/service.rb:30-39 | rb/lib/selenium/webdriver/edge/service.rb:30-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
ClassTooLong: SeleniumManager rust/src/lib.rs:115— ClassTooLong — 1073 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 145 methods. The bar is 400 significant lines; this is 673 over it, 2.68× 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: LocalNode java/src/org/openqa/selenium/grid/node/local/LocalNode.java:137— ClassTooLong — 1020 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 400 significant lines; this is 620 over it, 2.55× 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: CdpClientGenerator java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:61— ClassTooLong — 976 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 576 over it, 2.44× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ExpectedConditions java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:45— ClassTooLong — 933 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 400 significant lines; this is 533 over it, 2.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: KubernetesSessionFactory java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:116— ClassTooLong — 924 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 524 over it, 2.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: RemoteWebDriver java/src/org/openqa/selenium/remote/RemoteWebDriver.java:114— ClassTooLong — 870 significant lines (blank, comment-only and punctuation-only lines excluded), 82 methods. The bar is 400 significant lines; this is 470 over it, 2.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: NodeOptions java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:71— ClassTooLong — 490 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 90 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: RunningSessions javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx:1— ClassTooLong — 477 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 77 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RedisBackedDistributor java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:127— ClassTooLong — 459 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 59 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: JsonInput java/src/org/openqa/selenium/json/JsonInput.java:45— ClassTooLong — 445 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 45 over it, 1.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FirefoxManager rust/src/firefox.rs:76— ClassTooLong — 422 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 3 methods, 3 blocks, lines 76-661. The bar is 400 significant lines; this is 22 over it, 1.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LocalDistributor java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:108— ClassTooLong — 421 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 21 over it, 1.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: RedisBackedNodeRegistry java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:87— ClassTooLong — 418 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 18 over it, 1.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: RedisBackedGridModel java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:63— ClassTooLong — 413 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 13 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ChromeManager rust/src/chrome.rs:73— ClassTooLong — 411 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 12 methods, 3 blocks, lines 73-694. The bar is 400 significant lines; this is 11 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: JdkHttpClient java/src/org/openqa/selenium/remote/http/jdk/JdkHttpClient.java:76— ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 10 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:708— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:708-716 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1779-1787 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/bidi/Connection.java:164— java/src/org/openqa/selenium/bidi/Connection.java:164-172 | java/src/org/openqa/selenium/devtools/Connection.java:200-208 — `java/src/org/openqa/selenium/bidi/Connection.java` and `java/src/org/openqa/selenium/devtools/Connection.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 38 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/Connection.java:164` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/bidi/module/LogInspector.java:58— java/src/org/openqa/selenium/bidi/module/LogInspector.java:58-66 | java/src/org/openqa/selenium/bidi/module/SpeculationInspector.java:50-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/bidi/script/LocalValue.java:116— java/src/org/openqa/selenium/bidi/script/LocalValue.java:116-124 | java/src/org/openqa/selenium/bidi/script/LocalValue.java:199-207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:206— java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:206-214 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:263-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/remote/ElementLocation.java:68— java/src/org/openqa/selenium/remote/ElementLocation.java:68-76 | java/src/org/openqa/selenium/remote/ElementLocation.java:112-120 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/remote/ElementLocation.java:68` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:107— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:107-115 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:122-130 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) dotnet/src/webdriver/BiDi/EventStream.cs:49— dotnet/src/webdriver/BiDi/EventStream.cs:49-57 | dotnet/src/webdriver/BiDi/Subscription.cs:69-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) dotnet/src/webdriver/Remote/DesiredCapabilities.cs:128— dotnet/src/webdriver/Remote/DesiredCapabilities.cs:128-136 | dotnet/src/webdriver/Remote/ReadOnlyDesiredCapabilities.cs:90-98 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `dotnet/src/webdriver/Remote/DesiredCapabilities.cs:138` calls `SetCapability` and `dotnet/src/webdriver/Remote/ReadOnlyDesiredCapabilities.cs:99` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/devtools/NetworkInterceptor.java:106— java/src/org/openqa/selenium/devtools/NetworkInterceptor.java:106-114 | java/src/org/openqa/selenium/devtools/idealized/Network.java:301-309 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:374— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:374-382 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:446-454 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:437— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:437-445 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:506-514 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:519— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:519-527 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:577-585 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/chrome/ChromeDriver.java:91— java/src/org/openqa/selenium/chrome/ChromeDriver.java:91-99 | java/src/org/openqa/selenium/edge/EdgeDriver.java:63-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/chrome/ChromeDriver.java:91` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `options` to `ChromeOptions` in one and `EdgeOptions` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:170— java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:170-178 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:243-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) py/private/_script_handlers.py:191— py/private/_script_handlers.py:191-199 | py/private/_script_handlers.py:205-213 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `py/private/_script_handlers.py:191` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1666— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1666-1672 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1922-1928 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/chromium/ChromiumOptions.java:333— java/src/org/openqa/selenium/chromium/ChromiumOptions.java:333-339 | java/src/org/openqa/selenium/firefox/FirefoxOptions.java:372-378 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/chromium/ChromiumOptions.java:333` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:531— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:531-537 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:590-596 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:531` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/grid/distributor/selector/DefaultSlotSelector.java:65— java/src/org/openqa/selenium/grid/distributor/selector/DefaultSlotSelector.java:65-71 | java/src/org/openqa/selenium/grid/distributor/selector/GreedySlotSelector.java:65-71 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/distributor/selector/DefaultSlotSelector.java:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/remote/ElementLocation.java:53— java/src/org/openqa/selenium/remote/ElementLocation.java:53-59 | java/src/org/openqa/selenium/remote/ElementLocation.java:97-103 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/remote/ElementLocation.java:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:137— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:137-143 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:106-112 — before extracting anything, compare `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java` and `java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:447— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:447-453 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:516-522 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/grid/distributor/remote/RemoteDistributor.java:62— java/src/org/openqa/selenium/grid/distributor/remote/RemoteDistributor.java:62-68 | java/src/org/openqa/selenium/grid/node/remote/RemoteNode.java:117-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/grid/sessionmap/remote/RemoteSessionMap.java:68— java/src/org/openqa/selenium/grid/sessionmap/remote/RemoteSessionMap.java:68-74 | java/src/org/openqa/selenium/grid/sessionqueue/remote/RemoteNewSessionQueue.java:203-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/interactions/PointerInput.java:257— java/src/org/openqa/selenium/interactions/PointerInput.java:257-263 | java/src/org/openqa/selenium/interactions/WheelInput.java:123-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/safari/SafariDriverService.java:108— java/src/org/openqa/selenium/safari/SafariDriverService.java:108-114 | java/src/org/openqa/selenium/safari/SafariTechPreviewDriverService.java:108-114 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) java/src/org/openqa/selenium/bidi/module/LogInspector.java:148— java/src/org/openqa/selenium/bidi/module/LogInspector.java:148-154 | java/src/org/openqa/selenium/bidi/module/SpeculationInspector.java:62-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `consumer` to `Consumer<LogEntry>` in one and `Consumer<PrefetchStatusUpdatedParameters>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/bidi/module/SpeculationInspector.java:70` calls `removeListener` and `java/src/org/openqa/selenium/bidi/module/LogInspector.java:156` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) py/selenium/webdriver/chromium/webdriver.py:49— py/selenium/webdriver/chromium/webdriver.py:49-55 | py/selenium/webdriver/firefox/webdriver.py:54-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:512— java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:512-516 | java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:648-652 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:512` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/support/FindAll.java:53— java/src/org/openqa/selenium/support/FindAll.java:53-57 | java/src/org/openqa/selenium/support/FindBys.java:52-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `findBys` to `FindAll` in one and `FindBys` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/docker/client/InspectContainer.java:50— java/src/org/openqa/selenium/docker/client/InspectContainer.java:50-54 | java/src/org/openqa/selenium/docker/client/ListImages.java:52-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/grid/TemplateGridServerCommand.java:80— java/src/org/openqa/selenium/grid/TemplateGridServerCommand.java:80-84 | java/src/org/openqa/selenium/grid/web/GridUiRoute.java:91-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:305— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:305-315 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1298-1302 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:305` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:541— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:541-545 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1368-1372 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/grid/sessionmap/GetFromSessionMap.java:42— java/src/org/openqa/selenium/grid/sessionmap/GetFromSessionMap.java:42-46 | java/src/org/openqa/selenium/grid/sessionmap/RemoveFromSession.java:38-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/grid/sessionqueue/AddBackToSessionQueue.java:43— java/src/org/openqa/selenium/grid/sessionqueue/AddBackToSessionQueue.java:43-47 | java/src/org/openqa/selenium/grid/sessionqueue/RemoveFromSessionQueue.java:42-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/grid/sessionqueue/SessionCreated.java:43— java/src/org/openqa/selenium/grid/sessionqueue/SessionCreated.java:43-47 | java/src/org/openqa/selenium/grid/sessionqueue/SessionNotCreated.java:44-48 — before extracting anything, compare `java/src/org/openqa/selenium/grid/sessionqueue/SessionCreated.java` and `java/src/org/openqa/selenium/grid/sessionqueue/SessionNotCreated.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/grid/data/SessionClosedEvent.java:65— java/src/org/openqa/selenium/grid/data/SessionClosedEvent.java:65-70 | java/src/org/openqa/selenium/grid/data/SessionCreatedEvent.java:57-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/chrome/ChromeDriver.java:126— java/src/org/openqa/selenium/chrome/ChromeDriver.java:126-130 | java/src/org/openqa/selenium/edge/EdgeDriver.java:98-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1040— java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1040-1044 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1060-1064 — 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.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×11
Edited copy of a member (18 corresponding lines) java/src/org/openqa/selenium/firefox/FirefoxOptions.java:533— java/src/org/openqa/selenium/firefox/FirefoxOptions.java:533-550 | java/src/org/openqa/selenium/firefox/FirefoxOptions.java:598-615 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) java/src/org/openqa/selenium/bidi/module/Script.java:355— java/src/org/openqa/selenium/bidi/module/Script.java:355-376 | java/src/org/openqa/selenium/bidi/module/Script.java:384-401 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) rust/src/rules.rs:34— rust/src/rules.rs:34-51 | rust/src/skills.rs:26-43 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:513— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:513-539 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1375-1392 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) java/src/org/openqa/selenium/grid/jmx/MBean.java:137— java/src/org/openqa/selenium/grid/jmx/MBean.java:137-156 | java/src/org/openqa/selenium/grid/jmx/MBean.java:158-175 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:534— java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:534-553 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:662-679 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1420— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1420-1438 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1471-1488 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) dotnet/src/support/Events/EventFiringWebDriver.cs:1666— dotnet/src/support/Events/EventFiringWebDriver.cs:1666-1683 | dotnet/src/support/Events/EventFiringWebDriver.cs:1799-1816 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) REDACTED:146— REDACTED:146-163 | REDACTED:177-194 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) dotnet/src/webdriver/RelativeBy.cs:297— dotnet/src/webdriver/RelativeBy.cs:297-314 | dotnet/src/webdriver/RelativeBy.cs:317-334 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) dotnet/src/webdriver/Interactions/Actions.cs:650— dotnet/src/webdriver/Interactions/Actions.cs:650-669 | dotnet/src/support/Extensions/WebDriverExtensions.cs:127-144 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
X20 · Mistyped argument guard· Argument guard throws the exception its own condition disproves · ×11
Argument guard throws the exception its own condition disproves dotnet/src/webdriver/CommandInfoRepository.cs:119— The guard on line 117 rejects `commandName` and line 119 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(commandName)` is true of a value that is NOT null: it is satisfied by an EMPTY `commandName`, and on that path `commandName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves REDACTED:71— The guard on line 69 rejects `endpointAddress` and line 71 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(endpointAddress)` is true of a value that is NOT null: it is satisfied by an EMPTY `endpointAddress`, and on that path `endpointAddress` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves dotnet/src/webdriver/Firefox/FirefoxDriver.cs:301— The guard on line 299 rejects `addOnDirectoryToInstall` and line 301 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(addOnDirectoryToInstall)` is true of a value that is NOT null: it is satisfied by an EMPTY `addOnDirectoryToInstall`, and on that path `addOnDirectoryToInstall` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves dotnet/src/webdriver/Firefox/FirefoxDriver.cs:330— The guard on line 328 rejects `addOnFileToInstall` and line 330 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(addOnFileToInstall)` is true of a value that is NOT null: it is satisfied by an EMPTY `addOnFileToInstall`, and on that path `addOnFileToInstall` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves dotnet/src/webdriver/Firefox/FirefoxDriver.cs:359— The guard on line 357 rejects `base64EncodedAddOn` and line 359 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(base64EncodedAddOn)` is true of a value that is NOT null: it is satisfied by an EMPTY `base64EncodedAddOn`, and on that path `base64EncodedAddOn` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves dotnet/src/webdriver/Firefox/FirefoxDriver.cs:381— The guard on line 379 rejects `addOnId` and line 381 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(addOnId)` is true of a value that is NOT null: it is satisfied by an EMPTY `addOnId`, and on that path `addOnId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves dotnet/src/webdriver/Firefox/Internal/IniFileReader.cs:41— The guard on line 39 rejects `fileName` and line 41 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves dotnet/src/webdriver/Firefox/Internal/IniFileReader.cs:110— The guard on line 108 rejects `sectionName` and line 110 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(sectionName)` is true of a value that is NOT null: it is satisfied by an EMPTY `sectionName`, and on that path `sectionName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves dotnet/src/webdriver/Firefox/Internal/IniFileReader.cs:117— The guard on line 115 rejects `valueName` and line 117 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(valueName)` is true of a value that is NOT null: it is satisfied by an EMPTY `valueName`, and on that path `valueName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves dotnet/src/webdriver/RelativeBy.cs:320— The guard on line 318 rejects `direction` and line 320 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(direction)` is true of a value that is NOT null: it is satisfied by an EMPTY `direction`, and on that path `direction` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves dotnet/src/webdriver/Safari/SafariDriver.cs:220— The guard on line 218 rejects `permissionName` and line 220 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(permissionName)` is true of a value that is NOT null: it is satisfied by an EMPTY `permissionName`, and on that path `permissionName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
MethodTooLong: ModuleGenerator.main java/src/dev/selenium/tools/modules/ModuleGenerator.java:98— MethodTooLong — main runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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: JdkHttpClient.openSocket java/src/org/openqa/selenium/remote/http/jdk/JdkHttpClient.java:159— MethodTooLong — openSocket 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.
MethodTooLong: KubernetesSessionFactory.apply java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:317— MethodTooLong — apply runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.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: LocalNode.newSession java/src/org/openqa/selenium/grid/node/local/LocalNode.java:499— MethodTooLong — newSession 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.
MethodTooLong: LocalNode.<init> java/src/org/openqa/selenium/grid/node/local/LocalNode.java:172— MethodTooLong — <init> 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.
MethodTooLong: SeleniumManager.download_browser rust/src/lib.rs:240— MethodTooLong — download_browser runs 128 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: W3CHttpCommandCodec.amendParameters java/src/org/openqa/selenium/remote/codec/w3c/W3CHttpCommandCodec.java:169— MethodTooLong — amendParameters runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DockerSessionFactory.apply java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:161— MethodTooLong — apply 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: KubernetesOptions.getKubernetesSessionFactories java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:76— MethodTooLong — getKubernetesSessionFactories runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: DriverServiceSessionFactory.apply java/src/org/openqa/selenium/grid/node/config/DriverServiceSessionFactory.java:110— MethodTooLong — apply runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×10
Edited copy of a member (10 corresponding lines) java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:311— java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:311-320 | java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:336-347 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:203— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:203-212 | java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:218-228 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) dotnet/src/webdriver/WebElement.cs:368— dotnet/src/webdriver/WebElement.cs:368-377 | dotnet/src/webdriver/WebElement.cs:403-412 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) dotnet/src/webdriver/WebElement.cs:199— dotnet/src/webdriver/WebElement.cs:199-208 | dotnet/src/webdriver/WebElement.cs:452-468 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) dotnet/src/webdriver/WebDriver.cs:1223— dotnet/src/webdriver/WebDriver.cs:1223-1232 | dotnet/src/webdriver/WebDriver.cs:1282-1292 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:547— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:547-556 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1332-1342 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) java/src/org/openqa/selenium/docker/Device.java:58— java/src/org/openqa/selenium/docker/Device.java:58-69 | java/src/org/openqa/selenium/remote/ShadowRoot.java:71-80 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) java/src/org/openqa/selenium/remote/ErrorCodes.java:361— java/src/org/openqa/selenium/remote/ErrorCodes.java:361-374 | java/src/org/openqa/selenium/remote/ErrorCodes.java:376-385 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) py/selenium/webdriver/chrome/service.py:49— py/selenium/webdriver/chrome/service.py:49-58 | py/selenium/webdriver/edge/service.py:46-58 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) dotnet/src/webdriver/Chromium/ChromiumDriver.cs:249— dotnet/src/webdriver/Chromium/ChromiumDriver.cs:249-259 | dotnet/src/webdriver/Firefox/FirefoxDriver.cs:378-387 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×10
Edited copy of a member (8 corresponding lines) py/selenium/webdriver/support/event_firing_webdriver.py:114— py/selenium/webdriver/support/event_firing_webdriver.py:114-121 | py/selenium/webdriver/support/event_firing_webdriver.py:195-202 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) java/src/org/openqa/selenium/bidi/script/MapLocalValue.java:35— java/src/org/openqa/selenium/bidi/script/MapLocalValue.java:35-42 | java/src/org/openqa/selenium/bidi/script/ObjectLocalValue.java:35-42 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) py/selenium/webdriver/support/event_firing_webdriver.py:138— py/selenium/webdriver/support/event_firing_webdriver.py:138-145 | py/selenium/webdriver/support/event_firing_webdriver.py:205-212 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) java/src/org/openqa/selenium/chrome/ElectronDriver.java:61— java/src/org/openqa/selenium/chrome/ElectronDriver.java:61-68 | java/src/org/openqa/selenium/safari/SafariDriver.java:95-102 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) java/src/org/openqa/selenium/remote/RemoteTags.java:51— java/src/org/openqa/selenium/remote/RemoteTags.java:51-58 | java/src/org/openqa/selenium/remote/tracing/opentelemetry/SeleniumSpanExporter.java:50-57 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) rust/src/firefox.rs:537— rust/src/firefox.rs:537-549 | rust/src/chrome.rs:645-652 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) java/src/org/openqa/selenium/interactions/KeyInput.java:56— java/src/org/openqa/selenium/interactions/KeyInput.java:56-63 | java/src/org/openqa/selenium/interactions/WheelInput.java:66-73 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) java/src/org/openqa/selenium/grid/data/TraceSessionRequest.java:30— java/src/org/openqa/selenium/grid/data/TraceSessionRequest.java:30-37 | java/src/org/openqa/selenium/remote/tracing/HttpTracing.java:34-41 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:471— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:471-479 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:286-293 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:460— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:460-468 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:276-283 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×10
Edited copy of a member (7 corresponding lines) java/src/org/openqa/selenium/bidi/browsingcontext/DownloadCanceled.java:32— java/src/org/openqa/selenium/bidi/browsingcontext/DownloadCanceled.java:32-38 | java/src/org/openqa/selenium/bidi/browsingcontext/DownloadCompleted.java:40-47 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:390— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:390-396 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:688-696 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) dotnet/src/webdriver/Remote/DesiredCapabilities.cs:228— dotnet/src/webdriver/Remote/DesiredCapabilities.cs:228-234 | dotnet/src/webdriver/Remote/ReadOnlyDesiredCapabilities.cs:177-183 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) java/src/org/openqa/selenium/devtools/NetworkInterceptor.java:117— java/src/org/openqa/selenium/devtools/NetworkInterceptor.java:117-123 | java/src/org/openqa/selenium/devtools/idealized/Network.java:339-345 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) java/src/org/openqa/selenium/grid/distributor/remote/RemoteDistributor.java:109— java/src/org/openqa/selenium/grid/distributor/remote/RemoteDistributor.java:109-116 | java/src/org/openqa/selenium/grid/sessionqueue/remote/RemoteNewSessionQueue.java:185-191 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) dotnet/src/webdriver/Firefox/FirefoxDriver.cs:394— dotnet/src/webdriver/Firefox/FirefoxDriver.cs:394-400 | dotnet/src/webdriver/WebDriver.cs:422-428 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) java/src/org/openqa/selenium/bidi/Module.java:38— java/src/org/openqa/selenium/bidi/Module.java:38-44 | java/src/org/openqa/selenium/bidi/emulation/Emulation.java:30-38 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerOptions.java:256— java/src/org/openqa/selenium/grid/node/docker/DockerOptions.java:256-262 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:368-374 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:295— java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:295-302 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:393-399 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) java/src/org/openqa/selenium/interactions/PointerInput.java:315— java/src/org/openqa/selenium/interactions/PointerInput.java:315-322 | java/src/org/openqa/selenium/print/PrintOptions.java:91-97 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 3) dotnet/src/webdriver/Firefox/FirefoxDriver.cs:202— dotnet/src/webdriver/Firefox/FirefoxDriver.cs:202-210 | dotnet/src/webdriver/IE/InternetExplorerDriver.cs:162-170 | dotnet/src/webdriver/Safari/SafariDriver.cs:167-175 — before extracting anything, compare `dotnet/src/webdriver/IE/InternetExplorerDriver.cs` and `dotnet/src/webdriver/Safari/SafariDriver.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/webdriver/Firefox/FirefoxDriver.cs:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `dotnet/src/webdriver/Firefox/FirefoxDriver.cs:211` calls `GetBrowserPathAsync`, `ConfigureAwait` and `dotnet/src/webdriver/IE/InternetExplorerDriver.cs:171` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 3) java/src/org/openqa/selenium/chrome/ChromeDriver.java:103— java/src/org/openqa/selenium/chrome/ChromeDriver.java:103-111 | java/src/org/openqa/selenium/edge/EdgeDriver.java:75-83 | java/src/org/openqa/selenium/firefox/FirefoxDriver.java:115-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Note first that the copies are not typed on the same thing: the declarations holding them bind `options` to `ChromeOptions` in one and `EdgeOptions` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Network.java:76— java/src/org/openqa/selenium/devtools/v155/v155Network.java:76-84 | java/src/org/openqa/selenium/devtools/v156/v156Network.java:76-84 | java/src/org/openqa/selenium/devtools/v157/v157Network.java:76-84 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Network.java` and `java/src/org/openqa/selenium/devtools/v156/v156Network.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Fetch` names `org.openqa.selenium.devtools.v155.fetch.Fetch` in one and `org.openqa.selenium.devtools.v156.fetch.Fetch` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 3) java/src/org/openqa/selenium/docker/client/V140Adapter.java:72— java/src/org/openqa/selenium/docker/client/V140Adapter.java:72-80 | java/src/org/openqa/selenium/docker/client/V144Adapter.java:83-91 | java/src/org/openqa/selenium/docker/client/V148Adapter.java:156-164 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/docker/client/V140Adapter.java:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) java/src/org/openqa/selenium/firefox/AddHasFullPageScreenshot.java:71— java/src/org/openqa/selenium/firefox/AddHasFullPageScreenshot.java:71-79 | java/src/org/openqa/selenium/remote/RemoteWebDriver.java:430-438 | java/src/org/openqa/selenium/remote/RemoteWebElement.java:374-382 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/firefox/AddHasFullPageScreenshot.java:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:163— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:163-171 | java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:305-313 | java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:339-347 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:143— dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:143-151 | dotnet/src/webdriver/DevTools/v156/V156JavaScript.cs:143-151 | dotnet/src/webdriver/DevTools/v157/V157JavaScript.cs:143-151 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs` and `dotnet/src/webdriver/DevTools/v156/V156JavaScript.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 3) dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:155— dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:155-163 | dotnet/src/webdriver/DevTools/v156/V156JavaScript.cs:155-163 | dotnet/src/webdriver/DevTools/v157/V157JavaScript.cs:155-163 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs` and `dotnet/src/webdriver/DevTools/v156/V156JavaScript.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 3) java/src/org/openqa/selenium/bidi/module/Permission.java:36— java/src/org/openqa/selenium/bidi/module/Permission.java:36-44 | java/src/org/openqa/selenium/bidi/module/Storage.java:43-51 | java/src/org/openqa/selenium/bidi/webextension/WebExtension.java:32-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Network.java:181— java/src/org/openqa/selenium/devtools/v155/v155Network.java:181-189 | java/src/org/openqa/selenium/devtools/v156/v156Network.java:181-189 | java/src/org/openqa/selenium/devtools/v157/v157Network.java:181-189 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Network.java` and `java/src/org/openqa/selenium/devtools/v156/v156Network.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `Fetch` names `org.openqa.selenium.devtools.v155.fetch.Fetch` in one and `org.openqa.selenium.devtools.v156.fetch.Fetch` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 2) dotnet/src/webdriver/BiDi/Input/SourceActions.cs:78— dotnet/src/webdriver/BiDi/Input/SourceActions.cs:78-85 | dotnet/src/webdriver/BiDi/Input/SourceActions.cs:131-143 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/webdriver/BiDi/Input/SourceActions.cs:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) dotnet/src/webdriver/ShadowRoot.cs:96— dotnet/src/webdriver/ShadowRoot.cs:96-103 | dotnet/src/webdriver/ShadowRoot.cs:126-133 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/webdriver/ShadowRoot.cs:96` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) java/src/org/openqa/selenium/docker/client/V144Adapter.java:112— java/src/org/openqa/selenium/docker/client/V144Adapter.java:112-119 | java/src/org/openqa/selenium/docker/client/V148Adapter.java:238-245 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/docker/client/V144Adapter.java:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) java/src/org/openqa/selenium/grid/node/config/DriverServiceSessionFactory.java:341— java/src/org/openqa/selenium/grid/node/config/DriverServiceSessionFactory.java:341-348 | java/src/org/openqa/selenium/remote/service/DriverFinder.java:185-192 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/config/DriverServiceSessionFactory.java:341` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) java/src/org/openqa/selenium/safari/SafariDriverService.java:156— java/src/org/openqa/selenium/safari/SafariDriverService.java:156-163 | java/src/org/openqa/selenium/safari/SafariTechPreviewDriverService.java:157-164 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:498— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:498-505 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1354-1361 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) java/src/org/openqa/selenium/bidi/webextension/ExtensionArchivePath.java:32— java/src/org/openqa/selenium/bidi/webextension/ExtensionArchivePath.java:32-39 | java/src/org/openqa/selenium/bidi/webextension/ExtensionPath.java:27-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) java/src/org/openqa/selenium/bidi/network/Initiator.java:44— java/src/org/openqa/selenium/bidi/network/Initiator.java:44-51 | java/src/org/openqa/selenium/bidi/script/RemoteValue.java:80-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/bidi/script/RemoteValue.java:90` calls `Json` and `java/src/org/openqa/selenium/bidi/network/Initiator.java:54` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) java/src/org/openqa/selenium/safari/SafariDriverService.java:171— java/src/org/openqa/selenium/safari/SafariDriverService.java:171-178 | java/src/org/openqa/selenium/safari/SafariTechPreviewDriverService.java:168-175 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/safari/SafariDriverService.java:171` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) py/selenium/webdriver/chrome/remote_connection.py:34— py/selenium/webdriver/chrome/remote_connection.py:34-41 | py/selenium/webdriver/edge/remote_connection.py:34-41 — `py/selenium/webdriver/chrome/remote_connection.py` and `py/selenium/webdriver/edge/remote_connection.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 8 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) dotnet/src/webdriver/Remote/DesiredCapabilities.cs:229— dotnet/src/webdriver/Remote/DesiredCapabilities.cs:229-234 | dotnet/src/webdriver/Remote/ReadOnlyDesiredCapabilities.cs:178-183 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) dotnet/src/webdriver/Internal/Base64UrlEncoder.cs:78— dotnet/src/webdriver/Internal/Base64UrlEncoder.cs:78-83 | dotnet/src/webdriver/Internal/Base64UrlEncoder.cs:95-100 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) java/src/org/openqa/selenium/bidi/script/MapLocalValue.java:37— java/src/org/openqa/selenium/bidi/script/MapLocalValue.java:37-42 | java/src/org/openqa/selenium/bidi/script/ObjectLocalValue.java:37-42 — before extracting anything, compare `java/src/org/openqa/selenium/bidi/script/MapLocalValue.java` and `java/src/org/openqa/selenium/bidi/script/ObjectLocalValue.java` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/script/MapLocalValue.java:37` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2106— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2106-2111 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2123-2128 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) java/src/org/openqa/selenium/bidi/Connection.java:355— java/src/org/openqa/selenium/bidi/Connection.java:355-360 | java/src/org/openqa/selenium/devtools/Connection.java:267-272 — `java/src/org/openqa/selenium/bidi/Connection.java` and `java/src/org/openqa/selenium/devtools/Connection.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 38 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/Connection.java:355` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) java/src/org/openqa/selenium/bidi/log/StackFrame.java:35— java/src/org/openqa/selenium/bidi/log/StackFrame.java:35-40 | java/src/org/openqa/selenium/bidi/script/StackFrame.java:36-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) java/src/org/openqa/selenium/bidi/network/ContinueResponseParameters.java:35— java/src/org/openqa/selenium/bidi/network/ContinueResponseParameters.java:35-40 | java/src/org/openqa/selenium/bidi/network/ProvideResponseParameters.java:39-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:296— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:296-301 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:391-396 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) py/private/_network_handlers.py:458— py/private/_network_handlers.py:458-463 | py/private/_network_handlers.py:595-600 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `py/private/_network_handlers.py:601` calls `get`, `isinstance` and `py/private/_network_handlers.py:464` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) rust/src/main.rs:207— rust/src/main.rs:207-212 | rust/src/main.rs:224-229 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `rust/src/main.rs:207` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Unfinished stub — throws NotImplementedException dotnet/src/webdriver/BiDi/BrowsingContext/DownloadEndEvent.cs:68— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException dotnet/src/webdriver/BiDi/Input/Origin.cs:31— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException dotnet/src/webdriver/BiDi/Json/Converters/PrintPageRangeConverter.cs:28— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException dotnet/src/webdriver/BiDi/Log/EntryAddedEvent.cs:83— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException dotnet/src/webdriver/BiDi/Script/Evaluate.cs:94— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException dotnet/src/webdriver/BiDi/Script/RealmInfo.cs:101— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException dotnet/src/webdriver/BiDi/Script/RealmInfoEvent.cs:86— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException dotnet/src/webdriver/BiDi/Script/RemoteValue.cs:403— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException dotnet/src/webdriver/DriverOptions.cs:189— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException dotnet/src/webdriver/ElementCoordinates.cs:45— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Hotspot: javascript/selenium-webdriver/project_bidi_schema.mjs javascript/selenium-webdriver/project_bidi_schema.mjs:873— javascript/selenium-webdriver/project_bidi_schema.mjs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in project_bidi_schema.checkSchema at line 873. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:37:07 +01:00' --until='2026-11-13 13:37:07 +01:00' --full-history --no-merges -- javascript/selenium-webdriver/project_bidi_schema.mjs`: 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: javascript/selenium-webdriver/bidi/serialization/record.js javascript/selenium-webdriver/bidi/serialization/record.js:50— javascript/selenium-webdriver/bidi/serialization/record.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in record.validateValue at line 50. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:37:07 +01:00' --until='2026-11-13 13:37:07 +01:00' --full-history --no-merges -- javascript/selenium-webdriver/bidi/serialization/record.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: javascript/selenium-webdriver/generate_bidi.mjs javascript/selenium-webdriver/generate_bidi.mjs:942— javascript/selenium-webdriver/generate_bidi.mjs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in generate_bidi.generateDomainFile at line 942. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:37:07 +01:00' --until='2026-11-13 13:37:07 +01:00' --full-history --no-merges -- javascript/selenium-webdriver/generate_bidi.mjs`: 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: rust/src/lib.rs rust/src/lib.rs:240— rust/src/lib.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in SeleniumManager::download_browser at line 240. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:37:07 +01:00' --until='2026-11-13 13:37:07 +01:00' --full-history --no-merges -- rust/src/lib.rs`: 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: javascript/selenium-webdriver/testing/index.js javascript/selenium-webdriver/testing/index.js:315— javascript/selenium-webdriver/testing/index.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in Environment.builder at line 315. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:37:07 +01:00' --until='2026-11-13 13:37:07 +01:00' --full-history --no-merges -- javascript/selenium-webdriver/testing/index.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: java/src/org/openqa/selenium/remote/codec/w3c/W3CHttpCommandCodec.java java/src/org/openqa/selenium/remote/codec/w3c/W3CHttpCommandCodec.java:169— java/src/org/openqa/selenium/remote/codec/w3c/W3CHttpCommandCodec.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in W3CHttpCommandCodec.amendParameters at line 169. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:37:07 +01:00' --until='2026-11-13 13:37:07 +01:00' --full-history --no-merges -- java/src/org/openqa/selenium/remote/codec/w3c/W3CHttpCommandCodec.java`: 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: py/selenium/webdriver/common/_bidi/serialization.py py/selenium/webdriver/common/_bidi/serialization.py:432— py/selenium/webdriver/common/_bidi/serialization.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in serialization._read_scalar at line 432. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:37:07 +01:00' --until='2026-11-13 13:37:07 +01:00' --full-history --no-merges -- py/selenium/webdriver/common/_bidi/serialization.py`: 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: java/src/dev/selenium/tools/modules/ModuleGenerator.java java/src/dev/selenium/tools/modules/ModuleGenerator.java:98— java/src/dev/selenium/tools/modules/ModuleGenerator.java changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in ModuleGenerator.main at line 98. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:37:07 +01:00' --until='2026-11-13 13:37:07 +01:00' --full-history --no-merges -- java/src/dev/selenium/tools/modules/ModuleGenerator.java`: 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: py/selenium/webdriver/common/api_request_context.py py/selenium/webdriver/common/api_request_context.py:103— py/selenium/webdriver/common/api_request_context.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in api_request_context._cookie_matches at line 103. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:37:07 +01:00' --until='2026-11-13 13:37:07 +01:00' --full-history --no-merges -- py/selenium/webdriver/common/api_request_context.py`: 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.
FunctionTooLong: RunningSessions.RunningSessions javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx:175— FunctionTooLong — RunningSessions runs 477 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 377 over it, 4.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: Overview.Overview javascript/grid-ui/src/screens/Overview/Overview.tsx:46— FunctionTooLong — Overview runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× 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: roles.implicitRole javascript/atoms/typescript/core/accessibility/roles.ts:248— FunctionTooLong — implicitRole runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: get-attribute.get javascript/atoms/typescript/get-attribute.ts:28— FunctionTooLong — get runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: shown.isShownElement javascript/atoms/typescript/core/shown.ts:28— FunctionTooLong — isShownElement runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Node.Node javascript/grid-ui/src/components/Node/Node.tsx:78— FunctionTooLong — Node runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: LiveView.LiveView javascript/grid-ui/src/components/LiveView/LiveView.tsx:32— FunctionTooLong — LiveView runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ColumnSelector.ColumnSelector javascript/grid-ui/src/components/RunningSessions/ColumnSelector.tsx:41— FunctionTooLong — ColumnSelector 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.
FunctionTooLong: events.bot.events.TouchEventFactory_.create javascript/atoms/events.js:431— FunctionTooLong — bot.events.TouchEventFactory_.create 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×9
Edited copy of a member (14 corresponding lines) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:344— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:344-357 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:360-376 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:497— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:497-510 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1353-1366 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) py/selenium/webdriver/support/event_firing_webdriver.py:148— py/selenium/webdriver/support/event_firing_webdriver.py:148-161 | py/selenium/webdriver/support/event_firing_webdriver.py:215-228 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) dotnet/src/webdriver/Chrome/ChromeDriver.cs:168— dotnet/src/webdriver/Chrome/ChromeDriver.cs:168-181 | dotnet/src/webdriver/Edge/EdgeDriver.cs:138-151 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:255— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:255-270 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:312-325 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:375— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:375-388 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1575-1590 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) java/src/org/openqa/selenium/docker/client/V140Adapter.java:49— java/src/org/openqa/selenium/docker/client/V140Adapter.java:49-62 | java/src/org/openqa/selenium/docker/client/V144Adapter.java:51-73 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) java/src/org/openqa/selenium/remote/RemoteWebDriverBuilder.java:145— java/src/org/openqa/selenium/remote/RemoteWebDriverBuilder.java:145-161 | java/src/org/openqa/selenium/remote/RemoteWebDriverBuilder.java:169-182 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) py/selenium/webdriver/common/_bidi/serialization.py:127— py/selenium/webdriver/common/_bidi/serialization.py:127-155 | py/selenium/webdriver/common/actions/pointer_actions.py:54-67 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×9
Edited copy of a member (16 corresponding lines) py/private/_network_handlers.py:458— py/private/_network_handlers.py:458-474 | py/private/_network_handlers.py:595-610 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:585— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:585-603 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:642-657 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:449— java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:449-466 | java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:563-578 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) java/src/org/openqa/selenium/grid/data/SessionClosedData.java:122— java/src/org/openqa/selenium/grid/data/SessionClosedData.java:122-140 | java/src/org/openqa/selenium/grid/data/SessionEventData.java:202-217 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) java/src/org/openqa/selenium/bidi/log/StackTrace.java:43— java/src/org/openqa/selenium/bidi/log/StackTrace.java:43-58 | java/src/org/openqa/selenium/bidi/script/StackTrace.java:43-59 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1054— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1054-1069 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1098-1113 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) java/src/org/openqa/selenium/grid/distributor/StatusHandler.java:38— java/src/org/openqa/selenium/grid/distributor/StatusHandler.java:38-53 | java/src/org/openqa/selenium/grid/node/StatusHandler.java:39-56 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:753— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:753-769 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:790-805 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) dotnet/src/webdriver/Chrome/ChromeDriverService.cs:67— dotnet/src/webdriver/Chrome/ChromeDriverService.cs:67-82 | dotnet/src/webdriver/Edge/EdgeDriverService.cs:67-82 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×9
Edited copy of a member (11 corresponding lines) py/private/_network_handlers.py:392— py/private/_network_handlers.py:392-404 | py/private/_network_handlers.py:534-544 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2021— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2021-2037 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2233-2243 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) REDACTED:87— REDACTED:87-97 | py/selenium/webdriver/remote/webdriver.py:112-125 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) py/private/_script_handlers.py:174— py/private/_script_handlers.py:174-187 | py/private/_script_handlers.py:191-201 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:720— java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:720-740 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:820-830 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) java/src/org/openqa/selenium/support/FindAll.java:50— java/src/org/openqa/selenium/support/FindAll.java:50-60 | java/src/org/openqa/selenium/support/FindBys.java:49-59 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) java/src/org/openqa/selenium/remote/ErrorCodes.java:387— java/src/org/openqa/selenium/remote/ErrorCodes.java:387-400 | java/src/org/openqa/selenium/remote/ErrorCodes.java:402-412 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) java/src/org/openqa/selenium/grid/jmx/MBean.java:244— java/src/org/openqa/selenium/grid/jmx/MBean.java:244-254 | java/src/org/openqa/selenium/grid/jmx/MBean.java:277-288 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:147— java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:147-157 | java/src/org/openqa/selenium/grid/sessionqueue/config/NewSessionQueueOptions.java:162-172 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×9
Edited copy of a member (9 corresponding lines) dotnet/src/webdriver/Window.cs:49— dotnet/src/webdriver/Window.cs:49-57 | dotnet/src/webdriver/Window.cs:75-83 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) java/src/org/openqa/selenium/bidi/network/BeforeRequestSent.java:48— java/src/org/openqa/selenium/bidi/network/BeforeRequestSent.java:48-56 | java/src/org/openqa/selenium/bidi/network/ResponseDetails.java:44-52 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerSession.java:70— java/src/org/openqa/selenium/grid/node/docker/DockerSession.java:70-78 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSession.java:71-80 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) java/src/org/openqa/selenium/safari/SafariDriverService.java:155— java/src/org/openqa/selenium/safari/SafariDriverService.java:155-163 | java/src/org/openqa/selenium/safari/SafariTechPreviewDriverService.java:156-164 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) dotnet/src/webdriver/WebDriver.cs:369— dotnet/src/webdriver/WebDriver.cs:369-377 | dotnet/src/webdriver/WebDriver.cs:407-415 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:305— java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:305-317 | java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:251-259 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) java/src/org/openqa/selenium/grid/router/httpd/RouterServer.java:215— java/src/org/openqa/selenium/grid/router/httpd/RouterServer.java:215-224 | java/src/org/openqa/selenium/grid/sessionmap/httpd/SessionMapServer.java:108-116 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:504— java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:504-512 | java/src/org/openqa/selenium/grid/sessionqueue/redis/RedisBackedNewSessionQueue.java:550-560 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) java/src/org/openqa/selenium/bidi/Connection.java:193— java/src/org/openqa/selenium/bidi/Connection.java:193-201 | java/src/org/openqa/selenium/devtools/Connection.java:228-236 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) dotnet/src/support/UI/SelectElement.cs:289— dotnet/src/support/UI/SelectElement.cs:289-301 | dotnet/src/support/UI/SelectElement.cs:325-337 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/support/UI/SelectElement.cs:289` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:453— java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:453-465 | java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:566-578 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:453` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) java/src/org/openqa/selenium/events/zeromq/ZeroMqEventBus.java:73— java/src/org/openqa/selenium/events/zeromq/ZeroMqEventBus.java:73-85 | java/src/org/openqa/selenium/events/zeromq/ZeroMqEventBus.java:87-99 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) java/src/org/openqa/selenium/firefox/FirefoxOptions.java:500— java/src/org/openqa/selenium/firefox/FirefoxOptions.java:500-512 | java/src/org/openqa/selenium/firefox/FirefoxOptions.java:637-649 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:85— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:85-97 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:76-88 — before extracting anything, compare `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java` and `java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:74` calls `GridRedisClient` and `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:81` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:259— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:259-271 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:242-254 — before extracting anything, compare `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java` and `java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:259` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:169— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:169-181 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:198-210 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) py/generate_bidi.py:1285— py/generate_bidi.py:1285-1297 | py/generate_bidi.py:1454-1466 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) rust/src/rules.rs:36— rust/src/rules.rs:36-48 | rust/src/skills.rs:28-40 — before extracting anything, compare `rust/src/rules.rs` and `rust/src/skills.rs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×8
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×8
Edited copy of a member (12 corresponding lines) java/src/org/openqa/selenium/firefox/FirefoxOptions.java:516— java/src/org/openqa/selenium/firefox/FirefoxOptions.java:516-529 | java/src/org/openqa/selenium/firefox/FirefoxOptions.java:583-594 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) java/src/org/openqa/selenium/grid/config/ConcatenatingConfig.java:67— java/src/org/openqa/selenium/grid/config/ConcatenatingConfig.java:67-78 | java/src/org/openqa/selenium/grid/config/ConcatenatingConfig.java:81-92 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) rust/src/config.rs:229— rust/src/config.rs:229-240 | rust/src/config.rs:246-257 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:409— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:409-420 | java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:423-434 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) java/src/org/openqa/selenium/bidi/Connection.java:179— java/src/org/openqa/selenium/bidi/Connection.java:179-191 | java/src/org/openqa/selenium/devtools/Connection.java:215-226 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) dotnet/src/webdriver/Chromium/ChromiumDriver.cs:268— dotnet/src/webdriver/Chromium/ChromiumDriver.cs:268-285 | dotnet/src/webdriver/Safari/SafariDriver.cs:217-228 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) java/src/org/openqa/selenium/grid/data/SessionEvent.java:88— java/src/org/openqa/selenium/grid/data/SessionEvent.java:88-99 | java/src/org/openqa/selenium/grid/data/SessionEvent.java:130-141 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) py/selenium/webdriver/webkitgtk/options.py:61— py/selenium/webdriver/webkitgtk/options.py:61-73 | py/selenium/webdriver/wpewebkit/options.py:47-58 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) dotnet/src/support/Events/EventFiringWebDriver.cs:1699— dotnet/src/support/Events/EventFiringWebDriver.cs:1699-1713 | dotnet/src/support/Events/EventFiringWebDriver.cs:1832-1846 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/support/Events/EventFiringWebDriver.cs:1699` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) java/src/org/openqa/selenium/bidi/log/StackTrace.java:44— java/src/org/openqa/selenium/bidi/log/StackTrace.java:44-58 | java/src/org/openqa/selenium/bidi/script/StackTrace.java:45-59 — `java/src/org/openqa/selenium/bidi/log/StackTrace.java` and `java/src/org/openqa/selenium/bidi/script/StackTrace.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 15 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:559— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:559-573 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1269-1283 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:261— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:261-275 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:316-330 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:261` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:259` calls `findElements` and `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:314` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1061— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1061-1075 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1105-1119 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1061` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) dotnet/src/webdriver/BiDi/Script/RealmInfo.cs:84— dotnet/src/webdriver/BiDi/Script/RealmInfo.cs:84-99 | dotnet/src/webdriver/BiDi/Script/RealmInfoEvent.cs:70-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) java/src/org/openqa/selenium/bidi/emulation/SetTimezoneOverrideParameters.java:27— java/src/org/openqa/selenium/bidi/emulation/SetTimezoneOverrideParameters.java:27-41 | java/src/org/openqa/selenium/bidi/emulation/SetUserAgentOverrideParameters.java:26-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) scripts/pinned_browsers.py:35— scripts/pinned_browsers.py:35-49 | scripts/update_cdp.py:29-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×7
Edited copy of a member (17 corresponding lines) java/src/org/openqa/selenium/bidi/Connection.java:161— java/src/org/openqa/selenium/bidi/Connection.java:161-177 | java/src/org/openqa/selenium/devtools/Connection.java:197-213 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) dotnet/src/webdriver/Interactions/Actions.cs:213— dotnet/src/webdriver/Interactions/Actions.cs:213-230 | dotnet/src/webdriver/Interactions/Actions.cs:257-273 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) java/src/org/openqa/selenium/json/Input.java:155— java/src/org/openqa/selenium/json/Input.java:155-171 | java/src/org/openqa/selenium/json/Input.java:209-225 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) java/src/org/openqa/selenium/json/JsonOutput.java:335— java/src/org/openqa/selenium/json/JsonOutput.java:335-351 | java/src/org/openqa/selenium/json/JsonOutput.java:372-388 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:151— java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:151-167 | java/src/org/openqa/selenium/grid/sessionqueue/redis/RedisBackedNewSessionQueue.java:166-191 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSession.java:107— java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSession.java:107-127 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1314-1330 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) REDACTED:293— REDACTED:293-309 | REDACTED:317-333 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×7
Edited copy of a member (13 corresponding lines) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:518— java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:518-530 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:532-544 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) java/src/org/openqa/selenium/grid/sessionmap/AddToSessionMap.java:51— java/src/org/openqa/selenium/grid/sessionmap/AddToSessionMap.java:51-66 | java/src/org/openqa/selenium/grid/sessionmap/GetFromSessionMap.java:49-61 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:566— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:566-579 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:481-493 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) py/generate_bidi_protocol.py:686— py/generate_bidi_protocol.py:686-698 | py/generate_bidi_protocol.py:704-717 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) rust/src/metadata.rs:141— rust/src/metadata.rs:141-153 | rust/src/metadata.rs:159-171 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) java/src/org/openqa/selenium/edge/EdgeDriverService.java:154— java/src/org/openqa/selenium/edge/EdgeDriverService.java:154-172 | java/src/org/openqa/selenium/chrome/ChromeDriverService.java:159-171 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) dotnet/src/webdriver/Remote/DesiredCapabilities.cs:189— dotnet/src/webdriver/Remote/DesiredCapabilities.cs:189-201 | dotnet/src/webdriver/Remote/ReadOnlyDesiredCapabilities.cs:149-161 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (11 lines × 2) java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:904— java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:904-914 | java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:1290-1300 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:900` calls `equals`, `addExtendedType` and `java/src/org/openqa/selenium/devtools/CdpClientGenerator.java:1288` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) java/src/org/openqa/selenium/grid/config/MapConfig.java:80— java/src/org/openqa/selenium/grid/config/MapConfig.java:80-90 | java/src/org/openqa/selenium/grid/config/TomlConfig.java:111-121 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/config/MapConfig.java:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:250— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:250-260 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:465-475 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:250` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:673— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:673-683 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:581-591 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) dotnet/src/webdriver/Chromium/ChromiumDriver.cs:488— dotnet/src/webdriver/Chromium/ChromiumDriver.cs:488-498 | REDACTED:637-647 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) py/generate_bidi.py:353— py/generate_bidi.py:353-363 | py/generate_bidi.py:373-385 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) REDACTED:86— REDACTED:86-96 | REDACTED:126-136 — 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.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×6
Edited copy of a member (20 corresponding lines) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:77— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:77-97 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:69-88 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) java/src/org/openqa/selenium/grid/node/config/DriverServiceSessionFactory.java:340— java/src/org/openqa/selenium/grid/node/config/DriverServiceSessionFactory.java:340-364 | java/src/org/openqa/selenium/remote/service/DriverFinder.java:184-203 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) dotnet/src/webdriver/ShadowRoot.cs:86— dotnet/src/webdriver/ShadowRoot.cs:86-105 | dotnet/src/webdriver/ShadowRoot.cs:116-135 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) py/private/_network_handlers.py:367— py/private/_network_handlers.py:367-389 | py/private/_network_handlers.py:512-531 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) dotnet/src/webdriver/Chromium/ChromiumOptions.cs:598— dotnet/src/webdriver/Chromium/ChromiumOptions.cs:598-620 | dotnet/src/webdriver/Firefox/FirefoxOptions.cs:328-347 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) java/src/org/openqa/selenium/bidi/BiDiProvider.java:57— java/src/org/openqa/selenium/bidi/BiDiProvider.java:57-81 | java/src/org/openqa/selenium/devtools/DevToolsProvider.java:51-70 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×6
Edited copy of a member (15 corresponding lines) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2096— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2096-2116 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2119-2133 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:530— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:530-544 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:588-603 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) dotnet/src/webdriver/WebElement.cs:148— dotnet/src/webdriver/WebElement.cs:148-162 | dotnet/src/webdriver/WebElement.cs:172-186 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) dotnet/src/webdriver/BiDi/EventDispatcher.cs:65— dotnet/src/webdriver/BiDi/EventDispatcher.cs:65-80 | dotnet/src/webdriver/BiDi/EventDispatcher.cs:98-112 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) dotnet/src/webdriver/Interactions/PointerInputDevice.cs:433— dotnet/src/webdriver/Interactions/PointerInputDevice.cs:433-447 | dotnet/src/webdriver/Interactions/PointerInputDevice.cs:468-483 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) scripts/pinned_browsers.py:35— scripts/pinned_browsers.py:35-49 | scripts/update_cdp.py:20-43 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×6
Edited copy of a member (5 corresponding lines) dotnet/src/webdriver/BiDi/Network/NetworkModule.cs:70— dotnet/src/webdriver/BiDi/Network/NetworkModule.cs:70-74 | dotnet/src/webdriver/BiDi/Network/NetworkModule.cs:107-111 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) dotnet/src/webdriver/BiDi/Network/NetworkModule.cs:77— dotnet/src/webdriver/BiDi/Network/NetworkModule.cs:77-81 | dotnet/src/webdriver/BiDi/Network/NetworkModule.cs:107-111 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) java/src/org/openqa/selenium/grid/data/Slot.java:40— java/src/org/openqa/selenium/grid/data/Slot.java:40-45 | java/src/org/openqa/selenium/grid/graphql/Slot.java:39-43 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextScriptModule.cs:48— dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextScriptModule.cs:48-52 | dotnet/src/webdriver/BiDi/Script/ScriptModule.cs:36-40 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextScriptModule.cs:65— dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextScriptModule.cs:65-69 | dotnet/src/webdriver/BiDi/Script/ScriptModule.cs:50-54 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) java/src/org/openqa/selenium/grid/distributor/GetDistributorStatus.java:38— java/src/org/openqa/selenium/grid/distributor/GetDistributorStatus.java:38-42 | java/src/org/openqa/selenium/grid/node/GetNodeSession.java:42-46 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (7 lines × 3) dotnet/src/webdriver/Interactions/Actions.cs:219— dotnet/src/webdriver/Interactions/Actions.cs:219-225 | dotnet/src/webdriver/Interactions/Actions.cs:263-269 | dotnet/src/webdriver/Interactions/Actions.cs:300-306 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) dotnet/src/webdriver/BiDi/Input/SourceActions.cs:80— dotnet/src/webdriver/BiDi/Input/SourceActions.cs:80-86 | dotnet/src/webdriver/BiDi/Input/SourceActions.cs:97-103 | dotnet/src/webdriver/BiDi/Input/SourceActions.cs:133-145 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:127— java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:127-133 | java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:144-150 | java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:183-189 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:127` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) dotnet/src/webdriver/DevTools/v155/V155Network.cs:42— dotnet/src/webdriver/DevTools/v155/V155Network.cs:42-48 | dotnet/src/webdriver/DevTools/v156/V156Network.cs:42-48 | dotnet/src/webdriver/DevTools/v157/V157Network.cs:42-48 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155Network.cs` and `dotnet/src/webdriver/DevTools/v156/V156Network.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Log.java:78— java/src/org/openqa/selenium/devtools/v155/v155Log.java:78-84 | java/src/org/openqa/selenium/devtools/v156/v156Log.java:78-84 | java/src/org/openqa/selenium/devtools/v157/v157Log.java:78-84 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Log.java` and `java/src/org/openqa/selenium/devtools/v156/v156Log.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: `Timestamp` names `org.openqa.selenium.devtools.v155.runtime.model.Timestamp` in one and `org.openqa.selenium.devtools.v156.runtime.model.Timestamp` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 3) java/src/org/openqa/selenium/firefox/GeckoDriverInfo.java:83— java/src/org/openqa/selenium/firefox/GeckoDriverInfo.java:83-89 | java/src/org/openqa/selenium/ie/InternetExplorerDriverInfo.java:84-92 | java/src/org/openqa/selenium/safari/SafariDriverInfo.java:87-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) java/src/org/openqa/selenium/grid/distributor/remote/RemoteDistributor.java:99— java/src/org/openqa/selenium/grid/distributor/remote/RemoteDistributor.java:99-106 | java/src/org/openqa/selenium/grid/node/remote/RemoteNode.java:224-232 | java/src/org/openqa/selenium/grid/node/remote/RemoteNode.java:268-275 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) java/src/org/openqa/selenium/grid/node/local/LocalNode.java:273— java/src/org/openqa/selenium/grid/node/local/LocalNode.java:273-280 | java/src/org/openqa/selenium/grid/node/local/LocalNode.java:283-290 | java/src/org/openqa/selenium/grid/node/local/LocalNode.java:293-300 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/local/LocalNode.java:273` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:41— dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:41-48 | dotnet/src/webdriver/DevTools/v156/V156JavaScript.cs:41-48 | dotnet/src/webdriver/DevTools/v157/V157JavaScript.cs:41-48 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs` and `dotnet/src/webdriver/DevTools/v156/V156JavaScript.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) dotnet/src/webdriver/DevTools/v155/V155Network.cs:303— dotnet/src/webdriver/DevTools/v155/V155Network.cs:303-310 | dotnet/src/webdriver/DevTools/v156/V156Network.cs:303-310 | dotnet/src/webdriver/DevTools/v157/V157Network.cs:303-310 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155Network.cs` and `dotnet/src/webdriver/DevTools/v156/V156Network.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Network.java:103— java/src/org/openqa/selenium/devtools/v155/v155Network.java:103-110 | java/src/org/openqa/selenium/devtools/v156/v156Network.java:103-110 | java/src/org/openqa/selenium/devtools/v157/v157Network.java:103-110 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Network.java` and `java/src/org/openqa/selenium/devtools/v156/v156Network.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/devtools/v155/v155Network.java:103` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `AuthChallengeResponse` names `org.openqa.selenium.devtools.v155.fetch.model.AuthChallengeResponse` in one and `org.openqa.selenium.devtools.v156.fetch.model.AuthChallengeResponse` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Domains.java:37— java/src/org/openqa/selenium/devtools/v155/v155Domains.java:37-44 | java/src/org/openqa/selenium/devtools/v156/v156Domains.java:37-44 | java/src/org/openqa/selenium/devtools/v157/v157Domains.java:37-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (14 lines × 2) java/src/org/openqa/selenium/grid/data/DefaultSlotMatcher.java:113— java/src/org/openqa/selenium/grid/data/DefaultSlotMatcher.java:113-126 | java/src/org/openqa/selenium/grid/data/DefaultSlotMatcher.java:170-183 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/data/DefaultSlotMatcher.java:113` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) java/src/org/openqa/selenium/grid/distributor/httpd/DistributorServer.java:124— java/src/org/openqa/selenium/grid/distributor/httpd/DistributorServer.java:124-137 | java/src/org/openqa/selenium/grid/sessionqueue/httpd/NewSessionQueueServer.java:134-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/distributor/httpd/DistributorServer.java:124` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) java/src/org/openqa/selenium/json/JsonOutput.java:338— java/src/org/openqa/selenium/json/JsonOutput.java:338-351 | java/src/org/openqa/selenium/json/JsonOutput.java:375-388 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/json/JsonOutput.java:338` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (14 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:121— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:121-134 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:136-149 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:152` calls `reconstructLocalNodesFromRedis` and `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:137` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) rust/src/grid.rs:170— rust/src/grid.rs:170-183 | rust/src/iexplorer.rs:171-184 — before extracting anything, compare `rust/src/grid.rs` and `rust/src/iexplorer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rust/src/grid.rs:170` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) java/src/org/openqa/selenium/bidi/module/Script.java:356— java/src/org/openqa/selenium/bidi/module/Script.java:356-367 | java/src/org/openqa/selenium/bidi/module/Script.java:385-396 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/bidi/module/Script.java:369` calls `ifPresent`, `put` and `java/src/org/openqa/selenium/bidi/module/Script.java:398` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) java/src/org/openqa/selenium/grid/graphql/Types.java:42— java/src/org/openqa/selenium/grid/graphql/Types.java:42-53 | java/src/org/openqa/selenium/grid/graphql/Types.java:97-108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:222— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:222-233 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:223-234 — before extracting anything, compare `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java` and `java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:222` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:270— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:270-281 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:319-330 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/BiDiGenerator.java:270` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:390— java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:390-401 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:128-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2 locations) javascript/grid-ui/src/components/QueuedSessions/QueuedSessions.tsx:52— javascript/grid-ui/src/components/QueuedSessions/QueuedSessions.tsx:52 · javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx:326 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (14 lines × 2 locations) javascript/selenium-webdriver/bidi/storage.js:133— javascript/selenium-webdriver/bidi/storage.js:133 · javascript/selenium-webdriver/bidi/storage.js:175 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 2 locations) javascript/selenium-webdriver/lib/script.js:89— javascript/selenium-webdriver/lib/script.js:89 · REDACTED:1575 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (14 lines × 2 locations) javascript/selenium-webdriver/lib/select.js:183— javascript/selenium-webdriver/lib/select.js:183 · javascript/selenium-webdriver/lib/select.js:399 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2 locations) javascript/selenium-webdriver/normalize_bidi_ast_test.mjs:119— javascript/selenium-webdriver/normalize_bidi_ast_test.mjs:119 · javascript/selenium-webdriver/normalize_bidi_ast_test.mjs:177 — 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.
SeleniumManager::discover_local_browser (cognitive 56) rust/src/lib.rs:531— SeleniumManager::discover_local_browser has cognitive complexity 56 (threshold 15). Drivers by points: if/else 16 (48 pts), boolean chains 6, match/switch 1 (2 pts) (nesting depth added 33). 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.
SeleniumManager::download_browser (cognitive 30) rust/src/lib.rs:240— SeleniumManager::download_browser has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 6, match/switch 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.
SeleniumManager::setup (cognitive 27) rust/src/lib.rs:875— SeleniumManager::setup has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 7, match/switch 3 (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.
SeleniumManager::detect_browser_path (cognitive 20) rust/src/lib.rs:432— SeleniumManager::detect_browser_path has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, 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.
selenium_manager::main (cognitive 40) rust/src/main.rs:184— selenium_manager::main has cognitive complexity 40 (threshold 15). Drivers by points: if/else 25 (35 pts), boolean chains 5 (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.
selenium_manager::files::uncompress (cognitive 25) rust/src/files.rs:125— selenium_manager::files::uncompress has cognitive complexity 25 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 2, match/switch 1 (nesting depth added 4). 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.
selenium_manager::files::unzip (cognitive 17) rust/src/files.rs:478— selenium_manager::files::unzip has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
selenium_manager::files::copy_folder_content (cognitive 16) rust/src/files.rs:567— selenium_manager::files::copy_folder_content has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) java/src/org/openqa/selenium/ImmutableCapabilities.java:49— java/src/org/openqa/selenium/ImmutableCapabilities.java:49-62 | java/src/org/openqa/selenium/ImmutableCapabilities.java:64-80 | java/src/org/openqa/selenium/ImmutableCapabilities.java:83-102 | java/src/org/openqa/selenium/ImmutableCapabilities.java:114-136 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) java/src/org/openqa/selenium/bidi/module/Script.java:253— java/src/org/openqa/selenium/bidi/module/Script.java:253-266 | java/src/org/openqa/selenium/bidi/module/Script.java:268-282 | java/src/org/openqa/selenium/bidi/module/Script.java:284-299 | java/src/org/openqa/selenium/bidi/module/Script.java:302-317 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:128— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:128-185 | java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:188-287 | java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:290-326 | java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:328-360 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:290— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:290-326 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:149-199 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:202-256 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:259-286 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×4
Edited copy of a member (26 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:223— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:223-248 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:268-302 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) java/src/org/openqa/selenium/docker/client/V140Adapter.java:65— java/src/org/openqa/selenium/docker/client/V140Adapter.java:65-90 | java/src/org/openqa/selenium/docker/client/V144Adapter.java:76-102 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) dotnet/src/webdriver/Interactions/PointerInputDevice.cs:547— dotnet/src/webdriver/Interactions/PointerInputDevice.cs:547-577 | dotnet/src/webdriver/Interactions/WheelInputDevice.cs:176-201 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) dotnet/src/webdriver/WebDriver.cs:806— dotnet/src/webdriver/WebDriver.cs:806-836 | dotnet/src/webdriver/WebDriver.cs:843-868 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×4
Edited copy of a member (24 corresponding lines) java/src/org/openqa/selenium/remote/NewSessionPayload.java:315— java/src/org/openqa/selenium/remote/NewSessionPayload.java:315-338 | java/src/org/openqa/selenium/remote/NewSessionPayload.java:340-363 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:126— java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:126-149 | java/src/org/openqa/selenium/grid/sessionqueue/redis/RedisBackedNewSessionQueue.java:141-164 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:450— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:450-475 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:492-515 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) py/selenium/webdriver/remote/webdriver.py:988— py/selenium/webdriver/remote/webdriver.py:988-1011 | REDACTED:535-566 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×4
Edited copy of a member (23 corresponding lines) java/src/org/openqa/selenium/grid/distributor/selector/DefaultSlotSelector.java:43— java/src/org/openqa/selenium/grid/distributor/selector/DefaultSlotSelector.java:43-71 | java/src/org/openqa/selenium/grid/distributor/selector/GreedySlotSelector.java:49-71 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) dotnet/src/webdriver/Interactions/PointerInputDevice.cs:522— dotnet/src/webdriver/Interactions/PointerInputDevice.cs:522-544 | dotnet/src/webdriver/Interactions/WheelInputDevice.cs:150-173 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:346— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:346-368 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:172-194 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) REDACTED:569— REDACTED:569-596 | py/selenium/webdriver/remote/webdriver.py:1014-1036 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×4
Edited copies of one member (3 members, 11+ corresponding lines) java/src/org/openqa/selenium/docker/Version.java:41— java/src/org/openqa/selenium/docker/Version.java:41-51 | java/src/org/openqa/selenium/docker/Version.java:53-67 | java/src/org/openqa/selenium/docker/Version.java:69-83 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:252— java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:252-267 | java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:269-279 | java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:281-292 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) java/src/org/openqa/selenium/bidi/network/BeforeRequestSent.java:36— java/src/org/openqa/selenium/bidi/network/BeforeRequestSent.java:36-46 | java/src/org/openqa/selenium/bidi/network/FetchError.java:32-42 | java/src/org/openqa/selenium/bidi/network/ResponseDetails.java:32-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) java/src/org/openqa/selenium/grid/commands/DefaultHubConfig.java:25— java/src/org/openqa/selenium/grid/commands/DefaultHubConfig.java:25-37 | java/src/org/openqa/selenium/grid/distributor/httpd/DefaultDistributorConfig.java:25-35 | java/src/org/openqa/selenium/grid/sessionmap/httpd/DefaultSessionMapConfig.java:25-36 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×4
Edited copy of a member (6 corresponding lines) java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:78— java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:78-84 | java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:70-75 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) java/src/org/openqa/selenium/bidi/Command.java:69— java/src/org/openqa/selenium/bidi/Command.java:69-74 | java/src/org/openqa/selenium/devtools/Command.java:50-56 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) dotnet/src/webdriver/Chromium/ChromiumDriver.cs:366— dotnet/src/webdriver/Chromium/ChromiumDriver.cs:366-371 | REDACTED:624-629 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) java/src/org/openqa/selenium/devtools/Message.java:33— java/src/org/openqa/selenium/devtools/Message.java:33-38 | java/src/org/openqa/selenium/events/Event.java:67-73 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (23 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:456— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:456-478 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:525-547 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:485` calls `getModel` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:549` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23 lines × 2) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:304— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:304-326 | java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:338-360 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:304` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) py/selenium/webdriver/webkitgtk/service.py:48— py/selenium/webdriver/webkitgtk/service.py:48-70 | py/selenium/webdriver/wpewebkit/service.py:48-70 — `py/selenium/webdriver/webkitgtk/service.py` and `py/selenium/webdriver/wpewebkit/service.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 23 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (23 lines × 2) rb/support/rbs_collection_update.rb:23— rb/support/rbs_collection_update.rb:23-45 | rb/support/steep_check.rb:25-47 — before extracting anything, compare `rb/support/rbs_collection_update.rb` and `rb/support/steep_check.rb` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rb/support/rbs_collection_update.rb:23` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 3) dotnet/src/webdriver/DevTools/v155/V155Target.cs:124— dotnet/src/webdriver/DevTools/v155/V155Target.cs:124-141 | dotnet/src/webdriver/DevTools/v156/V156Target.cs:124-141 | dotnet/src/webdriver/DevTools/v157/V157Target.cs:124-141 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155Target.cs` and `dotnet/src/webdriver/DevTools/v156/V156Target.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Network.java:193— java/src/org/openqa/selenium/devtools/v155/v155Network.java:193-210 | java/src/org/openqa/selenium/devtools/v156/v156Network.java:193-210 | java/src/org/openqa/selenium/devtools/v157/v157Network.java:193-210 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Network.java` and `java/src/org/openqa/selenium/devtools/v156/v156Network.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Fetch` names `org.openqa.selenium.devtools.v155.fetch.Fetch` in one and `org.openqa.selenium.devtools.v156.fetch.Fetch` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (18 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Network.java:214— java/src/org/openqa/selenium/devtools/v155/v155Network.java:214-231 | java/src/org/openqa/selenium/devtools/v156/v156Network.java:214-231 | java/src/org/openqa/selenium/devtools/v157/v157Network.java:214-231 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Network.java` and `java/src/org/openqa/selenium/devtools/v156/v156Network.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Fetch` names `org.openqa.selenium.devtools.v155.fetch.Fetch` in one and `org.openqa.selenium.devtools.v156.fetch.Fetch` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (18 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Log.java:59— java/src/org/openqa/selenium/devtools/v155/v155Log.java:59-76 | java/src/org/openqa/selenium/devtools/v156/v156Log.java:59-76 | java/src/org/openqa/selenium/devtools/v157/v157Log.java:59-76 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Log.java` and `java/src/org/openqa/selenium/devtools/v156/v156Log.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: `LogEntry` names `org.openqa.selenium.devtools.v155.log.model.LogEntry` in one and `org.openqa.selenium.devtools.v156.log.model.LogEntry` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (18 lines × 2) java/src/org/openqa/selenium/grid/commands/Standalone.java:266— java/src/org/openqa/selenium/grid/commands/Standalone.java:266-283 | java/src/org/openqa/selenium/grid/node/httpd/NodeServer.java:155-172 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/commands/Standalone.java:266` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:158— java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:158-175 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:184-201 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:158` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:255— java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:255-272 | java/src/org/openqa/selenium/grid/sessionqueue/redis/RedisBackedNewSessionQueue.java:268-285 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:255` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) py/selenium/webdriver/webkitgtk/webdriver.py:32— py/selenium/webdriver/webkitgtk/webdriver.py:32-49 | py/selenium/webdriver/wpewebkit/webdriver.py:32-49 — `py/selenium/webdriver/webkitgtk/webdriver.py` and `py/selenium/webdriver/wpewebkit/webdriver.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 18 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Note first that the copies are not typed on the same thing: `Options` names `selenium.webdriver.webkitgtk.options` in one and `selenium.webdriver.wpewebkit.options` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 2) java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java:48— java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java:48-64 | java/src/org/openqa/selenium/bidi/browsingcontext/NavigationInfo.java:51-67 — before extracting anything, compare `java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java` and `java/src/org/openqa/selenium/bidi/browsingcontext/NavigationInfo.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:272— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:272-288 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:334-350 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java:354— java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java:354-370 | java/src/org/openqa/selenium/grid/node/local/LocalNode.java:1111-1127 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java:354` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) java/src/org/openqa/selenium/bidi/Event.java:33— java/src/org/openqa/selenium/bidi/Event.java:33-49 | java/src/org/openqa/selenium/devtools/Event.java:29-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `mapper` to `Function<Map<String, Object>, X>` in one and `Function<JsonInput, X>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (14 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Log.java:44— java/src/org/openqa/selenium/devtools/v155/v155Log.java:44-57 | java/src/org/openqa/selenium/devtools/v156/v156Log.java:44-57 | java/src/org/openqa/selenium/devtools/v157/v157Log.java:44-57 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Log.java` and `java/src/org/openqa/selenium/devtools/v156/v156Log.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Log` names `org.openqa.selenium.devtools.v155.log.Log` in one and `org.openqa.selenium.devtools.v156.log.Log` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (14 lines × 3) java/src/org/openqa/selenium/grid/TemplateGridCommand.java:63— java/src/org/openqa/selenium/grid/TemplateGridCommand.java:63-76 | java/src/org/openqa/selenium/grid/commands/CompletionCommand.java:71-84 | java/src/org/openqa/selenium/grid/commands/InfoCommand.java:71-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/TemplateGridCommand.java:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:279— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:279-292 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:328-341 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:479-492 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/BiDiGenerator.java:279` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) py/selenium/webdriver/common/actions/pointer_actions.py:93— py/selenium/webdriver/common/actions/pointer_actions.py:93-106 | py/selenium/webdriver/common/actions/pointer_actions.py:124-137 | py/selenium/webdriver/common/actions/pointer_actions.py:155-168 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `py/selenium/webdriver/common/actions/pointer_actions.py:93` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 4) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:542— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:542-549 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:694-701 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1767-1774 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1920-1927 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 4) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:173— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:173-180 | java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:276-283 | java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:315-322 | java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:349-356 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:173` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:291— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:291-298 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:150-157 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:203-210 | java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java:260-267 — before extracting anything, compare `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java` and `java/src/org/openqa/selenium/grid/sessionmap/redis/RedisBackedSessionMap.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:291` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:735— java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:735-742 | java/src/org/openqa/selenium/grid/node/docker/DockerOptions.java:341-348 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:546-553 | java/src/org/openqa/selenium/grid/node/relay/RelayOptions.java:200-207 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
SeleniumManager::discover_local_browser (cyclomatic 20) rust/src/lib.rs:531— SeleniumManager::discover_local_browser 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.
SeleniumManager::setup (cyclomatic 20) rust/src/lib.rs:875— SeleniumManager::setup 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.
SeleniumManager::download_browser (cyclomatic 19) rust/src/lib.rs:240— SeleniumManager::download_browser 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.
shown.isShownElement::isShownInternal (cyclomatic 19) javascript/atoms/typescript/core/shown.ts:86— shown.isShownElement::isShownInternal has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: 2 other methods here (shown.isShownElement::isShownInternal::positiveSize, shown.isShownElement::displayed) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
shown.isShownElement::isShownInternal::positiveSize (cyclomatic 18) javascript/atoms/typescript/core/shown.ts:127— shown.isShownElement::isShownInternal::positiveSize has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (shown.isShownElement::isShownInternal, shown.isShownElement::displayed) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
shown.isShownElement::displayed (cyclomatic 16) javascript/atoms/typescript/core/shown.ts:191— shown.isShownElement::displayed 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. This shape REPEATS in the file: 2 other methods here (shown.isShownElement::isShownInternal, shown.isShownElement::isShownInternal::positiveSize) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
shown.isShownElement::isShownInternal::positiveSize (cognitive 21) javascript/atoms/typescript/core/shown.ts:127— shown.isShownElement::isShownInternal::positiveSize has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 8, 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. This shape REPEATS in the file: 2 other methods here (shown.isShownElement::isShownInternal, shown.isShownElement::displayed) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
shown.isShownElement::isShownInternal (cognitive 16) javascript/atoms/typescript/core/shown.ts:86— shown.isShownElement::isShownInternal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, boolean chains 6. 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. This shape REPEATS in the file: 2 other methods here (shown.isShownElement::isShownInternal::positiveSize, shown.isShownElement::displayed) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
shown.isShownElement::displayed (cognitive 16) javascript/atoms/typescript/core/shown.ts:191— shown.isShownElement::displayed has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 7 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: 2 other methods here (shown.isShownElement::isShownInternal, shown.isShownElement::isShownInternal::positiveSize) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Change-coupling hub: Broker.cs → BrowserModule.cs, BrowsingContextModule.cs, InputModule.cs, LogModule.cs, NetworkModule.cs, ScriptModule.cs, SessionModule.cs, StorageModule.cs, WebExtensionModule.cs dotnet/src/webdriver/BiDi/Broker.cs— `dotnet/src/webdriver/BiDi/Broker.cs` changes together with 9 other files — `dotnet/src/webdriver/BiDi/Browser/BrowserModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextModule.cs`, `dotnet/src/webdriver/BiDi/Input/InputModule.cs`, `dotnet/src/webdriver/BiDi/Log/LogModule.cs`, `dotnet/src/webdriver/BiDi/Network/NetworkModule.cs`, `dotnet/src/webdriver/BiDi/Script/ScriptModule.cs`, `dotnet/src/webdriver/BiDi/Session/SessionModule.cs`, `dotnet/src/webdriver/BiDi/Storage/StorageModule.cs`, `dotnet/src/webdriver/BiDi/WebExtension/WebExtensionModule.cs` — none of which declares a dependency on it: one file is the hub of 9 separate couplings, not 9 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 9.
Change-coupling hub: SafariDriverInfo.java → ChromeDriverInfo.java, EdgeDriverInfo.java, GeckoDriverInfo.java, SafariTechPreviewDriverInfo.java java/src/org/openqa/selenium/safari/SafariDriverInfo.java— `java/src/org/openqa/selenium/safari/SafariDriverInfo.java` changes together with 4 other files — `java/src/org/openqa/selenium/chrome/ChromeDriverInfo.java`, `java/src/org/openqa/selenium/edge/EdgeDriverInfo.java`, `java/src/org/openqa/selenium/firefox/GeckoDriverInfo.java`, `java/src/org/openqa/selenium/safari/SafariTechPreviewDriverInfo.java` — 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: DistributorFlags.java → Hub.java, Standalone.java, LocalDistributor.java java/src/org/openqa/selenium/grid/distributor/config/DistributorFlags.java— `java/src/org/openqa/selenium/grid/distributor/config/DistributorFlags.java` changes together with 3 other files — `java/src/org/openqa/selenium/grid/commands/Hub.java`, `java/src/org/openqa/selenium/grid/commands/Standalone.java`, `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×3
Edited copy of a member (31 corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerOptions.java:83— java/src/org/openqa/selenium/grid/node/docker/DockerOptions.java:83-113 | java/src/org/openqa/selenium/grid/node/relay/RelayOptions.java:57-88 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) dotnet/src/webdriver/IE/InternetExplorerDriver.cs:161— dotnet/src/webdriver/IE/InternetExplorerDriver.cs:161-191 | dotnet/src/webdriver/Safari/SafariDriver.cs:166-196 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) dotnet/src/webdriver/Chromium/ChromiumDriverService.cs:194— dotnet/src/webdriver/Chromium/ChromiumDriverService.cs:194-224 | dotnet/src/webdriver/Firefox/FirefoxDriverService.cs:374-405 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×3
Edited copy of a member (36 corresponding lines) java/src/org/openqa/selenium/remote/ElementLocation.java:51— java/src/org/openqa/selenium/remote/ElementLocation.java:51-89 | java/src/org/openqa/selenium/remote/ElementLocation.java:95-130 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) py/generate_bidi.py:1306— py/generate_bidi.py:1306-1349 | py/generate_bidi.py:1352-1387 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:481— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:481-517 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:295-330 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×3
Edited copy of a member (28 corresponding lines) rust/src/edge.rs:311— rust/src/edge.rs:311-338 | rust/src/firefox.rs:320-354 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:748— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:748-777 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:785-812 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) dotnet/src/webdriver/Remote/DesiredCapabilities.cs:261— dotnet/src/webdriver/Remote/DesiredCapabilities.cs:261-288 | dotnet/src/webdriver/Remote/ReadOnlyDesiredCapabilities.cs:200-227 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×3
Edited copies of one member (3 members, 4+ corresponding lines) java/src/org/openqa/selenium/devtools/v155/v155Network.java:59— java/src/org/openqa/selenium/devtools/v155/v155Network.java:59-62 | java/src/org/openqa/selenium/devtools/v156/v156Network.java:59-62 | java/src/org/openqa/selenium/devtools/v157/v157Network.java:59-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:119— java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:119-123 | java/src/org/openqa/selenium/bidi/module/Network.java:142-147 | java/src/org/openqa/selenium/bidi/module/Script.java:235-238 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) java/src/org/openqa/selenium/grid/commands/Hub.java:242— java/src/org/openqa/selenium/grid/commands/Hub.java:242-245 | java/src/org/openqa/selenium/grid/commands/Standalone.java:252-255 | java/src/org/openqa/selenium/grid/router/httpd/RouterServer.java:247-250 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×3
Edited copy of a member (3 corresponding lines) dotnet/src/webdriver/Internal/Logging/FileLogHandler.cs:77— dotnet/src/webdriver/Internal/Logging/FileLogHandler.cs:77-82 | dotnet/src/webdriver/Internal/Logging/TextWriterHandler.cs:35-37 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) dotnet/src/webdriver/Remote/DesiredCapabilities.cs:241— dotnet/src/webdriver/Remote/DesiredCapabilities.cs:241-243 | dotnet/src/webdriver/Remote/ReadOnlyDesiredCapabilities.cs:190-192 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) py/generate_bidi_protocol.py:82— py/generate_bidi_protocol.py:82-84 | py/selenium/webdriver/common/_bidi/serialization.py:175-178 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×3
Edited copy of a member (4 corresponding lines) rb/lib/selenium/webdriver/chromium/options.rb:219— rb/lib/selenium/webdriver/chromium/options.rb:219-222 | rb/lib/selenium/webdriver/firefox/options.rb:163-166 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) java/src/org/openqa/selenium/grid/security/SecretOptions.java:74— java/src/org/openqa/selenium/grid/security/SecretOptions.java:74-77 | java/src/org/openqa/selenium/grid/server/BaseServerOptions.java:136-139 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) java/src/org/openqa/selenium/ie/InternetExplorerOptions.java:99— java/src/org/openqa/selenium/ie/InternetExplorerOptions.java:99-102 | java/src/org/openqa/selenium/safari/SafariOptions.java:60-64 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (20 lines × 2) dotnet/src/webdriver/Interactions/PointerInputDevice.cs:523— dotnet/src/webdriver/Interactions/PointerInputDevice.cs:523-542 | dotnet/src/webdriver/Interactions/WheelInputDevice.cs:151-170 — before extracting anything, compare `dotnet/src/webdriver/Interactions/PointerInputDevice.cs` and `dotnet/src/webdriver/Interactions/WheelInputDevice.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:438— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:438-457 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:254-273 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java` and `java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 2) java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:379— java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:379-398 | java/src/org/openqa/selenium/grid/sessionqueue/redis/RedisBackedNewSessionQueue.java:403-422 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/sessionqueue/local/LocalNewSessionQueue.java:379` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 3) dotnet/src/webdriver/DevTools/v155/V155Network.cs:268— dotnet/src/webdriver/DevTools/v155/V155Network.cs:268-286 | dotnet/src/webdriver/DevTools/v156/V156Network.cs:268-286 | dotnet/src/webdriver/DevTools/v157/V157Network.cs:268-286 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155Network.cs` and `dotnet/src/webdriver/DevTools/v156/V156Network.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 3) java/src/org/openqa/selenium/grid/commands/EventBusCommand.java:172— java/src/org/openqa/selenium/grid/commands/EventBusCommand.java:172-190 | java/src/org/openqa/selenium/grid/sessionmap/httpd/SessionMapServer.java:123-141 | java/src/org/openqa/selenium/grid/sessionqueue/httpd/NewSessionQueueServer.java:153-171 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/commands/EventBusCommand.java:172` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/grid/commands/EventBusCommand.java:170` calls `nonNull` and `java/src/org/openqa/selenium/grid/sessionmap/httpd/SessionMapServer.java:121` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 3) java/src/org/openqa/selenium/bidi/emulation/SetGeolocationOverrideParameters.java:28— java/src/org/openqa/selenium/bidi/emulation/SetGeolocationOverrideParameters.java:28-51 | java/src/org/openqa/selenium/bidi/emulation/SetScreenOrientationOverrideParameters.java:27-45 | java/src/org/openqa/selenium/bidi/emulation/SetScreenSettingsOverrideParameters.java:27-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) dotnet/src/webdriver/Interactions/PointerInputDevice.cs:559— dotnet/src/webdriver/Interactions/PointerInputDevice.cs:559-574 | dotnet/src/webdriver/Interactions/WheelInputDevice.cs:180-195 — before extracting anything, compare `dotnet/src/webdriver/Interactions/PointerInputDevice.cs` and `dotnet/src/webdriver/Interactions/WheelInputDevice.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java:376— java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java:376-391 | java/src/org/openqa/selenium/grid/node/local/LocalNode.java:1133-1148 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java:376` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) java/src/org/openqa/selenium/json/UriCoercer.java:35— java/src/org/openqa/selenium/json/UriCoercer.java:35-50 | java/src/org/openqa/selenium/json/UrlCoercer.java:35-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/json/UriCoercer.java:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) java/src/org/openqa/selenium/ImmutableCapabilities.java:66— java/src/org/openqa/selenium/ImmutableCapabilities.java:66-76 | java/src/org/openqa/selenium/ImmutableCapabilities.java:87-97 | java/src/org/openqa/selenium/ImmutableCapabilities.java:120-130 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/ImmutableCapabilities.java:98` calls `setCapability` and `java/src/org/openqa/selenium/ImmutableCapabilities.java:78` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 3) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:182— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:182-192 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:200-210 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:242-252 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) java/src/org/openqa/selenium/bidi/module/BrowsingContextInspector.java:138— java/src/org/openqa/selenium/bidi/module/BrowsingContextInspector.java:138-148 | java/src/org/openqa/selenium/bidi/module/Network.java:74-84 | java/src/org/openqa/selenium/bidi/module/Script.java:88-98 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Low cohesion: GraphqlHandler (LCOM4 4) java/src/org/openqa/selenium/grid/graphql/GraphqlHandler.java:67— GraphqlHandler's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: 2 (LCOM4 4) java/src/org/openqa/selenium/remote/http/jdk/JdkHttpClient.java:182— 2's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PersistentCapabilities (LCOM4 4) java/src/org/openqa/selenium/PersistentCapabilities.java:28— PersistentCapabilities's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Outbound HTTP without resilience REDACTED:394— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
Outbound HTTP without resilience REDACTED:456— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
Outbound HTTP without resilience REDACTED:517— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
Duplicated block (17 lines × 2 locations) javascript/atoms/typescript/core/locators.ts:233— javascript/atoms/typescript/core/locators.ts:233 · javascript/atoms/typescript/core/locators.ts:385 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) javascript/selenium-webdriver/bidi/browsingContext.js:167— javascript/selenium-webdriver/bidi/browsingContext.js:167 · javascript/selenium-webdriver/bidi/browsingContext.js:424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2 locations) REDACTED:822— REDACTED:822 · REDACTED:841 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2 locations) javascript/atoms/locators/classname.js:36— javascript/atoms/locators/classname.js:36 · javascript/atoms/locators/classname.js:72 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) javascript/selenium-webdriver/bidi/network.js:298— javascript/selenium-webdriver/bidi/network.js:298 · javascript/selenium-webdriver/bidi/network.js:331 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) javascript/selenium-webdriver/bidi/scriptManager.js:344— javascript/selenium-webdriver/bidi/scriptManager.js:344 · javascript/selenium-webdriver/bidi/scriptManager.js:378 — 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.
Stateful singleton: TemplatesManager third_party/dotnet/devtools/src/generator/CodeGen/TemplatesManager.cs:15— `TemplatesManager` is a singleton (one shared instance) but mutates instance state outside any lock (m_templateGenerators; e.g. `m_templateGenerators` at line 134).
Stateful singleton: CodeGenerationSettings third_party/dotnet/devtools/src/generator/CodeGen/CodeGenerationSettings.cs:9— `CodeGenerationSettings` is a singleton (one shared instance) but mutates instance state outside any lock (TemplatesPath; e.g. `TemplatesPath` at third_party/dotnet/devtools/src/generator/CodeGen/ProtocolGenerator.cs line 26, through the shared instance).
Stateful shared instance: Parameters dotnet/src/webdriver/BiDi/Command.cs:26— `Parameters` keeps one instance of itself in the static `Empty`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (RawAdditionalData; e.g. `RawAdditionalData` at line 42).
Stateful shared instance: LogContext dotnet/src/webdriver/Internal/Logging/LogContext.cs:30— `LogContext` is not registered, but the singleton `LogContextManager` creates it and keeps it in `GlobalContext`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_level, _truncationLength; e.g. `_level` at line 115).
AX2 · Stateful singletons· Process-global static state · ×2
Process-global static state: Keys dotnet/src/webdriver/Keys.cs:27— `Keys` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (descriptions; e.g. `descriptions` at line 365). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Platform dotnet/src/webdriver/Platform.cs:83— `Platform` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (current; e.g. `current` at line 133). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
selenium_manager::main (cyclomatic 27) rust/src/main.rs:184— selenium_manager::main 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.
selenium_manager::files::uncompress (cyclomatic 18) rust/src/files.rs:125— selenium_manager::files::uncompress 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.
D17 · Explicit Debt· Whole file has no live code · ×2
Whole file has no live code — 4 debt markers inside it dotnet/test/webdriver/BiDi/Input/DefaultKeyboardTests.cs:31— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 4 debt markers (4 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 4 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 1 debt marker inside it dotnet/test/webdriver/BiDi/Input/DefaultMouseTests.cs:40— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
FirefoxManager::get_browser_url_for_download (cognitive 28) rust/src/firefox.rs:551— FirefoxManager::get_browser_url_for_download has cognitive complexity 28 (threshold 15). Drivers by points: if/else 20 (27 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FirefoxManager::request_fixed_browser_version_from_online (cognitive 23) rust/src/firefox.rs:438— FirefoxManager::request_fixed_browser_version_from_online has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 1 (2 pts) (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.
Logger::create (cognitive 27) rust/src/logger.rs:88— Logger::create has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (22 pts), match/switch 2 (5 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.
Logger::logger (cognitive 26) rust/src/logger.rs:190— Logger::logger has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 6, match/switch 1 (nesting depth added 8). 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.
project_bidi_schema.checkSchema::hasUnknown (cognitive 21) javascript/selenium-webdriver/project_bidi_schema.mjs:878— project_bidi_schema.checkSchema::hasUnknown has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (21 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (project_bidi_schema.checkSchema::hasEmptyInlineRecord) 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.
project_bidi_schema.checkSchema::hasEmptyInlineRecord (cognitive 16) javascript/selenium-webdriver/project_bidi_schema.mjs:892— project_bidi_schema.checkSchema::hasEmptyInlineRecord has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (15 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (project_bidi_schema.checkSchema::hasUnknown) 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.
NewSessionRunnable.handleNewSessionRequest (cognitive 16) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:605— NewSessionRunnable.handleNewSessionRequest has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 1 (3 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.
NewSessionRunnable.handleNewSessionRequest (cognitive 16) java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:659— NewSessionRunnable.handleNewSessionRequest has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 1 (3 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.
Change coupling: EdgeDriverInfo.java ↔ GeckoDriverInfo.java java/src/org/openqa/selenium/edge/EdgeDriverInfo.java:1— `java/src/org/openqa/selenium/edge/EdgeDriverInfo.java` and `java/src/org/openqa/selenium/firefox/GeckoDriverInfo.java` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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 `48e8db2e` [grid] improved logging when driver discovery failed; `0013140f` [grid] Using SM to find drivers on PATH; `5374cf84` [java] Invoking Selenium Manager only with `--browser` — run `git show` on any of them.
Change coupling: ChromeDriverInfo.java ↔ GeckoDriverInfo.java java/src/org/openqa/selenium/chrome/ChromeDriverInfo.java:1— `java/src/org/openqa/selenium/chrome/ChromeDriverInfo.java` and `java/src/org/openqa/selenium/firefox/GeckoDriverInfo.java` 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 `48e8db2e` [grid] improved logging when driver discovery failed; `0013140f` [grid] Using SM to find drivers on PATH; `5374cf84` [java] Invoking Selenium Manager only with `--browser` — run `git show` on any of them.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:525— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:525-647 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:653-723 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1652-1677 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1745-1885 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1901-1965 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) rust/src/chrome.rs:374— rust/src/chrome.rs:374-431 | rust/src/electron.rs:143-208 | rust/src/firefox.rs:221-314 | rust/src/grid.rs:105-190 | rust/src/iexplorer.rs:120-192 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (54 corresponding lines) · ×2
Edited copy of a member (54 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:168— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:168-221 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:197-255 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (54 corresponding lines) java/src/org/openqa/selenium/grid/graphql/Types.java:37— java/src/org/openqa/selenium/grid/graphql/Types.java:37-90 | java/src/org/openqa/selenium/grid/graphql/Types.java:92-150 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×2
Edited copy of a member (46 corresponding lines) java/src/org/openqa/selenium/bidi/Connection.java:114— java/src/org/openqa/selenium/bidi/Connection.java:114-159 | java/src/org/openqa/selenium/devtools/Connection.java:145-195 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (46 corresponding lines) java/src/org/openqa/selenium/net/UrlChecker.java:58— java/src/org/openqa/selenium/net/UrlChecker.java:58-107 | java/src/org/openqa/selenium/net/UrlChecker.java:110-155 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×2
Edited copies of one member (3 members, 20+ corresponding lines) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:129— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:129-148 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:169-192 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:242-265 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 20+ corresponding lines) java/src/org/openqa/selenium/json/UriCoercer.java:33— java/src/org/openqa/selenium/json/UriCoercer.java:33-56 | java/src/org/openqa/selenium/json/UrlCoercer.java:33-56 | java/src/org/openqa/selenium/json/UuidCoercer.java:32-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×2
Edited copy of a member (34 corresponding lines) rb/support/rbs_collection_update.rb:23— rb/support/rbs_collection_update.rb:23-56 | rb/support/steep_check.rb:25-61 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) java/src/org/openqa/selenium/bidi/browsingcontext/UserPromptOpened.java:47— java/src/org/openqa/selenium/bidi/browsingcontext/UserPromptOpened.java:47-86 | java/src/org/openqa/selenium/manager/SeleniumManagerOutput.java:193-226 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1039— java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1039-1057 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1059-1085 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) java/src/org/openqa/selenium/grid/graphql/Types.java:56— java/src/org/openqa/selenium/grid/graphql/Types.java:56-74 | java/src/org/openqa/selenium/grid/graphql/Types.java:112-134 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×2
Edited copies of one member (3 members, 17+ corresponding lines) java/src/org/openqa/selenium/devtools/v155/v155Target.java:74— java/src/org/openqa/selenium/devtools/v155/v155Target.java:74-90 | java/src/org/openqa/selenium/devtools/v156/v156Target.java:74-90 | java/src/org/openqa/selenium/devtools/v157/v157Target.java:74-90 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 17+ corresponding lines) java/src/org/openqa/selenium/grid/sessionqueue/AddBackToSessionQueue.java:50— java/src/org/openqa/selenium/grid/sessionqueue/AddBackToSessionQueue.java:50-67 | java/src/org/openqa/selenium/grid/sessionqueue/SessionCreated.java:50-66 | java/src/org/openqa/selenium/grid/sessionqueue/SessionNotCreated.java:51-67 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×2
Edited copies of one member (3 members, 16+ corresponding lines) java/src/org/openqa/selenium/firefox/AddHasFullPageScreenshot.java:63— java/src/org/openqa/selenium/firefox/AddHasFullPageScreenshot.java:63-85 | java/src/org/openqa/selenium/remote/RemoteWebDriver.java:427-442 | java/src/org/openqa/selenium/remote/RemoteWebElement.java:371-386 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) py/selenium/webdriver/common/actions/pointer_actions.py:88— py/selenium/webdriver/common/actions/pointer_actions.py:88-106 | py/selenium/webdriver/common/actions/pointer_actions.py:122-137 | py/selenium/webdriver/common/actions/pointer_actions.py:153-168 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×2
Edited copies of one member (3 members, 12+ corresponding lines) java/src/org/openqa/selenium/chrome/ChromeDriver.java:102— java/src/org/openqa/selenium/chrome/ChromeDriver.java:102-113 | java/src/org/openqa/selenium/edge/EdgeDriver.java:74-85 | java/src/org/openqa/selenium/firefox/FirefoxDriver.java:114-125 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 12+ corresponding lines) java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:77— java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContext.java:77-89 | java/src/org/openqa/selenium/bidi/module/LogInspector.java:57-68 | java/src/org/openqa/selenium/bidi/module/SpeculationInspector.java:49-60 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 21+ corresponding lines) · ×2
Edited copies of one member (4 members, 21+ corresponding lines) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:520— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:520-546 | java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:549-569 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:333-358 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:361-384 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 21+ corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:565— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:565-587 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:598-620 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:630-651 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:662-682 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×2
Edited copies of one member (3 members, 14+ corresponding lines) java/src/org/openqa/selenium/internal/Require.java:383— java/src/org/openqa/selenium/internal/Require.java:383-396 | java/src/org/openqa/selenium/internal/Require.java:398-411 | java/src/org/openqa/selenium/internal/Require.java:413-428 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) rust/src/electron.rs:214— rust/src/electron.rs:214-227 | rust/src/grid.rs:196-210 | rust/src/iexplorer.rs:198-211 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×2
Edited copies of one member (3 members, 10+ corresponding lines) java/src/org/openqa/selenium/devtools/v155/v155Target.java:98— java/src/org/openqa/selenium/devtools/v155/v155Target.java:98-107 | java/src/org/openqa/selenium/devtools/v156/v156Target.java:98-107 | java/src/org/openqa/selenium/devtools/v157/v157Target.java:98-107 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) java/src/org/openqa/selenium/PageLoadStrategy.java:38— java/src/org/openqa/selenium/PageLoadStrategy.java:38-47 | java/src/org/openqa/selenium/UnexpectedAlertBehaviour.java:40-49 | java/src/org/openqa/selenium/WindowType.java:39-48 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×2
Edited copies of one member (3 members, 7+ corresponding lines) java/src/org/openqa/selenium/devtools/v155/v155Target.java:40— java/src/org/openqa/selenium/devtools/v155/v155Target.java:40-46 | java/src/org/openqa/selenium/devtools/v156/v156Target.java:40-46 | java/src/org/openqa/selenium/devtools/v157/v157Target.java:40-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) java/src/org/openqa/selenium/firefox/GeckoDriverInfo.java:46— java/src/org/openqa/selenium/firefox/GeckoDriverInfo.java:46-52 | java/src/org/openqa/selenium/safari/SafariDriverInfo.java:48-54 | java/src/org/openqa/selenium/safari/SafariTechPreviewDriverInfo.java:51-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×2
Edited copies of one member (4 members, 17+ corresponding lines) rust/src/chrome.rs:527— rust/src/chrome.rs:527-543 | rust/src/edge.rs:378-394 | rust/src/electron.rs:267-289 | rust/src/firefox.rs:394-414 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 17+ corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:690— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:690-706 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:820-838 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:852-868 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1545-1563 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×2
Edited copies of one member (3 members, 9+ corresponding lines) java/src/org/openqa/selenium/grid/data/Session.java:52— java/src/org/openqa/selenium/grid/data/Session.java:52-60 | java/src/org/openqa/selenium/grid/node/config/DriverServiceSessionFactory.java:89-97 | java/src/org/openqa/selenium/grid/node/relay/RelaySessionFactory.java:91-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) java/src/org/openqa/selenium/grid/distributor/remote/RemoteDistributor.java:98— java/src/org/openqa/selenium/grid/distributor/remote/RemoteDistributor.java:98-106 | java/src/org/openqa/selenium/grid/node/remote/RemoteNode.java:223-232 | java/src/org/openqa/selenium/grid/node/remote/RemoteNode.java:267-275 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (28–29 lines × 2) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:482— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:482-510 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:296-323 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java` and `java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:482` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28–29 lines × 2) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1426— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1426-1453 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1475-1503 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1426` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1424` calls `findElement` and `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1473` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (24 lines × 2) dotnet/src/webdriver/Interactions/PointerInputDevice.cs:592— dotnet/src/webdriver/Interactions/PointerInputDevice.cs:592-615 | dotnet/src/webdriver/Interactions/WheelInputDevice.cs:205-228 — before extracting anything, compare `dotnet/src/webdriver/Interactions/PointerInputDevice.cs` and `dotnet/src/webdriver/Interactions/WheelInputDevice.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) java/src/org/openqa/selenium/bidi/script/CallFunctionParameters.java:34— java/src/org/openqa/selenium/bidi/script/CallFunctionParameters.java:34-67 | java/src/org/openqa/selenium/bidi/script/EvaluateParameters.java:29-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23–25 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:194— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:194-218 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:226-248 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:251` calls `scheduleAtFixedRate`, `guard` and `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:220` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23–25 lines × 2) rust/src/grid.rs:112— rust/src/grid.rs:112-134 | rust/src/iexplorer.rs:126-150 — before extracting anything, compare `rust/src/grid.rs` and `rust/src/iexplorer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rust/src/grid.rs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (22–23 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:425— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:425-447 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:468-489 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22–23 lines × 2) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:523— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:523-544 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:334-356 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java` and `java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:583— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:583-604 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:620-641 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 2) java/src/org/openqa/selenium/devtools/events/DomMutationEvent.java:30— java/src/org/openqa/selenium/devtools/events/DomMutationEvent.java:30-51 | java/src/org/openqa/selenium/remote/DomMutation.java:30-51 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/events/DomMutationEvent.java` and `java/src/org/openqa/selenium/remote/DomMutation.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/devtools/events/DomMutationEvent.java:30` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21 lines × 3) java/src/org/openqa/selenium/bidi/browsingcontext/NavigationResult.java:46— java/src/org/openqa/selenium/bidi/browsingcontext/NavigationResult.java:46-66 | java/src/org/openqa/selenium/bidi/script/RegExpValue.java:44-64 | java/src/org/openqa/selenium/bidi/storage/PartitionKey.java:35-55 — before extracting anything, compare `java/src/org/openqa/selenium/bidi/browsingcontext/NavigationResult.java` and `java/src/org/openqa/selenium/bidi/script/RegExpValue.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Target.java:51— java/src/org/openqa/selenium/devtools/v155/v155Target.java:51-71 | java/src/org/openqa/selenium/devtools/v156/v156Target.java:51-71 | java/src/org/openqa/selenium/devtools/v157/v157Target.java:51-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Target` names `org.openqa.selenium.devtools.v155.target.Target` in one and `org.openqa.selenium.devtools.v156.target.Target` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (21 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:310— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:310-330 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:373-393 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:310` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) java/src/org/openqa/selenium/net/HostIdentifier.java:43— java/src/org/openqa/selenium/net/HostIdentifier.java:43-63 | java/src/org/openqa/selenium/net/NetworkUtils.java:264-284 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/net/HostIdentifier.java:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/net/HostIdentifier.java:64` calls `log` and `java/src/org/openqa/selenium/net/NetworkUtils.java:285` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 2) java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:124— java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:124-142 | java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:180-198 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:178` calls `of` and `java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:122` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:228— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:228-246 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:442-460 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:228` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 3) dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:167— dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs:167-182 | dotnet/src/webdriver/DevTools/v156/V156JavaScript.cs:167-182 | dotnet/src/webdriver/DevTools/v157/V157JavaScript.cs:167-182 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155JavaScript.cs` and `dotnet/src/webdriver/DevTools/v156/V156JavaScript.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 3) java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:54— java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:54-69 | java/src/org/openqa/selenium/grid/sessionmap/config/SessionMapOptions.java:51-66 | java/src/org/openqa/selenium/grid/sessionqueue/config/NewSessionQueueOptions.java:56-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:54` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:71` calls `BaseServerOptions`, `isSecure`, `isSelfSigned` and `java/src/org/openqa/selenium/grid/sessionmap/config/SessionMapOptions.java:68` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16–17 lines × 2) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:757— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:757-773 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:793-808 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:757` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:756` calls `findElement` and `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:792` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16–17 lines × 2) rust/src/chrome.rs:416— rust/src/chrome.rs:416-431 | rust/src/firefox.rs:298-314 — before extracting anything, compare `rust/src/chrome.rs` and `rust/src/firefox.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rust/src/chrome.rs:416` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) java/src/org/openqa/selenium/ImmutableCapabilities.java:91— java/src/org/openqa/selenium/ImmutableCapabilities.java:91-102 | java/src/org/openqa/selenium/ImmutableCapabilities.java:124-136 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/ImmutableCapabilities.java:91` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) java/src/org/openqa/selenium/grid/node/local/LocalNode.java:1196— java/src/org/openqa/selenium/grid/node/local/LocalNode.java:1196-1207 | java/src/org/openqa/selenium/grid/node/local/LocalNode.java:1229-1241 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/local/LocalNode.java:1196` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 2) java/src/org/openqa/selenium/grid/node/config/DriverServiceSessionFactory.java:165— java/src/org/openqa/selenium/grid/node/config/DriverServiceSessionFactory.java:165-174 | java/src/org/openqa/selenium/grid/node/relay/RelaySessionFactory.java:189-197 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9–10 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:210— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:210-219 | java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:241-249 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 4) java/src/org/openqa/selenium/ImmutableCapabilities.java:50— java/src/org/openqa/selenium/ImmutableCapabilities.java:50-58 | java/src/org/openqa/selenium/ImmutableCapabilities.java:67-75 | java/src/org/openqa/selenium/ImmutableCapabilities.java:88-96 | java/src/org/openqa/selenium/ImmutableCapabilities.java:121-129 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/ImmutableCapabilities.java:76` calls `setCapability` and `java/src/org/openqa/selenium/ImmutableCapabilities.java:60` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 4) rust/src/chrome.rs:489— rust/src/chrome.rs:489-497 | rust/src/edge.rs:340-348 | rust/src/electron.rs:229-237 | rust/src/firefox.rs:356-364 — before extracting anything, compare `rust/src/chrome.rs` and `rust/src/firefox.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) dotnet/src/webdriver/Chromium/ChromiumDriver.cs:159— dotnet/src/webdriver/Chromium/ChromiumDriver.cs:159-164 | dotnet/src/webdriver/Firefox/FirefoxDriver.cs:205-210 | dotnet/src/webdriver/IE/InternetExplorerDriver.cs:165-170 | dotnet/src/webdriver/Safari/SafariDriver.cs:170-175 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/webdriver/Chromium/ChromiumDriver.cs:159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `dotnet/src/webdriver/Chromium/ChromiumDriver.cs:165` calls `GetBrowserPathAsync`, `ConfigureAwait` and `dotnet/src/webdriver/IE/InternetExplorerDriver.cs:171` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) java/src/org/openqa/selenium/bidi/network/ContinueRequestParameters.java:40— java/src/org/openqa/selenium/bidi/network/ContinueRequestParameters.java:40-45 | java/src/org/openqa/selenium/bidi/network/ContinueRequestParameters.java:47-52 | java/src/org/openqa/selenium/bidi/network/ContinueResponseParameters.java:55-60 | java/src/org/openqa/selenium/bidi/network/ProvideResponseParameters.java:46-51 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 3) java/src/org/openqa/selenium/remote/NewSessionPayload.java:300— java/src/org/openqa/selenium/remote/NewSessionPayload.java:300-305 | java/src/org/openqa/selenium/remote/NewSessionPayload.java:316-321 | java/src/org/openqa/selenium/remote/NewSessionPayload.java:341-346 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/remote/NewSessionPayload.java:300` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Network.java:113— java/src/org/openqa/selenium/devtools/v155/v155Network.java:113-118 | java/src/org/openqa/selenium/devtools/v156/v156Network.java:113-118 | java/src/org/openqa/selenium/devtools/v157/v157Network.java:113-118 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Network.java` and `java/src/org/openqa/selenium/devtools/v156/v156Network.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `AuthChallengeResponse` names `org.openqa.selenium.devtools.v155.fetch.model.AuthChallengeResponse` in one and `org.openqa.selenium.devtools.v156.fetch.model.AuthChallengeResponse` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 4) java/src/org/openqa/selenium/bidi/module/BrowsingContextInspector.java:150— java/src/org/openqa/selenium/bidi/module/BrowsingContextInspector.java:150-156 | java/src/org/openqa/selenium/bidi/module/BrowsingContextInspector.java:158-164 | java/src/org/openqa/selenium/bidi/module/BrowsingContextInspector.java:226-232 | java/src/org/openqa/selenium/bidi/module/Script.java:331-337 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Note first that the copies are not typed on the same thing: the declarations holding them bind `consumer` to `Consumer<BrowsingContextInfo>` in one and `Consumer<HistoryUpdated>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 4) java/src/org/openqa/selenium/chrome/ChromeDriverService.java:339— java/src/org/openqa/selenium/chrome/ChromeDriverService.java:339-345 | java/src/org/openqa/selenium/edge/EdgeDriverService.java:346-352 | java/src/org/openqa/selenium/firefox/GeckoDriverService.java:327-333 | java/src/org/openqa/selenium/ie/InternetExplorerDriverService.java:245-251 — before extracting anything, compare `java/src/org/openqa/selenium/chrome/ChromeDriverService.java` and `java/src/org/openqa/selenium/edge/EdgeDriverService.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/chrome/ChromeDriverService.java:339` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (33 lines × 2 locations) javascript/selenium-webdriver/bidi/network.js:53— javascript/selenium-webdriver/bidi/network.js:53 · javascript/selenium-webdriver/bidi/scriptManager.js:46 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (33 lines × 2 locations) REDACTED:2729— REDACTED:2729 · REDACTED:3254 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (27 lines × 2 locations) javascript/selenium-webdriver/bidi/continueResponseParameters.js:83— javascript/selenium-webdriver/bidi/continueResponseParameters.js:83 · javascript/selenium-webdriver/bidi/provideResponseParameters.js:77 — 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 (27 lines × 2 locations) javascript/webdriver/atoms/inject/local_storage.js:22— javascript/webdriver/atoms/inject/local_storage.js:22 · javascript/webdriver/atoms/inject/session_storage.js:22 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (18 lines × 2 locations) REDACTED:131— REDACTED:131 · REDACTED:247 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) javascript/selenium-webdriver/bidi/cookieFilter.js:62— javascript/selenium-webdriver/bidi/cookieFilter.js:62 · javascript/selenium-webdriver/bidi/partialCookie.js:42 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
Duplicated block (16 lines × 2 locations) javascript/grid-ui/src/components/Node/NodeDetailsDialog.tsx:94— javascript/grid-ui/src/components/Node/NodeDetailsDialog.tsx:94 · javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx:731 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (16 lines × 2 locations) javascript/webdriver/atoms/inject/action.js:224— javascript/webdriver/atoms/inject/action.js:224 · javascript/webdriver/atoms/inject/dom.js:152 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (14 matched lines × 2 locations) · ×2
Duplicated block with local edits (14 matched lines × 2 locations) javascript/atoms/locators/link_text.js:26— javascript/atoms/locators/link_text.js:26 · javascript/atoms/locators/link_text.js:61 — the two spans are one implementation copied and then locally edited — 129 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (14 matched lines × 2 locations) javascript/bidi-support/bidi-mutation-listener.js:18— javascript/bidi-support/bidi-mutation-listener.js:18 · javascript/cdp-support/mutation-listener.js:18 — the two spans are one implementation copied and then locally edited — 112 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (13 lines × 2 locations) javascript/grid-ui/src/components/QueuedSessions/QueuedSessions.tsx:84— javascript/grid-ui/src/components/QueuedSessions/QueuedSessions.tsx:84 · javascript/grid-ui/src/components/QueuedSessions/QueuedSessions.tsx:116 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (13 lines × 2 locations) javascript/selenium-webdriver/testing/index.js:325— javascript/selenium-webdriver/testing/index.js:325 · javascript/selenium-webdriver/testing/index.js:339 — 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.
Dead file (~347 LoC) javascript/selenium-webdriver/bidi_schema_diff_test.mjs— no import path from any entry point (83 application, 15 tooling, 132 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 (~347 LoC) javascript/webdriver/logging.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~248 LoC) javascript/atoms/locators/xpath.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~248 LoC) javascript/webdriver/command.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~205 LoC) javascript/atoms/userAgent.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~205 LoC) javascript/webdriver/atoms/inputs.js— no import path from any entry point (83 application, 15 tooling, 132 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
roles.implicitRole (cyclomatic 82) javascript/atoms/typescript/core/accessibility/roles.ts:248— roles.implicitRole has cyclomatic complexity 82 (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.
checkSchema (cyclomatic 71) javascript/selenium-webdriver/project_bidi_schema.mjs:873— checkSchema has cyclomatic complexity 71 (threshold 15). Of this number, 43 points are the body's own statements and 28 belong to 14 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CddlModule.generate_code (cyclomatic 62) py/generate_bidi.py:638— CddlModule.generate_code has cyclomatic complexity 62 (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.
Generator.appendRecordBody (cyclomatic 54) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:726— Generator.appendRecordBody has cyclomatic complexity 54 (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.
overflow.getOverflowState (cyclomatic 54) javascript/atoms/typescript/core/overflow.ts:40— overflow.getOverflowState has cyclomatic complexity 54 (threshold 15). Of this number, 32 points are the body's own statements and 22 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
record.validateValue (cyclomatic 51) javascript/selenium-webdriver/bidi/serialization/record.js:50— record.validateValue has cyclomatic complexity 51 (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.
dom.bot.dom.getOverflowState (cyclomatic 48) javascript/atoms/dom.js:667— dom.bot.dom.getOverflowState has cyclomatic complexity 48 (threshold 15). Of this number, 31 points are the body's own statements and 17 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
get-attribute.get (cyclomatic 42) javascript/atoms/typescript/get-attribute.ts:28— get-attribute.get has cyclomatic complexity 42 (threshold 15). Of this number, 29 points are the body's own statements and 13 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Builder.build (cyclomatic 39) javascript/selenium-webdriver/index.js:601— Builder.build has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
W3CHttpCommandCodec.amendParameters (cyclomatic 37) java/src/org/openqa/selenium/remote/codec/w3c/W3CHttpCommandCodec.java:169— W3CHttpCommandCodec.amendParameters 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.
RunningSessions.RunningSessions (cyclomatic 37) javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx:175— RunningSessions.RunningSessions has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 10 of the 37 points are its own statements and the rest belongs to 9 function items inside it that branch (handleDeleteSession, handleClick, getCapabilityValue, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
dom.bot.dom.isShown_ (cyclomatic 36) javascript/atoms/dom.js:460— dom.bot.dom.isShown_ has cyclomatic complexity 36 (threshold 15). Of this number, 19 points are the body's own statements and 17 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WebDriver.UnpackAndThrowOnError (cyclomatic 35) dotnet/src/webdriver/WebDriver.cs:894— WebDriver.UnpackAndThrowOnError has cyclomatic complexity 35 (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.
JsonOutput.resolveConverter (cyclomatic 34) java/src/org/openqa/selenium/json/JsonOutput.java:115— JsonOutput.resolveConverter has cyclomatic complexity 34 (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.
CddlCommand.to_python_method (cyclomatic 34) py/generate_bidi.py:204— CddlCommand.to_python_method has cyclomatic complexity 34 (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.
ErrorHandler.check_response (cyclomatic 34) py/selenium/webdriver/remote/errorhandler.py:145— ErrorHandler.check_response has cyclomatic complexity 34 (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.
projectSchema (cyclomatic 30) javascript/selenium-webdriver/project_bidi_schema.mjs:677— projectSchema has cyclomatic complexity 30 (threshold 15). Of this number, 18 points are the body's own statements and 12 belong to 6 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.
RemoteValue.ConvertTo (cyclomatic 28) dotnet/src/webdriver/BiDi/Script/RemoteValue.cs:65— RemoteValue.ConvertTo has cyclomatic complexity 28 (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 is NOT this file's highest cyclomatic complexity: RemoteValueConverter.Read (cyclomatic 29) 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.
ConstructorCoercer.tryDirectCoercion (cyclomatic 28) java/src/org/openqa/selenium/json/ConstructorCoercer.java:191— ConstructorCoercer.tryDirectCoercion 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.
accname.nativeName (cyclomatic 28) javascript/atoms/typescript/core/accessibility/accname.ts:420— accname.nativeName has cyclomatic complexity 28 (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.
corpus-consistent.validate (cyclomatic 28) javascript/atoms/typescript/testing/corpus-consistent.mjs:68— corpus-consistent.validate has cyclomatic complexity 28 (threshold 15). Of this number, 27 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.
projectEntry (cyclomatic 27) javascript/selenium-webdriver/project_bidi_schema.mjs:224— projectEntry has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Broker.ProcessReceivedMessage (cyclomatic 26) dotnet/src/webdriver/BiDi/Broker.cs:221— Broker.ProcessReceivedMessage has cyclomatic complexity 26 (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.
Proxy.Proxy.ctor (cyclomatic 26) dotnet/src/webdriver/Proxy.cs:95— Proxy.Proxy.ctor 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.
locators.relativeMany (cyclomatic 26) javascript/atoms/typescript/core/locators.ts:501— locators.relativeMany 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 8 function literals inside it that branch (lines 542, 549, 572, …). 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.
by.escapeCss (cyclomatic 26) javascript/selenium-webdriver/lib/by.js:67— by.escapeCss has cyclomatic complexity 26 (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.
ModuleGenerator.main (cyclomatic 25) java/src/dev/selenium/tools/modules/ModuleGenerator.java:98— ModuleGenerator.main has cyclomatic complexity 25 (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.
attribute.get (cyclomatic 25) javascript/webdriver/atoms/attribute.js:110— attribute.get has cyclomatic complexity 25 (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.
ErrorHandler.throwIfResponseFailed (cyclomatic 24) java/src/org/openqa/selenium/remote/ErrorHandler.java:86— ErrorHandler.throwIfResponseFailed has cyclomatic complexity 24 (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.
script.deserialize_result (cyclomatic 24) py/selenium/webdriver/remote/script.py:238— script.deserialize_result has cyclomatic complexity 24 (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.
accname.computeTextAlternative (cyclomatic 24) javascript/atoms/typescript/core/accessibility/accname.ts:499— accname.computeTextAlternative has cyclomatic complexity 24 (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.
SeleniumManager.RunCommandAsync (cyclomatic 23) dotnet/src/webdriver/Manager/SeleniumManager.cs:256— SeleniumManager.RunCommandAsync has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FirefoxOptions.merge (cyclomatic 23) java/src/org/openqa/selenium/firefox/FirefoxOptions.java:307— FirefoxOptions.merge 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.
DriverCommandExecutor.execute (cyclomatic 22) java/src/org/openqa/selenium/remote/service/DriverCommandExecutor.java:114— DriverCommandExecutor.execute 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.
Environment.builder (cyclomatic 22) javascript/selenium-webdriver/testing/index.js:315— Environment.builder has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: 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.
V148Adapter.adaptContainerCreateRequest (cyclomatic 21) java/src/org/openqa/selenium/docker/client/V148Adapter.java:110— V148Adapter.adaptContainerCreateRequest 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.
JsonInput.parseDouble (cyclomatic 21) java/src/org/openqa/selenium/json/JsonInput.java:400— JsonInput.parseDouble 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. This is NOT this file's highest cyclomatic complexity: JsonInput.peek (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.
NetworkUtils.determineHostnameAndAddress (cyclomatic 21) java/src/org/openqa/selenium/net/NetworkUtils.java:255— NetworkUtils.determineHostnameAndAddress 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.
api_request_context._cookie_matches (cyclomatic 21) py/selenium/webdriver/common/api_request_context.py:103— api_request_context._cookie_matches 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.
EdgeManager::request_latest_browser_version_from_online (cyclomatic 21) rust/src/edge.rs:396— EdgeManager::request_latest_browser_version_from_online 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.
action.bot.action.type (cyclomatic 21) javascript/atoms/action.js:172— action.bot.action.type has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
defineRecord (cyclomatic 21) javascript/selenium-webdriver/bidi/serialization/record.js:236— defineRecord has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 5 function items inside it that branch (constructor, fromWire, toJSON, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
generateDomainFile (cyclomatic 21) javascript/selenium-webdriver/generate_bidi.mjs:942— generateDomainFile 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.
InternetExplorerOptions.BuildInternetExplorerOptionsDictionary (cyclomatic 20) dotnet/src/webdriver/IE/InternetExplorerOptions.cs:275— InternetExplorerOptions.BuildInternetExplorerOptionsDictionary 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.
ChromiumOptions.mergeInPlace (cyclomatic 20) java/src/org/openqa/selenium/chromium/ChromiumOptions.java:273— ChromiumOptions.mergeInPlace 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.
KubernetesOptions.inspectNodePod (cyclomatic 20) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:390— KubernetesOptions.inspectNodePod 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.
generate_bidi_protocol._imports (cyclomatic 20) py/generate_bidi_protocol.py:1083— generate_bidi_protocol._imports 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.
device.bot.Device.focusOnElement (cyclomatic 20) REDACTED:456— device.bot.Device.focusOnElement has cyclomatic complexity 20 (threshold 15). Of this number, 18 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.
xpath.bot.locators.xpath.evaluate_ (cyclomatic 20) javascript/atoms/locators/xpath.js:90— xpath.bot.locators.xpath.evaluate_ 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.
ChromiumOptions.BuildChromeOptionsDictionary (cyclomatic 19) dotnet/src/webdriver/Chromium/ChromiumOptions.cs:515— ChromiumOptions.BuildChromeOptionsDictionary has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DriverOptions.GenerateDesiredCapabilities (cyclomatic 19) dotnet/src/webdriver/DriverOptions.cs:413— DriverOptions.GenerateDesiredCapabilities has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FirefoxDriverService.CommandLineArguments.get (cyclomatic 19) dotnet/src/webdriver/Firefox/FirefoxDriverService.cs:167— FirefoxDriverService.CommandLineArguments.get has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Generator.computeReachable (cyclomatic 19) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:442— Generator.computeReachable 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 shape REPEATS in the file: one other method here (Generator.computeReceivableTypes) 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.
Generator.computeReceivableTypes (cyclomatic 19) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:295— Generator.computeReceivableTypes 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 shape REPEATS in the file: one other method here (Generator.computeReachable) 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.
Network.prepareToInterceptTraffic (cyclomatic 19) java/src/org/openqa/selenium/devtools/idealized/Network.java:167— Network.prepareToInterceptTraffic 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.
V148Adapter.adaptContainerInspectResponse (cyclomatic 19) java/src/org/openqa/selenium/docker/client/V148Adapter.java:204— V148Adapter.adaptContainerInspectResponse 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.
KubernetesSessionFactory.buildJobSpec (cyclomatic 19) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:560— KubernetesSessionFactory.buildJobSpec has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
W3CHttpResponseCodec.decode (cyclomatic 19) java/src/org/openqa/selenium/remote/codec/w3c/W3CHttpResponseCodec.java:72— W3CHttpResponseCodec.decode 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.
EventFiringDecorator.fireAfterEvents (cyclomatic 19) java/src/org/openqa/selenium/support/events/EventFiringDecorator.java:264— EventFiringDecorator.fireAfterEvents has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
dom.bot.dom.appendVisibleTextLinesFromElementCommon_ (cyclomatic 19) javascript/atoms/dom.js:1049— dom.bot.dom.appendVisibleTextLinesFromElementCommon_ has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
accname.computeContentText (cyclomatic 19) javascript/atoms/typescript/core/accessibility/accname.ts:328— accname.computeContentText 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.
WebDriver.wait (cyclomatic 19) REDACTED:860— WebDriver.wait has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 belong to 6 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.
ChromiumDriverService.CommandLineArguments.get (cyclomatic 18) dotnet/src/webdriver/Chromium/ChromiumDriverService.cs:107— ChromiumDriverService.CommandLineArguments.get 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.
Generator.computeSenderTypes (cyclomatic 18) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:250— Generator.computeSenderTypes 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.
KubernetesSessionFactory.evaluatePodStatus (cyclomatic 18) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1169— KubernetesSessionFactory.evaluatePodStatus 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.
LocalNode.newSession (cyclomatic 18) java/src/org/openqa/selenium/grid/node/local/LocalNode.java:499— LocalNode.newSession 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.
MessageInboundConverter.channelRead0 (cyclomatic 18) java/src/org/openqa/selenium/netty/server/MessageInboundConverter.java:59— MessageInboundConverter.channelRead0 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.
Logger::logger (cyclomatic 18) rust/src/logger.rs:190— Logger::logger 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.
get-text.appendTextFromElementCommon (cyclomatic 18) javascript/atoms/typescript/get-text.ts:161— get-text.appendTextFromElementCommon 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.
keyboard.editContent (cyclomatic 18) javascript/atoms/typescript/core/keyboard.ts:325— keyboard.editContent 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.
LocalValue.getArgument (cyclomatic 18) javascript/selenium-webdriver/bidi/protocolValue.js:192— LocalValue.getArgument 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.
Generator.generateUnion (cyclomatic 17) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1744— Generator.generateUnion 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.
SimplePropertyDescriptor.computePropertyDescriptors (cyclomatic 17) java/src/org/openqa/selenium/json/SimplePropertyDescriptor.java:84— SimplePropertyDescriptor.computePropertyDescriptors 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.
CddlParser._extract_parameters_and_required (cyclomatic 17) py/generate_bidi.py:1398— CddlParser._extract_parameters_and_required 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.
type.type (cyclomatic 17) javascript/atoms/typescript/type.ts:118— type.type 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.
collectUnionMembers (cyclomatic 17) javascript/selenium-webdriver/generate_bidi.mjs:394— collectUnionMembers has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs 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.
dedupeDefs (cyclomatic 17) javascript/selenium-webdriver/normalize_bidi_ast.mjs:530— dedupeDefs 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.
HttpCommandExecutor.execute (cyclomatic 16) java/src/org/openqa/selenium/remote/HttpCommandExecutor.java:212— HttpCommandExecutor.execute 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.
EventFiringDecorator.fireBeforeEvents (cyclomatic 16) java/src/org/openqa/selenium/support/events/EventFiringDecorator.java:214— EventFiringDecorator.fireBeforeEvents 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.
serialization._read_scalar (cyclomatic 16) py/selenium/webdriver/common/_bidi/serialization.py:432— serialization._read_scalar 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.
action.bot.action.clear (cyclomatic 16) javascript/atoms/action.js:86— action.bot.action.clear 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.
dom.bot.dom.isShown::displayed (cyclomatic 16) javascript/atoms/dom.js:600— dom.bot.dom.isShown::displayed 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.
LogInspector.onLog (cyclomatic 16) javascript/selenium-webdriver/bidi/logInspector.js:236— LogInspector.onLog 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 one function literal inside it that branches (line 250). 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.
project_bidi_schema.checkSelector (cyclomatic 16) javascript/selenium-webdriver/project_bidi_schema.mjs:997— project_bidi_schema.checkSelector 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, 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.
checkSchema (cognitive 118) javascript/selenium-webdriver/project_bidi_schema.mjs:873— checkSchema has cognitive complexity 118 (threshold 15). Drivers by points: if/else 23 (54 pts), loops 15 (34 pts), boolean chains 13, ternaries 11, other 6 (nesting depth added 50). Of this number, 89 points are the body's own statements and 29 belong to 14 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CddlModule.generate_code (cognitive 97) py/generate_bidi.py:638— CddlModule.generate_code has cognitive complexity 97 (threshold 15). Drivers by points: if/else 37 (65 pts), loops 17 (25 pts), boolean chains 7 (nesting depth added 36). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Generator.appendRecordBody (cognitive 96) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:726— Generator.appendRecordBody has cognitive complexity 96 (threshold 15). Drivers by points: if/else 26 (48 pts), loops 9 (21 pts), boolean chains 17, ternaries 5 (10 pts) (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
record.validateValue (cognitive 89) javascript/selenium-webdriver/bidi/serialization/record.js:50— record.validateValue has cognitive complexity 89 (threshold 15). Drivers by points: if/else 35 (70 pts), boolean chains 8, loops 4 (8 pts), error handling 1 (3 pts) (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ErrorHandler.check_response (cognitive 77) py/selenium/webdriver/remote/errorhandler.py:145— ErrorHandler.check_response has cognitive complexity 77 (threshold 15). Drivers by points: if/else 23 (53 pts), error handling 2 (7 pts), boolean chains 6, ternaries 1 (6 pts), loops 2 (5 pts) (nesting depth added 43). 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.
overflow.getOverflowState (cognitive 72) javascript/atoms/typescript/core/overflow.ts:40— overflow.getOverflowState has cognitive complexity 72 (threshold 15). Drivers by points: if/else 18 (32 pts), boolean chains 26, ternaries 5 (12 pts), loops 2 (nesting depth added 21). Of this number, 48 points are the body's own statements and 24 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getOverflowState (cognitive 69) javascript/atoms/dom.js:667— getOverflowState has cognitive complexity 69 (threshold 15). Drivers by points: if/else 20 (32 pts), boolean chains 22, ternaries 5 (12 pts), loops 2 (3 pts) (nesting depth added 20). Of this number, 45 points are the body's own statements and 24 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
V148Adapter.adaptContainerCreateRequest (cognitive 68) java/src/org/openqa/selenium/docker/client/V148Adapter.java:110— V148Adapter.adaptContainerCreateRequest has cognitive complexity 68 (threshold 15). Drivers by points: if/else 14 (52 pts), loops 2 (6 pts), ternaries 1 (6 pts), boolean chains 4 (nesting depth added 47). 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.
CddlCommand.to_python_method (cognitive 68) py/generate_bidi.py:204— CddlCommand.to_python_method has cognitive complexity 68 (threshold 15). Drivers by points: if/else 28 (49 pts), loops 7 (15 pts), boolean chains 4 (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.
V148Adapter.adaptContainerInspectResponse (cognitive 53) java/src/org/openqa/selenium/docker/client/V148Adapter.java:204— V148Adapter.adaptContainerInspectResponse has cognitive complexity 53 (threshold 15). Drivers by points: if/else 11 (34 pts), ternaries 2 (11 pts), loops 2 (5 pts), boolean chains 3 (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.
get-attribute.get (cognitive 53) javascript/atoms/typescript/get-attribute.ts:28— get-attribute.get has cognitive complexity 53 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 15, ternaries 6 (11 pts), error handling 1 (nesting depth added 12). Of this number, 40 points are the body's own statements and 13 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Generator.computeReachable (cognitive 49) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:442— Generator.computeReachable has cognitive complexity 49 (threshold 15). Drivers by points: if/else 10 (34 pts), loops 5 (12 pts), boolean chains 3 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (Generator.computeReceivableTypes) 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.
Generator.computeReceivableTypes (cognitive 49) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:295— Generator.computeReceivableTypes has cognitive complexity 49 (threshold 15). Drivers by points: if/else 10 (34 pts), loops 5 (12 pts), boolean chains 3 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (Generator.computeReachable) 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.
Generator.computeSenderTypes (cognitive 48) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:250— Generator.computeSenderTypes has cognitive complexity 48 (threshold 15). Drivers by points: if/else 10 (34 pts), loops 4 (11 pts), boolean chains 3 (nesting depth added 31). 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.
FirefoxOptions.merge (cognitive 48) java/src/org/openqa/selenium/firefox/FirefoxOptions.java:307— FirefoxOptions.merge has cognitive complexity 48 (threshold 15). Drivers by points: if/else 19 (38 pts), error handling 2 (8 pts), boolean chains 1, loops 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
evaluate_ (cognitive 46) javascript/atoms/locators/xpath.js:90— evaluate_ has cognitive complexity 46 (threshold 15). Drivers by points: if/else 11 (27 pts), loops 2 (6 pts), boolean chains 5, ternaries 2 (5 pts), error handling 2 (3 pts) (nesting depth added 24). Of this number, 45 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Broker.ProcessReceivedMessage (cognitive 44) dotnet/src/webdriver/BiDi/Broker.cs:221— Broker.ProcessReceivedMessage has cognitive complexity 44 (threshold 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.
NetworkUtils.determineHostnameAndAddress (cognitive 43) java/src/org/openqa/selenium/net/NetworkUtils.java:255— NetworkUtils.determineHostnameAndAddress has cognitive complexity 43 (threshold 15). Drivers by points: if/else 11 (21 pts), error handling 6 (15 pts), loops 2 (6 pts), boolean chains 1 (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.
ConstructorCoercer.tryDirectCoercion (cognitive 42) java/src/org/openqa/selenium/json/ConstructorCoercer.java:191— ConstructorCoercer.tryDirectCoercion has cognitive complexity 42 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 11, loops 1 (2 pts), ternaries 1 (2 pts) (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.
build (cognitive 42) javascript/selenium-webdriver/index.js:601— build has cognitive complexity 42 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 11, match/switch 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.
W3CHttpResponseCodec.decode (cognitive 41) java/src/org/openqa/selenium/remote/codec/w3c/W3CHttpResponseCodec.java:72— W3CHttpResponseCodec.decode has cognitive complexity 41 (threshold 15). Drivers by points: if/else 19 (38 pts), boolean chains 3 (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.
DriverCommandExecutor.execute (cognitive 40) java/src/org/openqa/selenium/remote/service/DriverCommandExecutor.java:114— DriverCommandExecutor.execute has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (23 pts), error handling 6 (12 pts), boolean chains 5 (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.
dom.bot.dom.appendVisibleTextLinesFromNodeInComposedDom_ (cognitive 39) javascript/atoms/dom.js:1363— dom.bot.dom.appendVisibleTextLinesFromNodeInComposedDom_ has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 3 (11 pts), ternaries 1 (4 pts), boolean chains 2 (nesting depth added 22). 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.
generateDomainFile (cognitive 38) javascript/selenium-webdriver/generate_bidi.mjs:942— generateDomainFile has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (22 pts), loops 4 (8 pts), ternaries 1 (4 pts), boolean chains 3, other 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ErrorHandler.throwIfResponseFailed (cognitive 36) java/src/org/openqa/selenium/remote/ErrorHandler.java:86— ErrorHandler.throwIfResponseFailed has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (27 pts), error handling 2 (5 pts), boolean chains 4 (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.
JsonOutput.resolveConverter (cognitive 35) java/src/org/openqa/selenium/json/JsonOutput.java:115— JsonOutput.resolveConverter has cognitive complexity 35 (threshold 15). Drivers by points: if/else 27 (29 pts), boolean chains 3, loops 2, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
corpus-consistent.validate (cognitive 35) javascript/atoms/typescript/testing/corpus-consistent.mjs:68— corpus-consistent.validate has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 11, loops 2 (4 pts) (nesting depth added 8). Of this number, 34 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.
RunningSessions.RunningSessions (cognitive 35) javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx:175— RunningSessions.RunningSessions has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 8, error handling 5 (6 pts), ternaries 4 (nesting depth added 2). Most of this is not in the body itself: 7 of the 35 points are its own statements and the rest belongs to 9 function items inside it that branch (handleDeleteSession, handleClick, getCapabilityValue, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Proxy.Proxy.ctor (cognitive 34) dotnet/src/webdriver/Proxy.cs:95— Proxy.Proxy.ctor has cognitive complexity 34 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MessageInboundConverter.channelRead0 (cognitive 34) java/src/org/openqa/selenium/netty/server/MessageInboundConverter.java:59— MessageInboundConverter.channelRead0 has cognitive complexity 34 (threshold 15). Drivers by points: if/else 18 (26 pts), error handling 2 (6 pts), match/switch 1 (2 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.
SeleniumManager.RunCommandAsync (cognitive 33) dotnet/src/webdriver/Manager/SeleniumManager.cs:256— SeleniumManager.RunCommandAsync has cognitive complexity 33 (threshold 15). Of this number, 31 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
script.deserialize_result (cognitive 33) py/selenium/webdriver/remote/script.py:238— script.deserialize_result has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 5 (11 pts), boolean chains 5, 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.
isShown_ (cognitive 33) javascript/atoms/dom.js:460— isShown_ has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 16 (nesting depth added 1). Of this number, 16 points are the body's own statements and 17 belong to 5 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
projectEntry (cognitive 33) javascript/selenium-webdriver/project_bidi_schema.mjs:224— projectEntry has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 7, ternaries 3 (7 pts), other 3 (nesting depth added 7). Of this number, 32 points are the body's own statements and 1 belongs to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PollingRunnable.run (cognitive 32) java/src/org/openqa/selenium/events/zeromq/UnboundZmqEventBus.java:242— PollingRunnable.run has cognitive complexity 32 (threshold 15). Drivers by points: if/else 5 (18 pts), error handling 3 (10 pts), loops 2 (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.
attribute.get (cognitive 32) javascript/webdriver/atoms/attribute.js:110— attribute.get has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 9, ternaries 3 (5 pts), error handling 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.
collectUnionMembers (cognitive 32) javascript/selenium-webdriver/generate_bidi.mjs:394— collectUnionMembers has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 4 (8 pts), ternaries 3 (6 pts), other 2, boolean chains 1 (nesting depth added 14). Of this number, 29 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.
JsonInput.parseDouble (cognitive 31) java/src/org/openqa/selenium/json/JsonInput.java:400— JsonInput.parseDouble has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 5, loops 3 (5 pts), ternaries 1 (2 pts) (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.
Index.constructor (cognitive 31) javascript/selenium-webdriver/bidi/index.js:33— Index.constructor has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (10 pts), error handling 3 (8 pts), ternaries 1 (6 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 16). None of this is in the body itself: all 31 points belong to 2 function literals inside it that branch (lines 66, 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.
defineRecord (cognitive 31) javascript/selenium-webdriver/bidi/serialization/record.js:236— defineRecord has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 5, boolean chains 4, other 1 (nesting depth added 10). None of this is in the body itself: all 31 points belong to 5 function items inside it that branch (fromWire, constructor, toJSON, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ChromiumOptions.mergeInPlace (cognitive 30) java/src/org/openqa/selenium/chromium/ChromiumOptions.java:273— ChromiumOptions.mergeInPlace has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 4, loops 2 (3 pts) (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.
KubernetesOptions.inspectNodePod (cognitive 30) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:390— KubernetesOptions.inspectNodePod has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 4, ternaries 4, error handling 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.
action.bot.action.type (cognitive 30) javascript/atoms/action.js:172— action.bot.action.type has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 6, ternaries 1 (2 pts) (nesting depth added 8). Of this number, 16 points are the body's own statements and 14 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Generator.generateUnion (cognitive 29) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1744— Generator.generateUnion has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 2 (5 pts), boolean chains 3, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
clear (cognitive 29) javascript/atoms/action.js:86— clear has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (18 pts), ternaries 3 (9 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.
Select.selectByVisibleText (cognitive 28) java/src/org/openqa/selenium/support/ui/Select.java:345— Select.selectByVisibleText has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 2 (5 pts), loops 2 (3 pts) (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.
CddlParser._extract_parameters_and_required (cognitive 28) py/generate_bidi.py:1398— CddlParser._extract_parameters_and_required has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 2 (4 pts), boolean chains 3 (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.
LogInspector.onLog (cognitive 28) javascript/selenium-webdriver/bidi/logInspector.js:236— LogInspector.onLog has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 2 (nesting depth added 12). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 250). 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.
KubernetesSessionFactory.evaluatePodStatus (cognitive 27) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:1169— KubernetesSessionFactory.evaluatePodStatus has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 5, loops 2 (4 pts), ternaries 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.
SimplePropertyDescriptor.computePropertyDescriptors (cognitive 27) java/src/org/openqa/selenium/json/SimplePropertyDescriptor.java:84— SimplePropertyDescriptor.computePropertyDescriptors has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 2 (6 pts), boolean chains 5, loops 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.
EdgeManager::request_latest_browser_version_from_online (cognitive 27) rust/src/edge.rs:396— EdgeManager::request_latest_browser_version_from_online has cognitive complexity 27 (threshold 15). Drivers by points: if/else 22 (23 pts), boolean chains 4 (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.
accname.computeTextAlternative (cognitive 27) javascript/atoms/typescript/core/accessibility/accname.ts:499— accname.computeTextAlternative has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 9, 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.
(anonymous) (cognitive 27) javascript/selenium-webdriver/bidi/index.js:66— (anonymous) has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 2 (6 pts), ternaries 1 (6 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 15). 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.
DevToolsSession.SendCommand (cognitive 25) REDACTED:256— DevToolsSession.SendCommand has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Network.prepareToInterceptTraffic (cognitive 25) java/src/org/openqa/selenium/devtools/idealized/Network.java:167— Network.prepareToInterceptTraffic has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (19 pts), error handling 6 (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.
AnnotatedConfig.<init> (cognitive 25) java/src/org/openqa/selenium/grid/config/AnnotatedConfig.java:59— AnnotatedConfig.<init> has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (4 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CddlParser._extract_type_fields (cognitive 25) py/generate_bidi.py:1245— CddlParser._extract_type_fields has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (6 pts), boolean chains 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.
device.bot.Device.focusOnElement (cognitive 25) REDACTED:456— device.bot.Device.focusOnElement has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, if/else 6 (11 pts), error handling 1 (3 pts) (nesting depth added 7). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
accname.computeContentText (cognitive 25) javascript/atoms/typescript/core/accessibility/accname.ts:328— accname.computeContentText has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 6, ternaries 3 (5 pts), 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.
project_bidi_schema.projectSchema (cognitive 25) javascript/selenium-webdriver/project_bidi_schema.mjs:677— project_bidi_schema.projectSchema has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (29 pts), loops 9 (11 pts), boolean chains 2, ternaries 1 (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.
project_bidi_schema.checkSelector (cognitive 25) javascript/selenium-webdriver/project_bidi_schema.mjs:997— project_bidi_schema.checkSelector has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 10). Of this number, 15 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ErrorResponse.ErrorResponse.ctor (cognitive 24) dotnet/src/webdriver/ErrorResponse.cs:39— ErrorResponse.ErrorResponse.ctor has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DefaultWait.Until (cognitive 24) dotnet/src/webdriver/Support/DefaultWait{T}.cs:132— DefaultWait.Until has cognitive complexity 24 (threshold 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.
SemanticVersionComparator.compare (cognitive 24) java/src/org/openqa/selenium/grid/data/SemanticVersionComparator.java:26— SemanticVersionComparator.compare has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 3 (7 pts), boolean chains 3, 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.
Proxy.to_bidi_dict (cognitive 24) py/selenium/webdriver/common/proxy.py:187— Proxy.to_bidi_dict has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 1 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Select.select_by_visible_text (cognitive 24) py/selenium/webdriver/support/select.py:103— Select.select_by_visible_text has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 2 (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.
type.type (cognitive 24) javascript/atoms/typescript/type.ts:118— type.type has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
roles.implicitRole (cognitive 24) javascript/atoms/typescript/core/accessibility/roles.ts:248— roles.implicitRole has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 3 (6 pts), boolean chains 3, 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.
updateOnLeftOrRight_ (cognitive 24) javascript/atoms/keyboard.js:814— updateOnLeftOrRight_ has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (18 pts), ternaries 2 (6 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.
builder (cognitive 24) javascript/selenium-webdriver/testing/index.js:315— builder has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 3). Of this number, 12 points are the body's own statements and 12 belong to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WebSocketConnection.ReceiveData (cognitive 23) dotnet/src/webdriver/DevTools/WebSocketConnection.cs:226— WebSocketConnection.ReceiveData has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
WebDriver.UnpackAndThrowOnError (cognitive 23) dotnet/src/webdriver/WebDriver.cs:894— WebDriver.UnpackAndThrowOnError has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LocalNode.newSession (cognitive 23) java/src/org/openqa/selenium/grid/node/local/LocalNode.java:499— LocalNode.newSession has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 3, loops 1 (nesting depth added 4). 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.
WebSocketFrameProxy.forwardFrame (cognitive 23) java/src/org/openqa/selenium/netty/server/WebSocketFrameProxy.java:105— WebSocketFrameProxy.forwardFrame has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), error handling 2 (6 pts), match/switch 1 (2 pts) (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.
ClientConfig.get_proxy_url (cognitive 23) py/selenium/webdriver/remote/client_config.py:174— ClientConfig.get_proxy_url has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 3 (6 pts), loops 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.
create (cognitive 23) javascript/atoms/events.js:356— create has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (9 pts), boolean chains 4 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
wait (cognitive 23) REDACTED:860— wait has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5, error handling 3 (5 pts) (nesting depth added 4). Most of this is not in the body itself: 9 of the 23 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 934, a function literal at line 870, a function literal at line 877, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
dedupeDefs (cognitive 23) javascript/selenium-webdriver/normalize_bidi_ast.mjs:530— dedupeDefs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5, other 4, ternaries 1 (2 pts), 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.
ChromiumDriverService.CommandLineArguments.get (cognitive 22) dotnet/src/webdriver/Chromium/ChromiumDriverService.cs:107— ChromiumDriverService.CommandLineArguments.get has cognitive complexity 22 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
InternetExplorerOptions.BuildInternetExplorerOptionsDictionary (cognitive 22) dotnet/src/webdriver/IE/InternetExplorerOptions.cs:275— InternetExplorerOptions.BuildInternetExplorerOptionsDictionary has cognitive complexity 22 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Proxy.AsDictionary (cognitive 22) dotnet/src/webdriver/Proxy.cs:442— Proxy.AsDictionary has cognitive complexity 22 (threshold 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.
WebDriver.ParseJavaScriptReturnValue (cognitive 22) dotnet/src/webdriver/WebDriver.cs:1112— WebDriver.ParseJavaScriptReturnValue has cognitive complexity 22 (threshold 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.
Generator.appendConstructorAssignment (cognitive 22) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1518— Generator.appendConstructorAssignment has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Generator.appendRangeValidation (cognitive 22) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1464— Generator.appendRangeValidation has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (16 pts), if/else 5, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HttpCommandExecutor.execute (cognitive 22) java/src/org/openqa/selenium/remote/HttpCommandExecutor.java:212— HttpCommandExecutor.execute has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CddlParser._extract_types (cognitive 22) py/generate_bidi.py:1128— CddlParser._extract_types has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (21 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.
serialization._read_scalar (cognitive 22) py/selenium/webdriver/common/_bidi/serialization.py:432— serialization._read_scalar has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4, 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.
_BiDiEncoder.default (cognitive 22) py/selenium/webdriver/remote/websocket_connection.py:55— _BiDiEncoder.default has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (6 pts), boolean chains 3 (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.
get-text.appendTextFromNodeInComposedDom (cognitive 22) javascript/atoms/typescript/get-text.ts:274— get-text.appendTextFromNodeInComposedDom has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 2 (7 pts), ternaries 1 (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.
keyboard.editContent (cognitive 22) javascript/atoms/typescript/core/keyboard.ts:325— keyboard.editContent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, ternaries 3 (5 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.
escapeCss (cognitive 22) javascript/selenium-webdriver/lib/by.js:67— escapeCss has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, if/else 5 (9 pts), loops 1 (nesting depth added 4). 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.
extractVendor (cognitive 22) javascript/selenium-webdriver/project_bidi_schema.mjs:805— extractVendor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 5 (7 pts), boolean chains 2, other 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.
SelectElement.SelectByText (cognitive 21) dotnet/src/support/UI/SelectElement.cs:126— SelectElement.SelectByText has cognitive complexity 21 (threshold 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.
FirefoxDriverService.CommandLineArguments.get (cognitive 21) dotnet/src/webdriver/Firefox/FirefoxDriverService.cs:167— FirefoxDriverService.CommandLineArguments.get has cognitive complexity 21 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
StackTraceElement.StackTraceElement.ctor (cognitive 21) dotnet/src/webdriver/StackTraceElement.cs:46— StackTraceElement.StackTraceElement.ctor has cognitive complexity 21 (threshold 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.
RequestConverter.channelRead0 (cognitive 21) java/src/org/openqa/selenium/netty/server/RequestConverter.java:60— RequestConverter.channelRead0 has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 2 (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.
serialization._validate_outbound_scalar (cognitive 21) py/selenium/webdriver/common/_bidi/serialization.py:533— serialization._validate_outbound_scalar has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 2 (6 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.
api_request_context._cookie_matches (cognitive 21) py/selenium/webdriver/common/api_request_context.py:103— api_request_context._cookie_matches has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (10 pts) (nesting depth added 2). 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.
value.embeddedValue (cognitive 21) javascript/atoms/typescript/core/accessibility/value.ts:59— value.embeddedValue has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (5 pts), boolean chains 4 (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.
tree.collectChildren (cognitive 21) javascript/atoms/typescript/core/accessibility/tree.ts:179— tree.collectChildren has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 3, loops 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.
index.suite (cognitive 21) javascript/selenium-webdriver/testing/index.js:470— index.suite has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 7). 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 into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
appendVisibleTextLinesFromElementCommon_ (cognitive 21) javascript/atoms/dom.js:1049— appendVisibleTextLinesFromElementCommon_ has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 9, ternaries 1 (2 pts) (nesting depth added 5). Of this number, 20 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hoistInlineRecords (cognitive 21) javascript/selenium-webdriver/normalize_bidi_ast.mjs:233— hoistInlineRecords has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (8 pts), boolean chains 5, loops 2 (3 pts), ternaries 1 (3 pts), other 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.
projectRecord (cognitive 21) javascript/selenium-webdriver/project_bidi_schema.mjs:349— projectRecord has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 5, loops 1, other 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.
projectSchema::projectMessages (cognitive 21) javascript/selenium-webdriver/project_bidi_schema.mjs:716— projectSchema::projectMessages has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (5 pts), other 4 (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.
ModuleGenerator.main (cognitive 20) java/src/dev/selenium/tools/modules/ModuleGenerator.java:98— ModuleGenerator.main has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (12 pts), error handling 2 (3 pts), match/switch 1 (2 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 3). 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.
Generator.serializeExpr (cognitive 20) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2145— Generator.serializeExpr has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 2 (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.
Connection.handle (cognitive 20) java/src/org/openqa/selenium/devtools/Connection.java:262— Connection.handle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (8 pts), match/switch 2 (5 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.
V148Adapter.adaptImageResponse (cognitive 20) java/src/org/openqa/selenium/docker/client/V148Adapter.java:52— V148Adapter.adaptImageResponse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 2 (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.
NodeOptions.addDriverConfigs (cognitive 20) java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:393— NodeOptions.addDriverConfigs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 3 (4 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.
KubernetesSessionFactory.buildJobSpec (cognitive 20) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:560— KubernetesSessionFactory.buildJobSpec has cognitive complexity 20 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 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.
JsonOutput.writeEscaped (cognitive 20) java/src/org/openqa/selenium/json/JsonOutput.java:494— JsonOutput.writeEscaped has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (18 pts), error handling 1, 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.
RemoteWebDriver.execute (cognitive 20) java/src/org/openqa/selenium/remote/RemoteWebDriver.java:722— RemoteWebDriver.execute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 1 (4 pts), error handling 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventFiringDecorator.fireAfterEvents (cognitive 20) java/src/org/openqa/selenium/support/events/EventFiringDecorator.java:264— EventFiringDecorator.fireAfterEvents has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (15 pts), error handling 2, ternaries 2, boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
generate_bidi_protocol._imports (cognitive 20) py/generate_bidi_protocol.py:1083— generate_bidi_protocol._imports has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12, boolean chains 4, loops 1 (2 pts), 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.
RemoteConnection._request (cognitive 20) py/selenium/webdriver/remote/remote_connection.py:437— RemoteConnection._request has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (15 pts), error handling 1 (2 pts), ternaries 1 (2 pts), boolean chains 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.
locators.relativeMany (cognitive 20) javascript/atoms/typescript/core/locators.ts:501— locators.relativeMany has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, if/else 9, ternaries 2. Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 542, 549, 572, …). 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.
index.sendRequest (cognitive 20) javascript/selenium-webdriver/http/index.js:179— index.sendRequest has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 217, 278). 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.
selectByVisibleText (cognitive 20) javascript/selenium-webdriver/lib/select.js:260— selectByVisibleText has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectElement.EscapeQuotes (cognitive 19) dotnet/src/support/UI/SelectElement.cs:366— SelectElement.EscapeQuotes has cognitive complexity 19 (threshold 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.
V155Network.OnFetchRequestPaused (cognitive 19) dotnet/src/webdriver/DevTools/v155/V155Network.cs:312— V155Network.OnFetchRequestPaused has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
V156Network.OnFetchRequestPaused (cognitive 19) dotnet/src/webdriver/DevTools/v156/V156Network.cs:312— V156Network.OnFetchRequestPaused has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
V157Network.OnFetchRequestPaused (cognitive 19) dotnet/src/webdriver/DevTools/v157/V157Network.cs:312— V157Network.OnFetchRequestPaused has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DriverOptions.GenerateDesiredCapabilities (cognitive 19) dotnet/src/webdriver/DriverOptions.cs:413— DriverOptions.GenerateDesiredCapabilities has cognitive complexity 19 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
IniFileReader.IniFileReader.ctor (cognitive 19) dotnet/src/webdriver/Firefox/Internal/IniFileReader.cs:37— IniFileReader.IniFileReader.ctor has cognitive complexity 19 (threshold 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.
RedisBackedNewSessionQueue.getNextAvailable (cognitive 19) java/src/org/openqa/selenium/grid/sessionqueue/redis/RedisBackedNewSessionQueue.java:393— RedisBackedNewSessionQueue.getNextAvailable has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 1 (2 pts), loops 2 (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.
DefaultNetworkInterfaceProvider.<init> (cognitive 19) java/src/org/openqa/selenium/net/DefaultNetworkInterfaceProvider.java:44— DefaultNetworkInterfaceProvider.<init> has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 3 (5 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
3.send (cognitive 19) java/src/org/openqa/selenium/remote/http/jdk/JdkHttpClient.java:278— 3.send has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 7, ternaries 1 (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.
Bazel.execute (cognitive 19) rake_tasks/bazel.rb:14— Bazel.execute has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 1 (3 pts), loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
locators.xpathMany (cognitive 19) javascript/atoms/typescript/core/locators.ts:227— locators.xpathMany has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (4 pts), error handling 2, boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
normalize_bidi_ast.flattenGroupComposition (cognitive 19) javascript/selenium-webdriver/normalize_bidi_ast.mjs:448— normalize_bidi_ast.flattenGroupComposition has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, loops 2, ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to one function item inside it that branches (mergedFields). 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.
ChromiumOptions.BuildChromeOptionsDictionary (cognitive 18) dotnet/src/webdriver/Chromium/ChromiumOptions.cs:515— ChromiumOptions.BuildChromeOptionsDictionary has cognitive complexity 18 (threshold 15). 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.
DevToolsSession.ProcessMessage (cognitive 18) REDACTED:541— DevToolsSession.ProcessMessage has cognitive complexity 18 (threshold 15). Of this number, 13 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.
KubernetesOptions.getKubernetesSessionFactories (cognitive 18) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesOptions.java:76— KubernetesOptions.getKubernetesSessionFactories has cognitive complexity 18 (threshold 15). Drivers by points: loops 3 (7 pts), if/else 4 (6 pts), ternaries 4, error handling 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, 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.
Bootstrap.createExtendedClassLoader (cognitive 18) java/src/org/openqa/selenium/grid/Bootstrap.java:87— Bootstrap.createExtendedClassLoader has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 2 (4 pts), loops 2 (4 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.
NetworkUtils.getLocalInterfaceAddress (cognitive 18) java/src/org/openqa/selenium/net/NetworkUtils.java:183— NetworkUtils.getLocalInterfaceAddress has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 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.
W3CHttpCommandCodec.amendParameters (cognitive 18) java/src/org/openqa/selenium/remote/codec/w3c/W3CHttpCommandCodec.java:169— W3CHttpCommandCodec.amendParameters has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 2 (4 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.
EventFiringDecorator.parametersMatch (cognitive 18) java/src/org/openqa/selenium/support/events/EventFiringDecorator.java:335— EventFiringDecorator.parametersMatch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 1, 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.
Platform.extractFromSysProperty (cognitive 18) java/src/org/openqa/selenium/Platform.java:432— Platform.extractFromSysProperty has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CddlTypeDefinition.to_python_dataclass (cognitive 18) py/generate_bidi.py:434— CddlTypeDefinition.to_python_dataclass has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (5 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.
CdpConnection._reader_task (cognitive 18) py/private/cdp.py:444— CdpConnection._reader_task has cognitive complexity 18 (threshold 15). Drivers by points: error handling 3 (7 pts), loops 4 (7 pts), if/else 3 (4 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.
Record.__post_init__ (cognitive 18) py/selenium/webdriver/common/_bidi/serialization.py:238— Record.__post_init__ has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 1, 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.
Service.__init__ (cognitive 18) py/selenium/webdriver/firefox/service.py:39— Service.__init__ has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4 (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.
script.serialize_argument (cognitive 18) py/selenium/webdriver/remote/script.py:201— script.serialize_argument has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 1 (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.
device.bot.Device.resolveUrl_ (cognitive 18) REDACTED:752— device.bot.Device.resolveUrl_ has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6 (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.
events.bot.events.TouchEventFactory_.create (cognitive 18) javascript/atoms/events.js:431— events.bot.events.TouchEventFactory_.create has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 2, boolean chains 1, match/switch 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, 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.
locators.xpathSingle (cognitive 18) javascript/atoms/typescript/core/locators.ts:379— locators.xpathSingle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 2 (4 pts), error handling 2, 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.
normalize_bidi_ast.detectInlineVariant (cognitive 18) javascript/selenium-webdriver/normalize_bidi_ast.mjs:293— normalize_bidi_ast.detectInlineVariant has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 4, loops 1, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
unionSelector (cognitive 18) javascript/selenium-webdriver/project_bidi_schema.mjs:472— unionSelector has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (4 pts), boolean chains 1, other 1, ternaries 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 2 belong to 14 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Broker.ProcessMessagesAsync (cognitive 17) dotnet/src/webdriver/BiDi/Broker.cs:413— Broker.ProcessMessagesAsync has cognitive complexity 17 (threshold 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.
Generator.appendNestedSynthetics (cognitive 17) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1257— Generator.appendNestedSynthetics has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (6 pts), boolean chains 1, 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.
InfoCommand.readContent (cognitive 17) java/src/org/openqa/selenium/grid/commands/InfoCommand.java:144— InfoCommand.readContent 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.
JsonInput.readNumberLexeme (cognitive 17) java/src/org/openqa/selenium/json/JsonInput.java:322— JsonInput.readNumberLexeme has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3 (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.
SeleniumManager.getBinary (cognitive 17) java/src/org/openqa/selenium/manager/SeleniumManager.java:178— SeleniumManager.getBinary has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 1 (3 pts), boolean chains 2, error handling 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.
UrlChecker.waitUntilAvailable (cognitive 17) java/src/org/openqa/selenium/net/UrlChecker.java:57— UrlChecker.waitUntilAvailable has cognitive complexity 17 (threshold 15). Drivers by points: error handling 4 (6 pts), if/else 2 (6 pts), loops 2 (3 pts), ternaries 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.
EventFiringDecorator.fireBeforeEvents (cognitive 17) java/src/org/openqa/selenium/support/events/EventFiringDecorator.java:214— EventFiringDecorator.fireBeforeEvents has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), error handling 2, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
CddlParser._extract_commands (cognitive 17) py/generate_bidi.py:1351— CddlParser._extract_commands has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 2 (4 pts) (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.
Record.as_json (cognitive 17) py/selenium/webdriver/common/_bidi/serialization.py:277— Record.as_json has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 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.
gen_file.write_atom_literal (cognitive 17) javascript/private/gen_file.py:28— gen_file.write_atom_literal has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (2 pts) (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.
device.bot.Device.clickElement (cognitive 17) REDACTED:385— device.bot.Device.clickElement has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 3). 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.
inject.wrapValue::wrap (cognitive 17) javascript/atoms/typescript/core/inject.ts:132— inject.wrapValue::wrap has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
record.checkBounds (cognitive 17) javascript/selenium-webdriver/bidi/serialization/record.js:22— record.checkBounds has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 5 (7 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.
Driver.createSession (cognitive 17) javascript/selenium-webdriver/chromium.js:619— Driver.createSession has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 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.
isShown::displayed (cognitive 17) javascript/atoms/dom.js:600— isShown::displayed has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 8 (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.
getSize (cognitive 17) javascript/atoms/window.js:221— getSize has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (6 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.
buildVendorModules (cognitive 17) javascript/selenium-webdriver/generate_bidi.mjs:661— buildVendorModules has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), other 6, loops 3 (4 pts), boolean chains 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 664, 662, 665, …). 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.
projectType (cognitive 17) javascript/selenium-webdriver/project_bidi_schema.mjs:313— projectType has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (6 pts), boolean chains 2, other 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.
WebDriver.StartSession (cognitive 16) dotnet/src/webdriver/WebDriver.cs:664— WebDriver.StartSession has cognitive complexity 16 (threshold 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.
RedisBackedGridModel.reconcileSlots (cognitive 16) java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:488— RedisBackedGridModel.reconcileSlots has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 1 (3 pts), 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.
KubernetesSessionFactory.buildJobSpecFromTemplate (cognitive 16) java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:867— KubernetesSessionFactory.buildJobSpecFromTemplate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4 (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.
LocalNode.stopTimedOutSession (cognitive 16) java/src/org/openqa/selenium/grid/node/local/LocalNode.java:350— LocalNode.stopTimedOutSession has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_script_handlers.execute_pinned (cognitive 16) py/private/_script_handlers.py:275— _script_handlers.execute_pinned has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 3 (5 pts), boolean chains 3, error handling 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.
api_request_context._parse_set_cookie (cognitive 16) py/selenium/webdriver/common/api_request_context.py:160— api_request_context._parse_set_cookie has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), error handling 2 (6 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.
GridManager::request_driver_version (cognitive 16) rust/src/grid.rs:105— GridManager::request_driver_version has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, match/switch 1 (nesting depth added 6). 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.
accname.nativeName (cognitive 16) javascript/atoms/typescript/core/accessibility/accname.ts:420— accname.nativeName has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), boolean chains 7, match/switch 1 (nesting depth added 4). 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.
inject.bot.inject.executeAsyncScript (cognitive 16) javascript/atoms/inject.js:324— inject.bot.inject.executeAsyncScript has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 3). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (sendResponse). 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.
LocalValue.getArgument (cognitive 16) javascript/selenium-webdriver/bidi/protocolValue.js:192— LocalValue.getArgument has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 4). Of this number, 12 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.
normalize_bidi_ast.eachPropertyDeep (cognitive 16) javascript/selenium-webdriver/normalize_bidi_ast.mjs:158— normalize_bidi_ast.eachPropertyDeep has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (3 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.
move (cognitive 16) javascript/atoms/mouse.js:352— move has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 3, ternaries 1 (3 pts), error handling 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.
checkCompleteness (cognitive 16) javascript/selenium-webdriver/project_bidi_schema.mjs:1122— checkCompleteness has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 3, loops 2, ternaries 1 (2 pts), other 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.
Near-duplicate member pair (53 shared lines) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:161— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:161-302 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:317-510 — These two members are variants of one another: 53 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (45 shared lines) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:106— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:106-161 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:121-176 — These two members are variants of one another: 45 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:250— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:250-292 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:295-341 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (113 corresponding lines) · ×1
Edited copy of a member (113 corresponding lines) java/src/org/openqa/selenium/grid/commands/Hub.java:109— java/src/org/openqa/selenium/grid/commands/Hub.java:109-221 | java/src/org/openqa/selenium/grid/commands/Standalone.java:117-229 — These two members are one piece of code written twice and then edited apart: 113 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (92 corresponding lines) · ×1
Edited copy of a member (92 corresponding lines) java/src/org/openqa/selenium/docker/client/V148Adapter.java:110— java/src/org/openqa/selenium/docker/client/V148Adapter.java:110-201 | java/src/org/openqa/selenium/docker/client/V148Adapter.java:204-301 — These two members are one piece of code written twice and then edited apart: 92 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:84— java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:84-157 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:185-244 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (52 corresponding lines) · ×1
Edited copy of a member (52 corresponding lines) java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:121— java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:121-172 | java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java:175-234 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:309— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:309-356 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:372-430 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java:350— java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java:350-391 | java/src/org/openqa/selenium/grid/node/local/LocalNode.java:1105-1148 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) java/src/org/openqa/selenium/chrome/ChromeDriverService.java:297— java/src/org/openqa/selenium/chrome/ChromeDriverService.java:297-331 | java/src/org/openqa/selenium/edge/EdgeDriverService.java:298-338 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 38+ corresponding lines) · ×1
Edited copies of one member (3 members, 38+ corresponding lines) java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:50— java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:50-87 | java/src/org/openqa/selenium/grid/sessionmap/config/SessionMapOptions.java:40-82 | java/src/org/openqa/selenium/grid/sessionqueue/config/NewSessionQueueOptions.java:51-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 38 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) java/src/org/openqa/selenium/devtools/v155/v155Events.java:77— java/src/org/openqa/selenium/devtools/v155/v155Events.java:77-108 | java/src/org/openqa/selenium/devtools/v156/v156Events.java:77-108 | java/src/org/openqa/selenium/devtools/v157/v157Events.java:77-108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 49+ corresponding lines) · ×1
Edited copies of one member (4 members, 49+ corresponding lines) java/src/org/openqa/selenium/bidi/log/ConsoleLogEntry.java:60— java/src/org/openqa/selenium/bidi/log/ConsoleLogEntry.java:60-122 | java/src/org/openqa/selenium/bidi/log/GenericLogEntry.java:49-99 | java/src/org/openqa/selenium/bidi/log/JavascriptLogEntry.java:43-93 | java/src/org/openqa/selenium/bidi/network/BaseParameters.java:65-113 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 49 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) java/src/org/openqa/selenium/grid/distributor/httpd/DistributorServer.java:91— java/src/org/openqa/selenium/grid/distributor/httpd/DistributorServer.java:91-137 | java/src/org/openqa/selenium/grid/sessionqueue/httpd/NewSessionQueueServer.java:88-147 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 45+ corresponding lines) · ×1
Edited copies of one member (3 members, 45+ corresponding lines) java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:95— java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:95-151 | java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java:40-84 | java/src/org/openqa/selenium/bidi/script/RealmInfo.java:38-91 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 45 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:433— java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:433-480 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:607-643 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 43+ corresponding lines) · ×1
Edited copies of one member (3 members, 43+ corresponding lines) java/src/org/openqa/selenium/grid/data/SessionClosedData.java:143— java/src/org/openqa/selenium/grid/data/SessionClosedData.java:143-193 | java/src/org/openqa/selenium/grid/data/SessionCreatedData.java:108-150 | java/src/org/openqa/selenium/grid/data/SessionEventData.java:220-262 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) java/src/org/openqa/selenium/devtools/idealized/target/model/TargetInfo.java:87— java/src/org/openqa/selenium/devtools/idealized/target/model/TargetInfo.java:87-126 | java/src/org/openqa/selenium/grid/data/SessionRequest.java:168-211 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) java/src/org/openqa/selenium/grid/data/DefaultSlotMatcher.java:157— java/src/org/openqa/selenium/grid/data/DefaultSlotMatcher.java:157-183 | java/src/org/openqa/selenium/grid/node/relay/RelaySessionFactory.java:108-139 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 34+ corresponding lines) · ×1
Edited copies of one member (3 members, 34+ corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:249— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:249-282 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1414-1453 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1465-1503 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) REDACTED:57— REDACTED:57-98 | REDACTED:101-138 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) java/src/org/openqa/selenium/json/InstanceCoercer.java:267— java/src/org/openqa/selenium/json/InstanceCoercer.java:267-291 | java/src/org/openqa/selenium/json/SimplePropertyDescriptor.java:149-180 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 32+ corresponding lines) · ×1
Edited copies of one member (4 members, 32+ corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:438— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:438-469 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:523-554 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1048-1083 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1092-1127 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) dotnet/src/support/Events/EventFiringWebDriver.cs:376— dotnet/src/support/Events/EventFiringWebDriver.cs:376-398 | dotnet/src/support/Events/EventFiringWebDriver.cs:1691-1713 | dotnet/src/support/Events/EventFiringWebDriver.cs:1824-1846 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) java/src/org/openqa/selenium/grid/data/NewSessionResponse.java:64— java/src/org/openqa/selenium/grid/data/NewSessionResponse.java:64-92 | java/src/org/openqa/selenium/grid/data/Slot.java:48-82 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 30+ corresponding lines) · ×1
Edited copies of one member (3 members, 30+ corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:398— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:398-427 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:480-511 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:954-985 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 26+ corresponding lines) · ×1
Edited copies of one member (3 members, 26+ corresponding lines) py/selenium/webdriver/firefox/webdriver.py:44— py/selenium/webdriver/firefox/webdriver.py:44-72 | py/selenium/webdriver/ie/webdriver.py:35-60 | py/selenium/webdriver/safari/webdriver.py:35-60 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) java/src/org/openqa/selenium/bidi/browsingcontext/NavigationResult.java:45— java/src/org/openqa/selenium/bidi/browsingcontext/NavigationResult.java:45-69 | java/src/org/openqa/selenium/bidi/script/RegExpValue.java:43-67 | java/src/org/openqa/selenium/bidi/storage/PartitionKey.java:34-58 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 16+ corresponding lines) · ×1
Edited copies of one member (8 members, 16+ corresponding lines) rust/src/chrome.rs:87— rust/src/chrome.rs:87-104 | rust/src/edge.rs:93-109 | rust/src/electron.rs:95-111 | rust/src/firefox.rs:88-103 | rust/src/grid.rs:56-73 | rust/src/iexplorer.rs:64-81 | rust/src/safari.rs:49-64 | rust/src/safaritp.rs:55-70 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 24+ corresponding lines) · ×1
Edited copies of one member (3 members, 24+ corresponding lines) dotnet/src/support/Events/EventFiringWebDriver.cs:477— dotnet/src/support/Events/EventFiringWebDriver.cs:477-500 | dotnet/src/support/Events/EventFiringWebDriver.cs:540-565 | dotnet/src/support/Events/EventFiringWebDriver.cs:574-597 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1138— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1138-1156 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1167-1185 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1195-1215 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 17+ corresponding lines) · ×1
Edited copies of one member (7 members, 17+ corresponding lines) java/src/org/openqa/selenium/grid/commands/EventBusCommand.java:169— java/src/org/openqa/selenium/grid/commands/EventBusCommand.java:169-190 | java/src/org/openqa/selenium/grid/commands/Hub.java:224-240 | java/src/org/openqa/selenium/grid/commands/Standalone.java:232-250 | java/src/org/openqa/selenium/grid/distributor/httpd/DistributorServer.java:140-160 | java/src/org/openqa/selenium/grid/node/httpd/NodeServer.java:263-284 | java/src/org/openqa/selenium/grid/router/httpd/RouterServer.java:229-245 | java/src/org/openqa/selenium/grid/sessionqueue/httpd/NewSessionQueueServer.java:150-171 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1280— java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1280-1289 | java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1298-1306 | java/src/org/openqa/selenium/remote/RemoteWebElement.java:308-314 | java/src/org/openqa/selenium/remote/RemoteWebElement.java:318-324 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) java/src/org/openqa/selenium/interactions/Actions.java:486— java/src/org/openqa/selenium/interactions/Actions.java:486-500 | java/src/org/openqa/selenium/interactions/Actions.java:502-516 | java/src/org/openqa/selenium/interactions/Actions.java:518-532 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) dotnet/src/support/UI/SelectElement.cs:204— dotnet/src/support/UI/SelectElement.cs:204-226 | dotnet/src/support/UI/SelectElement.cs:280-301 | dotnet/src/support/UI/SelectElement.cs:316-337 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) py/selenium/webdriver/support/select.py:160— py/selenium/webdriver/support/select.py:160-182 | py/selenium/webdriver/support/select.py:202-223 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 16+ corresponding lines) · ×1
Edited copies of one member (4 members, 16+ corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:81— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:81-97 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:105-120 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:128-143 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1312-1330 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1226— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1226-1243 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1254-1271 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:1282-1300 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 14+ corresponding lines) · ×1
Edited copies of one member (6 members, 14+ corresponding lines) dotnet/src/support/Events/EventFiringWebDriver.cs:830— dotnet/src/support/Events/EventFiringWebDriver.cs:830-844 | dotnet/src/support/Events/EventFiringWebDriver.cs:862-875 | dotnet/src/support/Events/EventFiringWebDriver.cs:895-913 | dotnet/src/support/Events/EventFiringWebDriver.cs:1479-1492 | dotnet/src/support/Events/EventFiringWebDriver.cs:1499-1512 | dotnet/src/support/Events/EventFiringWebDriver.cs:1540-1553 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 6+ corresponding lines) · ×1
Edited copies of one member (5 members, 6+ corresponding lines) java/src/org/openqa/selenium/chrome/ChromeDriver.java:125— java/src/org/openqa/selenium/chrome/ChromeDriver.java:125-130 | java/src/org/openqa/selenium/chromium/ChromiumDriverCommandExecutor.java:52-60 | java/src/org/openqa/selenium/edge/EdgeDriver.java:97-102 | java/src/org/openqa/selenium/firefox/FirefoxDriver.java:249-256 | java/src/org/openqa/selenium/safari/SafariDriver.java:139-145 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1240— java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1240-1245 | java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1254-1259 | java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1268-1273 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) py/selenium/webdriver/firefox/webdriver.py:170— py/selenium/webdriver/firefox/webdriver.py:170-196 | py/selenium/webdriver/remote/webdriver.py:1056-1082 | REDACTED:459-487 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) java/src/org/openqa/selenium/grid/distributor/remote/RemoteDistributor.java:86— java/src/org/openqa/selenium/grid/distributor/remote/RemoteDistributor.java:86-95 | java/src/org/openqa/selenium/grid/node/remote/RemoteNode.java:199-208 | java/src/org/openqa/selenium/grid/node/remote/RemoteNode.java:211-220 | java/src/org/openqa/selenium/grid/node/remote/RemoteNode.java:235-244 | java/src/org/openqa/selenium/grid/sessionqueue/remote/RemoteNewSessionQueue.java:114-125 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 8+ corresponding lines) · ×1
Edited copies of one member (6 members, 8+ corresponding lines) java/src/org/openqa/selenium/bidi/network/Cookie.java:48— java/src/org/openqa/selenium/bidi/network/Cookie.java:48-55 | java/src/org/openqa/selenium/bidi/permissions/PermissionState.java:44-51 | java/src/org/openqa/selenium/bidi/script/NodeProperties.java:45-52 | java/src/org/openqa/selenium/bidi/script/PrimitiveType.java:42-49 | java/src/org/openqa/selenium/bidi/script/RealmType.java:44-51 | java/src/org/openqa/selenium/bidi/speculation/PreloadingStatus.java:40-47 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (2 corresponding lines) · ×1
Edited copy of a member (2 corresponding lines) py/selenium/webdriver/chrome/service.py:62— py/selenium/webdriver/chrome/service.py:62-63 | py/selenium/webdriver/edge/service.py:62-63 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 3+ corresponding lines) · ×1
Edited copies of one member (5 members, 3+ corresponding lines) rb/lib/selenium/webdriver/chrome/driver.rb:34— rb/lib/selenium/webdriver/chrome/driver.rb:34-36 | rb/lib/selenium/webdriver/edge/driver.rb:34-36 | rb/lib/selenium/webdriver/firefox/driver.rb:37-39 | rb/lib/selenium/webdriver/ie/driver.rb:35-37 | rb/lib/selenium/webdriver/safari/driver.rb:35-37 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (1 corresponding lines) · ×1
Edited copy of a member (1 corresponding lines) REDACTED:79— REDACTED:79-79 | py/selenium/webdriver/support/wait.py:76-76 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (114–129 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:293— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:293-421 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:351-464 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (58–63 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:606— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:606-668 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:660-717 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (50 lines × 3) dotnet/src/webdriver/DevTools/v155/V155Network.cs:314— dotnet/src/webdriver/DevTools/v155/V155Network.cs:314-363 | dotnet/src/webdriver/DevTools/v156/V156Network.cs:314-363 | dotnet/src/webdriver/DevTools/v157/V157Network.cs:314-363 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155Network.cs` and `dotnet/src/webdriver/DevTools/v156/V156Network.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (44–48 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:536— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:536-583 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:597-640 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (37–43 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:202— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:202-244 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:272-308 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (42 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Network.java:127— java/src/org/openqa/selenium/devtools/v155/v155Network.java:127-168 | java/src/org/openqa/selenium/devtools/v156/v156Network.java:127-168 | java/src/org/openqa/selenium/devtools/v157/v157Network.java:127-168 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Network.java` and `java/src/org/openqa/selenium/devtools/v156/v156Network.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Fetch` names `org.openqa.selenium.devtools.v155.fetch.Fetch` in one and `org.openqa.selenium.devtools.v156.fetch.Fetch` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (33 lines × 3) dotnet/src/webdriver/DevTools/v155/V155Network.cs:175— dotnet/src/webdriver/DevTools/v155/V155Network.cs:175-207 | dotnet/src/webdriver/DevTools/v156/V156Network.cs:175-207 | dotnet/src/webdriver/DevTools/v157/V157Network.cs:175-207 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155Network.cs` and `dotnet/src/webdriver/DevTools/v156/V156Network.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (31 lines × 2) java/src/org/openqa/selenium/grid/commands/Hub.java:137— java/src/org/openqa/selenium/grid/commands/Hub.java:137-167 | java/src/org/openqa/selenium/grid/commands/Standalone.java:145-175 — before extracting anything, compare `java/src/org/openqa/selenium/grid/commands/Hub.java` and `java/src/org/openqa/selenium/grid/commands/Standalone.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/grid/commands/Standalone.java:142` calls `LocalSessionMap`, `addHandler` and `java/src/org/openqa/selenium/grid/commands/Hub.java:135` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (30 lines × 2) dotnet/src/webdriver/Chromium/ChromiumDriver.cs:159— dotnet/src/webdriver/Chromium/ChromiumDriver.cs:159-188 | dotnet/src/webdriver/Firefox/FirefoxDriver.cs:205-234 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/webdriver/Chromium/ChromiumDriver.cs:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28–30 lines × 2) java/src/org/openqa/selenium/docker/client/V148Adapter.java:160— java/src/org/openqa/selenium/docker/client/V148Adapter.java:160-189 | java/src/org/openqa/selenium/docker/client/V148Adapter.java:247-274 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/docker/client/V148Adapter.java:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 3) dotnet/src/webdriver/DevTools/v155/V155Network.cs:138— dotnet/src/webdriver/DevTools/v155/V155Network.cs:138-164 | dotnet/src/webdriver/DevTools/v156/V156Network.cs:138-164 | dotnet/src/webdriver/DevTools/v157/V157Network.cs:138-164 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155Network.cs` and `dotnet/src/webdriver/DevTools/v156/V156Network.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (28 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Events.java:81— java/src/org/openqa/selenium/devtools/v155/v155Events.java:81-108 | java/src/org/openqa/selenium/devtools/v156/v156Events.java:81-108 | java/src/org/openqa/selenium/devtools/v157/v157Events.java:81-108 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Events.java` and `java/src/org/openqa/selenium/devtools/v156/v156Events.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/devtools/v155/v155Events.java:81` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `ExceptionThrown` names `org.openqa.selenium.devtools.v155.runtime.model.ExceptionThrown` in one and `org.openqa.selenium.devtools.v156.runtime.model.ExceptionThrown` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (19–28 lines × 2) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2171— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2171-2198 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2204-2222 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/BiDiGenerator.java:2171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (27 lines × 2) dotnet/src/webdriver/IE/InternetExplorerDriver.cs:165— dotnet/src/webdriver/IE/InternetExplorerDriver.cs:165-191 | dotnet/src/webdriver/Safari/SafariDriver.cs:170-196 — before extracting anything, compare `dotnet/src/webdriver/IE/InternetExplorerDriver.cs` and `dotnet/src/webdriver/Safari/SafariDriver.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/webdriver/IE/InternetExplorerDriver.cs:165` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–27 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:165— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:165-191 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:231-251 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:165` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 3) java/src/org/openqa/selenium/bidi/log/ConsoleLogEntry.java:68— java/src/org/openqa/selenium/bidi/log/ConsoleLogEntry.java:68-93 | java/src/org/openqa/selenium/bidi/log/GenericLogEntry.java:55-80 | java/src/org/openqa/selenium/bidi/log/JavascriptLogEntry.java:49-74 — before extracting anything, compare `java/src/org/openqa/selenium/bidi/log/GenericLogEntry.java` and `java/src/org/openqa/selenium/bidi/log/JavascriptLogEntry.java` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/log/ConsoleLogEntry.java:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (26 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:331— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:331-356 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:405-430 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:331` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:329` calls `size`, `forEach` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:404` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (24–26 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:491— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:491-516 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:551-574 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22–25 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:137— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:137-161 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:155-176 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:137` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:152` calls `reconstructLocalNodesFromRedis` and `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:134` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23 lines × 3) dotnet/src/webdriver/DevTools/v155/V155Target.cs:55— dotnet/src/webdriver/DevTools/v155/V155Target.cs:55-77 | dotnet/src/webdriver/DevTools/v156/V156Target.cs:55-77 | dotnet/src/webdriver/DevTools/v157/V157Target.cs:55-77 — before extracting anything, compare `dotnet/src/webdriver/DevTools/v155/V155Target.cs` and `dotnet/src/webdriver/DevTools/v156/V156Target.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23–24 lines × 2) dotnet/src/webdriver/Chromium/ChromiumDriverService.cs:201— dotnet/src/webdriver/Chromium/ChromiumDriverService.cs:201-224 | dotnet/src/webdriver/Firefox/FirefoxDriverService.cs:383-405 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/webdriver/Chromium/ChromiumDriverService.cs:201` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25 lines × 2) java/src/org/openqa/selenium/chrome/ChromeDriverService.java:298— java/src/org/openqa/selenium/chrome/ChromeDriverService.java:298-322 | java/src/org/openqa/selenium/edge/EdgeDriverService.java:299-323 — before extracting anything, compare `java/src/org/openqa/selenium/chrome/ChromeDriverService.java` and `java/src/org/openqa/selenium/edge/EdgeDriverService.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/chrome/ChromeDriverService.java:324` calls `add`, `format` and `java/src/org/openqa/selenium/edge/EdgeDriverService.java:324` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22 lines × 3) java/src/org/openqa/selenium/grid/commands/Hub.java:185— java/src/org/openqa/selenium/grid/commands/Hub.java:185-206 | java/src/org/openqa/selenium/grid/commands/Standalone.java:193-214 | java/src/org/openqa/selenium/grid/router/httpd/RouterServer.java:157-178 — before extracting anything, compare `java/src/org/openqa/selenium/grid/commands/Hub.java` and `java/src/org/openqa/selenium/grid/commands/Standalone.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/grid/router/httpd/RouterServer.java:154` calls `Router`, `with`, `getSpecComplianceChecks` and `java/src/org/openqa/selenium/grid/commands/Hub.java:183` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19–21 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:248— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:248-268 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:312-330 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18–21 lines × 2) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:550— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:550-567 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:362-382 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java` and `java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18–19 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:329— java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:329-346 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:419-437 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16–18 lines × 3) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:566— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:566-583 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:631-647 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:663-678 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:566` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–17 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:587— java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:587-603 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java:643-657 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12–17 lines × 2) java/src/org/openqa/selenium/grid/router/GridStatusHandler.java:87— java/src/org/openqa/selenium/grid/router/GridStatusHandler.java:87-98 | java/src/org/openqa/selenium/grid/router/GridStatusHandler.java:107-123 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/router/GridStatusHandler.java:107` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–16 lines × 3) java/src/org/openqa/selenium/grid/commands/Hub.java:225— java/src/org/openqa/selenium/grid/commands/Hub.java:225-237 | java/src/org/openqa/selenium/grid/commands/Standalone.java:233-248 | java/src/org/openqa/selenium/grid/router/httpd/RouterServer.java:230-242 — before extracting anything, compare `java/src/org/openqa/selenium/grid/commands/Hub.java` and `java/src/org/openqa/selenium/grid/commands/Standalone.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/commands/Standalone.java:233` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–16 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:292— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:292-306 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:354-369 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 4) java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java:52— java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java:52-66 | java/src/org/openqa/selenium/bidi/log/ConsoleLogEntry.java:79-93 | java/src/org/openqa/selenium/bidi/log/GenericLogEntry.java:66-80 | java/src/org/openqa/selenium/bidi/log/JavascriptLogEntry.java:60-74 — before extracting anything, compare `java/src/org/openqa/selenium/bidi/log/GenericLogEntry.java` and `java/src/org/openqa/selenium/bidi/log/JavascriptLogEntry.java` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 3) java/src/org/openqa/selenium/json/UriCoercer.java:34— java/src/org/openqa/selenium/json/UriCoercer.java:34-48 | java/src/org/openqa/selenium/json/UrlCoercer.java:34-48 | java/src/org/openqa/selenium/json/UuidCoercer.java:33-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/json/UriCoercer.java:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–15 lines × 2) java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:411— java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:411-423 | java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:493-507 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/support/ui/ExpectedConditions.java:411` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–14 lines × 4) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:536— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:536-543 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:673-686 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1755-1763 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1917-1924 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–14 lines × 3) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:256— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:256-267 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:307-318 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:451-464 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/BiDiGenerator.java:256` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `java/src/org/openqa/selenium/bidi/BiDiGenerator.java:305` calls `seedRef`, `mapField` and `java/src/org/openqa/selenium/bidi/BiDiGenerator.java:255` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–14 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:440— java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:440-453 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedGridModel.java:611-623 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10–14 lines × 2) java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:323— java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java:323-332 | java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java:145-158 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/ProxyNodeWebsockets.java` and `java/src/org/openqa/selenium/grid/router/ProxyWebsocketsIntoGrid.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11–13 lines × 2) java/src/org/openqa/selenium/bidi/Connection.java:129— java/src/org/openqa/selenium/bidi/Connection.java:129-141 | java/src/org/openqa/selenium/devtools/Connection.java:160-170 — `java/src/org/openqa/selenium/bidi/Connection.java` and `java/src/org/openqa/selenium/devtools/Connection.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 38 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/Connection.java:129` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 4) java/src/org/openqa/selenium/bidi/module/Script.java:255— java/src/org/openqa/selenium/bidi/module/Script.java:255-266 | java/src/org/openqa/selenium/bidi/module/Script.java:271-282 | java/src/org/openqa/selenium/bidi/module/Script.java:288-299 | java/src/org/openqa/selenium/bidi/module/Script.java:306-317 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/module/Script.java:255` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–12 lines × 3) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:540— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:540-548 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:689-700 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1765-1773 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6–12 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:89— java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:89-100 | java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:163-168 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/distributor/local/LocalGridModel.java:89` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–12 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:360— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:360-371 | java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java:434-443 — before extracting anything, compare `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java` and `java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedNodeRegistry.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 374 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 6) java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:102— java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:102-112 | java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java:45-55 | java/src/org/openqa/selenium/bidi/browsingcontext/NavigationInfo.java:48-58 | java/src/org/openqa/selenium/bidi/browsingcontext/NavigationResult.java:47-57 | java/src/org/openqa/selenium/bidi/script/RegExpValue.java:45-55 | java/src/org/openqa/selenium/bidi/storage/PartitionKey.java:36-46 — before extracting anything, compare `java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java` and `java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–11 lines × 4) java/src/org/openqa/selenium/docker/client/V140Adapter.java:66— java/src/org/openqa/selenium/docker/client/V140Adapter.java:66-75 | java/src/org/openqa/selenium/docker/client/V144Adapter.java:77-86 | java/src/org/openqa/selenium/docker/client/V144Adapter.java:106-116 | java/src/org/openqa/selenium/docker/client/V148Adapter.java:111-120 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/docker/client/V140Adapter.java:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–11 lines × 2) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:901— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:901-911 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1215-1222 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/BiDiGenerator.java:901` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5–11 lines × 2) java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1709— java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1709-1719 | java/src/org/openqa/selenium/bidi/BiDiGenerator.java:1723-1727 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–11 lines × 2) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:273— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:273-283 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:481-489 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:273` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 2) java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:175— java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:175-185 | java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:278-287 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/sessionmap/jdbc/JdbcBackedSessionMap.java:175` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 5) java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:104— java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:104-115 | java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java:47-58 | java/src/org/openqa/selenium/bidi/browsingcontext/NavigationInfo.java:50-61 | java/src/org/openqa/selenium/bidi/network/RequestData.java:79-88 | java/src/org/openqa/selenium/bidi/network/ResponseData.java:88-97 — before extracting anything, compare `java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java` and `java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:116` calls `read` and `java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java:59` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 8) java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:104— java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:104-113 | java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java:47-56 | java/src/org/openqa/selenium/bidi/browsingcontext/NavigationInfo.java:50-59 | java/src/org/openqa/selenium/bidi/browsingcontext/NavigationResult.java:49-58 | java/src/org/openqa/selenium/bidi/network/RequestData.java:79-87 | java/src/org/openqa/selenium/bidi/network/ResponseData.java:88-96 | java/src/org/openqa/selenium/bidi/script/RegExpValue.java:47-56 | java/src/org/openqa/selenium/bidi/storage/PartitionKey.java:38-47 — before extracting anything, compare `java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java` and `java/src/org/openqa/selenium/bidi/browsingcontext/DownloadInfo.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/bidi/browsingcontext/BrowsingContextInfo.java:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8–9 lines × 2) java/src/org/openqa/selenium/firefox/FirefoxOptions.java:517— java/src/org/openqa/selenium/firefox/FirefoxOptions.java:517-525 | java/src/org/openqa/selenium/firefox/FirefoxOptions.java:584-591 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–10 lines × 2) java/src/org/openqa/selenium/grid/sessionmap/local/LocalSessionMap.java:110— java/src/org/openqa/selenium/grid/sessionmap/local/LocalSessionMap.java:110-117 | java/src/org/openqa/selenium/grid/sessionmap/local/LocalSessionMap.java:161-170 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/sessionmap/local/LocalSessionMap.java:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 5) java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:209— java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:209-216 | java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:240-247 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:359-366 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:421-428 | java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java:454-461 — before extracting anything, compare `java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java` and `java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Events.java:65— java/src/org/openqa/selenium/devtools/v155/v155Events.java:65-74 | java/src/org/openqa/selenium/devtools/v156/v156Events.java:65-74 | java/src/org/openqa/selenium/devtools/v157/v157Events.java:65-74 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Events.java` and `java/src/org/openqa/selenium/devtools/v156/v156Events.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `ConsoleAPICalled` names `org.openqa.selenium.devtools.v155.runtime.model.ConsoleAPICalled` in one and `org.openqa.selenium.devtools.v156.runtime.model.ConsoleAPICalled` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6–7 lines × 2) java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:535— java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:535-540 | java/src/org/openqa/selenium/grid/graphql/Grid.java:115-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java/src/org/openqa/selenium/grid/distributor/local/LocalNodeRegistry.java:535` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 3) java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1241— java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1241-1245 | java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1255-1259 | java/src/org/openqa/selenium/remote/RemoteWebDriver.java:1269-1273 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (35 lines × 2) java/src/org/openqa/selenium/chrome/ChromeDriverService.java:260— java/src/org/openqa/selenium/chrome/ChromeDriverService.java:260-294 | java/src/org/openqa/selenium/edge/EdgeDriverService.java:261-295 — before extracting anything, compare `java/src/org/openqa/selenium/chrome/ChromeDriverService.java` and `java/src/org/openqa/selenium/edge/EdgeDriverService.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (31 lines × 9) dotnet/src/webdriver/BiDi/Browser/ClientWindow.cs:31— dotnet/src/webdriver/BiDi/Browser/ClientWindow.cs:31-61 | dotnet/src/webdriver/BiDi/Browser/UserContext.cs:31-61 | dotnet/src/webdriver/BiDi/BrowsingContext/Download.cs:31-61 | dotnet/src/webdriver/BiDi/BrowsingContext/Navigation.cs:31-61 | dotnet/src/webdriver/BiDi/BrowsingContext/Screencast.cs:31-66 | dotnet/src/webdriver/BiDi/Network/Collector.cs:31-61 | dotnet/src/webdriver/BiDi/Network/Intercept.cs:31-61 | dotnet/src/webdriver/BiDi/Network/Request.cs:31-61 | dotnet/src/webdriver/BiDi/Session/Subscription.cs:31-61 — before extracting anything, compare `dotnet/src/webdriver/BiDi/Browser/ClientWindow.cs` and `dotnet/src/webdriver/BiDi/Browser/UserContext.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/webdriver/BiDi/Browser/ClientWindow.cs:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 6) dotnet/src/webdriver/BiDi/Script/Channel.cs:36— dotnet/src/webdriver/BiDi/Script/Channel.cs:36-59 | dotnet/src/webdriver/BiDi/Script/Handle.cs:36-59 | dotnet/src/webdriver/BiDi/Script/InternalId.cs:36-59 | dotnet/src/webdriver/BiDi/Script/PreloadScript.cs:36-59 | dotnet/src/webdriver/BiDi/Script/Realm.cs:36-59 | dotnet/src/webdriver/BiDi/WebExtension/Extension.cs:36-59 — before extracting anything, compare `dotnet/src/webdriver/BiDi/Script/Channel.cs` and `dotnet/src/webdriver/BiDi/Script/Handle.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `dotnet/src/webdriver/BiDi/Script/Channel.cs:36` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (36 lines × 3) dotnet/src/webdriver/DevTools/v155/V155Log.cs:43— dotnet/src/webdriver/DevTools/v155/V155Log.cs:43-78 | dotnet/src/webdriver/DevTools/v156/V156Log.cs:43-78 | dotnet/src/webdriver/DevTools/v157/V157Log.cs:43-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (54 lines × 3) java/src/org/openqa/selenium/devtools/v155/v155Javascript.java:32— java/src/org/openqa/selenium/devtools/v155/v155Javascript.java:32-85 | java/src/org/openqa/selenium/devtools/v156/v156Javascript.java:32-85 | java/src/org/openqa/selenium/devtools/v157/v157Javascript.java:32-85 — before extracting anything, compare `java/src/org/openqa/selenium/devtools/v155/v155Javascript.java` and `java/src/org/openqa/selenium/devtools/v156/v156Javascript.java` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `BindingCalled` names `org.openqa.selenium.devtools.v155.runtime.model.BindingCalled` in one and `org.openqa.selenium.devtools.v156.runtime.model.BindingCalled` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 4) dotnet/src/webdriver/Chromium/ChromiumDriver.cs:141— dotnet/src/webdriver/Chromium/ChromiumDriver.cs:141-145 | dotnet/src/webdriver/Firefox/FirefoxDriver.cs:194-198 | dotnet/src/webdriver/IE/InternetExplorerDriver.cs:154-158 | dotnet/src/webdriver/Safari/SafariDriver.cs:159-163 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `dotnet/src/webdriver/Firefox/FirefoxDriver.cs:190` calls `AddCustomFirefoxCommands` and `dotnet/src/webdriver/IE/InternetExplorerDriver.cs:150` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 8) java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:89— java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:89-98 | java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:100-109 | java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:189-195 | java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:201-207 | java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:213-219 | java/src/org/openqa/selenium/grid/node/config/NodeOptions.java:286-292 | java/src/org/openqa/selenium/grid/sessionqueue/config/NewSessionQueueOptions.java:100-110 | java/src/org/openqa/selenium/grid/sessionqueue/config/NewSessionQueueOptions.java:112-122 — there are 8 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 8 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21–26 lines × 2) py/selenium/webdriver/common/log.py:58— py/selenium/webdriver/common/log.py:58-83 | py/selenium/webdriver/common/log.py:111-131 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `py/selenium/webdriver/common/log.py:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 7) py/selenium/webdriver/chrome/__init__.py:24— py/selenium/webdriver/chrome/__init__.py:24-32 | py/selenium/webdriver/edge/__init__.py:24-32 | py/selenium/webdriver/firefox/__init__.py:24-32 | py/selenium/webdriver/ie/__init__.py:24-32 | py/selenium/webdriver/safari/__init__.py:24-32 | py/selenium/webdriver/webkitgtk/__init__.py:24-32 | py/selenium/webdriver/wpewebkit/__init__.py:24-32 — `py/selenium/webdriver/chrome/__init__.py` and `py/selenium/webdriver/edge/__init__.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 9 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (18–20 lines × 5) rust/src/chrome.rs:376— rust/src/chrome.rs:376-395 | rust/src/electron.rs:166-183 | rust/src/firefox.rs:223-242 | rust/src/grid.rs:108-125 | rust/src/iexplorer.rs:122-139 — before extracting anything, compare `rust/src/chrome.rs` and `rust/src/firefox.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rust/src/chrome.rs:376` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) scripts/pinned_browsers.py:53— scripts/pinned_browsers.py:53-91 | scripts/pinned_browsers.py:110-155 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (38–41 lines × 2) scripts/pinned_browsers.py:53— scripts/pinned_browsers.py:53-90 | scripts/pinned_browsers.py:110-150 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/pinned_browsers.py:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
End-of-life runtime: Node.js 18 javascript/selenium-manager/package.json:21— javascript/selenium-manager/package.json declares Node.js 18 as this project's engines.node, and Node.js 18, support ended 2025-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2025-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Coverage not measured — .NET and JavaScript/TypeScript suite — Coverage NOT MEASURED: the .NET half could not be measured — the repository's tests run on Microsoft.Testing.Platform (its build files say so) and wire up no coverage extension for it; the JavaScript/TypeScript half could not be measured — the jest suite in javascript/grid-ui/ ran and not one test passed (● Multiple configurations found:), so the coverage would describe the failed run, not the code. 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.
P3 · Security & performance tooling· SAST runs, but gates no merge · ×1
SAST runs, but gates no merge — `REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
Awaits without ConfigureAwait(false) dotnet/src/support/Events/EventFiringWebDriver.cs:821— `await this.BackAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Duplication concentrated across 7 sibling directories (9 clone groups) javascript/bidi-support/bidi-mutation-listener.js:18— 9 duplicated blocks under javascript/ have copies in at least two of the sibling directories atoms, bidi-support, cdp-support, chrome-driver, ie-driver, selenium-webdriver (+1 more sibling(s) not listed) — 6 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (66 matched lines × 2 locations) · ×1
Duplicated block with local edits (66 matched lines × 2 locations) javascript/selenium-webdriver/bidi/networkTypes.js:247— javascript/selenium-webdriver/bidi/networkTypes.js:247 · javascript/selenium-webdriver/bidi/networkTypes.js:698 — the two spans are one implementation copied and then locally edited — 251 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (43 lines × 2 locations) javascript/selenium-webdriver/bidi/continueRequestParameters.js:24— javascript/selenium-webdriver/bidi/continueRequestParameters.js:24 · javascript/selenium-webdriver/bidi/provideResponseParameters.js:25 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (40 matched lines × 2 locations) · ×1
Duplicated block with local edits (40 matched lines × 2 locations) javascript/selenium-webdriver/project_bidi_schema_test.mjs:351— javascript/selenium-webdriver/project_bidi_schema_test.mjs:351 · javascript/selenium-webdriver/project_bidi_schema_test.mjs:517 — the two spans are one implementation copied and then locally edited — 327 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (32 lines × 2 locations) javascript/atoms/typescript/core/locators.ts:618— javascript/atoms/typescript/core/locators.ts:618 · javascript/atoms/typescript/core/locators.ts:665 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (31 lines × 2 locations) javascript/selenium-webdriver/bidi/browsingContextInspector.js:139— javascript/selenium-webdriver/bidi/browsingContextInspector.js:139 · javascript/selenium-webdriver/bidi/network.js:394 — 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 (29 lines × 3 locations) javascript/selenium-webdriver/bidi/logInspector.js:57— javascript/selenium-webdriver/bidi/logInspector.js:57 · javascript/selenium-webdriver/bidi/network.js:59 · javascript/selenium-webdriver/bidi/scriptManager.js:50 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) javascript/selenium-webdriver/bidi/network.js:155— javascript/selenium-webdriver/bidi/network.js:155 · javascript/selenium-webdriver/bidi/networkInspector.js:62 — 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 (23 lines × 2 locations) javascript/selenium-webdriver/bidi/browsingContextInspector.js:89— javascript/selenium-webdriver/bidi/browsingContextInspector.js:89 · javascript/selenium-webdriver/bidi/networkInspector.js:40 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (21 matched lines × 2 locations) · ×1
Duplicated block with local edits (21 matched lines × 2 locations) javascript/atoms/dom.js:1219— javascript/atoms/dom.js:1219 · javascript/atoms/typescript/get-text.ts:117 — the two spans are one implementation copied and then locally edited — 121 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (21 lines × 2 locations) javascript/webdriver/atoms/storage/local_storage.js:25— javascript/webdriver/atoms/storage/local_storage.js:25 · javascript/webdriver/atoms/storage/session_storage.js:25 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (19 lines × 2 locations) javascript/atoms/action.js:398— javascript/atoms/action.js:398 · javascript/atoms/action.js:458 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 3 locations) javascript/selenium-webdriver/bidi/storage.js:52— javascript/selenium-webdriver/bidi/storage.js:52 · javascript/selenium-webdriver/bidi/storage.js:117 · javascript/selenium-webdriver/bidi/storage.js:159 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication· Duplicated block with local edits (16 matched lines × 2 locations) · ×1
Duplicated block with local edits (16 matched lines × 2 locations) javascript/selenium-webdriver/generate_bidi.mjs:788— javascript/selenium-webdriver/generate_bidi.mjs:788 · javascript/selenium-webdriver/project_bidi_schema.mjs:615 — the two spans are one implementation copied and then locally edited — 136 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (15 lines × 3 locations) javascript/selenium-webdriver/bidi/logInspector.js:102— javascript/selenium-webdriver/bidi/logInspector.js:102 · javascript/selenium-webdriver/bidi/logInspector.js:152 · javascript/selenium-webdriver/bidi/logInspector.js:228 — 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 with local edits (15 matched lines × 2 locations) · ×1
Duplicated block with local edits (15 matched lines × 2 locations) javascript/selenium-webdriver/http/util.js:56— javascript/selenium-webdriver/http/util.js:56 · javascript/selenium-webdriver/http/util.js:112 — the two spans are one implementation copied and then locally edited — 83 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (13 matched lines × 2 locations) · ×1
Duplicated block with local edits (13 matched lines × 2 locations) javascript/selenium-webdriver/bidi/serialization/record.js:254— javascript/selenium-webdriver/bidi/serialization/record.js:254 · javascript/selenium-webdriver/bidi/serialization/record.js:298 — the two spans are one implementation copied and then locally edited — 104 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.
Boundary violation [package:third-party-deep-import] javascript/grid-ui/src/components/LiveView/LiveView.tsx:19— javascript/grid-ui/src/components/LiveView/LiveView.tsx:19 imports @novnc/novnc/lib/rfb, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Complex function implicitRole (cyclomatic 82, cognitive 24) javascript/atoms/typescript/core/accessibility/roles.ts:248— implicitRole has cyclomatic complexity 82 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateValue (cyclomatic 51, cognitive 89) javascript/selenium-webdriver/bidi/serialization/record.js:50— validateValue has cyclomatic complexity 51 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkSchema (cyclomatic 43, cognitive 89) javascript/selenium-webdriver/project_bidi_schema.mjs:873— checkSchema has cyclomatic complexity 43 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function diffAgainstCddl2ts (cyclomatic 43, cognitive 86) javascript/selenium-webdriver/bidi_schema_diff_test.mjs:253— diffAgainstCddl2ts has cyclomatic complexity 43 and cognitive complexity 86; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function build (cyclomatic 39, cognitive 42) javascript/selenium-webdriver/index.js:601— build has cyclomatic complexity 39 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getOverflowState (cyclomatic 32, cognitive 48) javascript/atoms/typescript/core/overflow.ts:40— getOverflowState has cyclomatic complexity 32 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getOverflowState (cyclomatic 31, cognitive 45) javascript/atoms/dom.js:667— getOverflowState has cyclomatic complexity 31 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 get (cyclomatic 29, cognitive 40) · ×1
Complex function get (cyclomatic 29, cognitive 40) javascript/atoms/typescript/get-attribute.ts:28— get has cyclomatic complexity 29 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function nativeName (cyclomatic 28, cognitive 14) javascript/atoms/typescript/core/accessibility/accname.ts:420— nativeName has cyclomatic complexity 28 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validate (cyclomatic 27, cognitive 33) javascript/atoms/typescript/testing/corpus-consistent.mjs:68— validate has cyclomatic complexity 27 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function projectEntry (cyclomatic 26, cognitive 32) javascript/selenium-webdriver/project_bidi_schema.mjs:224— projectEntry has cyclomatic complexity 26 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function escapeCss (cyclomatic 26, cognitive 22) javascript/selenium-webdriver/lib/by.js:67— escapeCss has cyclomatic complexity 26 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function get (cyclomatic 25, cognitive 32) · ×1
Complex function get (cyclomatic 25, cognitive 32) javascript/webdriver/atoms/attribute.js:110— get has cyclomatic complexity 25 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 25, cognitive 24) javascript/selenium-webdriver/test/http/http_test.js:29— (anonymous) has cyclomatic complexity 25 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function computeTextAlternative (cyclomatic 24, cognitive 27) javascript/atoms/typescript/core/accessibility/accname.ts:499— computeTextAlternative has cyclomatic complexity 24 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateDomainFile (cyclomatic 21, cognitive 38) javascript/selenium-webdriver/generate_bidi.mjs:942— generateDomainFile has cyclomatic complexity 21 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function evaluate_ (cyclomatic 19, cognitive 45) javascript/atoms/locators/xpath.js:90— evaluate_ has cyclomatic complexity 19 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function computeContentText (cyclomatic 19, cognitive 28) javascript/atoms/typescript/core/accessibility/accname.ts:328— computeContentText has cyclomatic complexity 19 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isShown_ (cyclomatic 19, cognitive 16) javascript/atoms/dom.js:460— isShown_ has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isShownInternal (cyclomatic 19, cognitive 16) javascript/atoms/typescript/core/shown.ts:86— isShownInternal has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function projectSchema (cyclomatic 18, cognitive 25) javascript/selenium-webdriver/project_bidi_schema.mjs:677— projectSchema has cyclomatic complexity 18 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function focusOnElement (cyclomatic 18, cognitive 24) REDACTED:456— focusOnElement has cyclomatic complexity 18 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function editContent (cyclomatic 18, cognitive 21) javascript/atoms/typescript/core/keyboard.ts:325— editContent has cyclomatic complexity 18 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function positiveSize (cyclomatic 18, cognitive 21) javascript/atoms/typescript/core/shown.ts:127— positiveSize has cyclomatic complexity 18 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function appendVisibleTextLinesFromElementCommon_ (cyclomatic 18, cognitive 20) javascript/atoms/dom.js:1049— appendVisibleTextLinesFromElementCommon_ has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function appendTextFromElementCommon (cyclomatic 18, cognitive 14) javascript/atoms/typescript/get-text.ts:161— appendTextFromElementCommon has cyclomatic complexity 18 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function type (cyclomatic 17, cognitive 24) · ×1
Complex function type (cyclomatic 17, cognitive 24) javascript/atoms/typescript/type.ts:118— type has cyclomatic complexity 17 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function dedupeDefs (cyclomatic 17, cognitive 23) javascript/selenium-webdriver/normalize_bidi_ast.mjs:530— dedupeDefs has cyclomatic complexity 17 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getArgument (cyclomatic 17, cognitive 12) javascript/selenium-webdriver/bidi/protocolValue.js:192— getArgument has cyclomatic complexity 17 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function clear (cyclomatic 16, cognitive 29) javascript/atoms/action.js:86— clear has cyclomatic complexity 16 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function collectUnionMembers (cyclomatic 16, cognitive 29) javascript/selenium-webdriver/generate_bidi.mjs:394— collectUnionMembers has cyclomatic complexity 16 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function displayed (cyclomatic 16, cognitive 17) javascript/atoms/dom.js:600— displayed has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function displayed (cyclomatic 16, cognitive 16) javascript/atoms/typescript/core/shown.ts:191— displayed has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function appendVisibleTextLinesFromNodeInComposedDom_ (cyclomatic 15, cognitive 39) javascript/atoms/dom.js:1363— appendVisibleTextLinesFromNodeInComposedDom_ has cyclomatic complexity 15 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function extractVendor (cyclomatic 15, cognitive 22) javascript/selenium-webdriver/project_bidi_schema.mjs:805— extractVendor has cyclomatic complexity 15 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function moveCaret (cyclomatic 15, cognitive 21) javascript/atoms/typescript/core/keyboard.ts:280— moveCaret has cyclomatic complexity 15 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function hoistInlineRecords (cyclomatic 15, cognitive 21) javascript/selenium-webdriver/normalize_bidi_ast.mjs:233— hoistInlineRecords has cyclomatic complexity 15 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function clickElement (cyclomatic 15, cognitive 17) REDACTED:385— clickElement has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 17) javascript/atoms/typescript/core/inject.ts:132— (anonymous) has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getSize (cyclomatic 15, cognitive 17) javascript/atoms/window.js:221— getSize has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
REDACTED: 3211 lines of code REDACTED:1— REDACTED has 3211 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
javascript/atoms/dom.js: 1303 lines of code javascript/atoms/dom.js:1— javascript/atoms/dom.js has 1303 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/project_bidi_schema_test.mjs · ×1
javascript/selenium-webdriver/project_bidi_schema_test.mjs: 1172 lines of code javascript/selenium-webdriver/project_bidi_schema_test.mjs:1— javascript/selenium-webdriver/project_bidi_schema_test.mjs has 1172 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/generate_bidi.mjs · ×1
javascript/selenium-webdriver/generate_bidi.mjs: 1121 lines of code javascript/selenium-webdriver/generate_bidi.mjs:1— javascript/selenium-webdriver/generate_bidi.mjs has 1121 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/project_bidi_schema.mjs · ×1
javascript/selenium-webdriver/project_bidi_schema.mjs: 1080 lines of code javascript/selenium-webdriver/project_bidi_schema.mjs:1— javascript/selenium-webdriver/project_bidi_schema.mjs has 1080 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/lib/input.js · ×1
javascript/selenium-webdriver/lib/input.js: 978 lines of code javascript/selenium-webdriver/lib/input.js:1— javascript/selenium-webdriver/lib/input.js has 978 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/atoms/keyboard.js · ×1
javascript/atoms/keyboard.js: 938 lines of code javascript/atoms/keyboard.js:1— javascript/atoms/keyboard.js has 938 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 863 lines of code REDACTED:1— REDACTED has 863 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/chromium.js · ×1
javascript/selenium-webdriver/chromium.js: 795 lines of code javascript/selenium-webdriver/chromium.js:1— javascript/selenium-webdriver/chromium.js has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/bidi/networkTypes.js · ×1
javascript/selenium-webdriver/bidi/networkTypes.js: 765 lines of code javascript/selenium-webdriver/bidi/networkTypes.js:1— javascript/selenium-webdriver/bidi/networkTypes.js has 765 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/index.js · ×1
javascript/selenium-webdriver/index.js: 745 lines of code javascript/selenium-webdriver/index.js:1— javascript/selenium-webdriver/index.js has 745 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/firefox.js · ×1
javascript/selenium-webdriver/firefox.js: 713 lines of code javascript/selenium-webdriver/firefox.js:1— javascript/selenium-webdriver/firefox.js has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx · ×1
javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx: 698 lines of code javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx:1— javascript/grid-ui/src/components/RunningSessions/RunningSessions.tsx has 698 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
javascript/atoms/events.js: 687 lines of code javascript/atoms/events.js:1— javascript/atoms/events.js has 687 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
javascript/atoms/action.js: 685 lines of code javascript/atoms/action.js:1— javascript/atoms/action.js has 685 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/atoms/typescript/core/locators.ts · ×1
javascript/atoms/typescript/core/locators.ts: 653 lines of code javascript/atoms/typescript/core/locators.ts:1— javascript/atoms/typescript/core/locators.ts has 653 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/testing/index.js · ×1
javascript/selenium-webdriver/testing/index.js: 640 lines of code javascript/selenium-webdriver/testing/index.js:1— javascript/selenium-webdriver/testing/index.js has 640 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/lib/logging.js · ×1
javascript/selenium-webdriver/lib/logging.js: 637 lines of code javascript/selenium-webdriver/lib/logging.js:1— javascript/selenium-webdriver/lib/logging.js has 637 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/bidi/browsingContext.js · ×1
javascript/selenium-webdriver/bidi/browsingContext.js: 584 lines of code javascript/selenium-webdriver/bidi/browsingContext.js:1— javascript/selenium-webdriver/bidi/browsingContext.js has 584 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/remote/index.js · ×1
javascript/selenium-webdriver/remote/index.js: 557 lines of code javascript/selenium-webdriver/remote/index.js:1— javascript/selenium-webdriver/remote/index.js has 557 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/lib/error.js · ×1
javascript/selenium-webdriver/lib/error.js: 552 lines of code javascript/selenium-webdriver/lib/error.js:1— javascript/selenium-webdriver/lib/error.js has 552 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/atoms/typescript/core/accessibility/accname.ts · ×1
javascript/atoms/typescript/core/accessibility/accname.ts: 550 lines of code javascript/atoms/typescript/core/accessibility/accname.ts:1— javascript/atoms/typescript/core/accessibility/accname.ts has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/lib/http.js · ×1
javascript/selenium-webdriver/lib/http.js: 517 lines of code javascript/selenium-webdriver/lib/http.js:1— javascript/selenium-webdriver/lib/http.js has 517 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/normalize_bidi_ast.mjs · ×1
javascript/selenium-webdriver/normalize_bidi_ast.mjs: 517 lines of code javascript/selenium-webdriver/normalize_bidi_ast.mjs:1— javascript/selenium-webdriver/normalize_bidi_ast.mjs has 517 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 514 lines of code REDACTED:1— REDACTED has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/bidi/scriptManager.js · ×1
javascript/selenium-webdriver/bidi/scriptManager.js: 508 lines of code javascript/selenium-webdriver/bidi/scriptManager.js:1— javascript/selenium-webdriver/bidi/scriptManager.js has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/lib/capabilities.js · ×1
javascript/selenium-webdriver/lib/capabilities.js: 495 lines of code javascript/selenium-webdriver/lib/capabilities.js:1— javascript/selenium-webdriver/lib/capabilities.js has 495 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/lib/accessibility_snapshot.js · ×1
javascript/selenium-webdriver/lib/accessibility_snapshot.js: 483 lines of code javascript/selenium-webdriver/lib/accessibility_snapshot.js:1— javascript/selenium-webdriver/lib/accessibility_snapshot.js has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
javascript/atoms/inject.js: 479 lines of code javascript/atoms/inject.js:1— javascript/atoms/inject.js has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/bidi/index.js · ×1
javascript/selenium-webdriver/bidi/index.js: 475 lines of code javascript/selenium-webdriver/bidi/index.js:1— javascript/selenium-webdriver/bidi/index.js has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
javascript/atoms/mouse.js: 455 lines of code javascript/atoms/mouse.js:1— javascript/atoms/mouse.js has 455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/webdriver/http/http.js · ×1
javascript/webdriver/http/http.js: 452 lines of code javascript/webdriver/http/http.js:1— javascript/webdriver/http/http.js has 452 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/ie.js · ×1
javascript/selenium-webdriver/ie.js: 439 lines of code javascript/selenium-webdriver/ie.js:1— javascript/selenium-webdriver/ie.js has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/lib/by.js · ×1
javascript/selenium-webdriver/lib/by.js: 439 lines of code javascript/selenium-webdriver/lib/by.js:1— javascript/selenium-webdriver/lib/by.js has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/lib/select.js · ×1
javascript/selenium-webdriver/lib/select.js: 434 lines of code javascript/selenium-webdriver/lib/select.js:1— javascript/selenium-webdriver/lib/select.js has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/bidi/protocolValue.js · ×1
javascript/selenium-webdriver/bidi/protocolValue.js: 406 lines of code javascript/selenium-webdriver/bidi/protocolValue.js:1— javascript/selenium-webdriver/bidi/protocolValue.js has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· javascript/selenium-webdriver/lib/until.js · ×1
javascript/selenium-webdriver/lib/until.js: 402 lines of code javascript/selenium-webdriver/lib/until.js:1— javascript/selenium-webdriver/lib/until.js has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~1481 LoC) javascript/atoms/dom.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~1269 LoC) javascript/selenium-webdriver/project_bidi_schema_test.mjs— no import path from any entry point (83 application, 15 tooling, 132 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 (~1043 LoC) javascript/atoms/keyboard.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~986 LoC) REDACTED— no import path from any entry point (83 application, 15 tooling, 132 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 (~787 LoC) javascript/atoms/events.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~759 LoC) javascript/atoms/action.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~619 LoC) REDACTED— no import path from any entry point (83 application, 15 tooling, 132 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 (~537 LoC) javascript/atoms/inject.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~516 LoC) javascript/atoms/mouse.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~512 LoC) javascript/webdriver/http/http.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~459 LoC) javascript/atoms/locators/relative.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~436 LoC) javascript/atoms/window.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~428 LoC) javascript/selenium-webdriver/normalize_bidi_ast_test.mjs— no import path from any entry point (83 application, 15 tooling, 132 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 (~421 LoC) javascript/atoms/touchscreen.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~418 LoC) javascript/webdriver/capabilities.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~365 LoC) javascript/chrome-driver/atoms.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~281 LoC) javascript/webdriver/atoms/element.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~249 LoC) javascript/webdriver/atoms/inject/action.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~220 LoC) javascript/atoms/domcore.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~209 LoC) javascript/atoms/error.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~197 LoC) javascript/atoms/html5/storage.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~192 LoC) javascript/atoms/typescript/testing/corpus-consistent.mjs— no import path from any entry point (83 application, 15 tooling, 132 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 (~191 LoC) javascript/webdriver/atoms/attribute.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~190 LoC) REDACTED— no import path from any entry point (83 application, 15 tooling, 132 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 (~180 LoC) javascript/atoms/frame.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~177 LoC) javascript/webdriver/atoms/inject/dom.js— no import path from any entry point (83 application, 15 tooling, 132 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~164 LoC) javascript/atoms/locators/locators.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~154 LoC) javascript/ie-driver/atoms.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~144 LoC) javascript/atoms/locators/link_text.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~132 LoC) javascript/webdriver/http/corsclient.js— no import path from any entry point (83 application, 15 tooling, 132 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~116 LoC) javascript/atoms/locators/id.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~115 LoC) javascript/atoms/html5/html5_browser.js— no import path from any entry point (83 application, 15 tooling, 132 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 (~113 LoC) javascript/webdriver/atoms/inject/find_element.js— no import path from any entry point (83 application, 15 tooling, 132 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency 'clean-jsdoc-theme' — Declared in javascript/selenium-webdriver/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'has-flag' — Declared in javascript/selenium-webdriver/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'supports-color' — Declared in javascript/selenium-webdriver/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.
Weak hash algorithm third_party/dotnet/devtools/src/generator/Program.cs:85— MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
Third-party script without Subresource Integrity common/src/web/mouse_interaction.html:12— `https://selenium.dev/selenium/web/js/jquery-3.5.1.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 7 such include(s) across the repository's markup.
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.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked javascript/selenium-manager/package.json:31— javascript/selenium-manager/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
Duplicated predicate dotnet/src/webdriver/Remote/DesiredCapabilities.cs:194— `capability == CapabilityType.Platform && capabilityValue is string capabilityValueString` appears character-identically in 2 files — dotnet/src/webdriver/Remote/DesiredCapabilities.cs, dotnet/src/webdriver/Remote/ReadOnlyDesiredCapabilities.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate dotnet/src/webdriver/DevTools/v155/V155Network.cs:314— `e.ResponseErrorReason == null && e.ResponseStatusCode == null` appears character-identically in 3 files — dotnet/src/webdriver/DevTools/v155/V155Network.cs, dotnet/src/webdriver/DevTools/v156/V156Network.cs, dotnet/src/webdriver/DevTools/v157/V157Network.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/chrome/ChromeDriverService.java:302— `!Platform.getCurrent().is(Platform.WINDOWS) && System.getenv("CHROME_LOG_FILE") == null` appears character-identically in 2 files — java/src/org/openqa/selenium/chrome/ChromeDriverService.java, java/src/org/openqa/selenium/edge/EdgeDriverService.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/chrome/ChromeDriverInfo.java:76— `!isAvailable() || !isSupporting(capabilities)` appears character-identically in 2 files — java/src/org/openqa/selenium/chrome/ChromeDriverInfo.java, java/src/org/openqa/selenium/edge/EdgeDriverInfo.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/chromium/ChromiumOptions.java:277— `!name.equals("binary") && !name.equals("extensions") && !name.equals("args")` appears character-identically in 2 files — java/src/org/openqa/selenium/chromium/ChromiumOptions.java, java/src/org/openqa/selenium/grid/node/config/SessionCapabilitiesMutator.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/chromium/ChromiumDriver.java:80— `CHROME.is(name) || EDGE.is(name) || OPERA.is(name)` appears character-identically in 3 files — java/src/org/openqa/selenium/chromium/ChromiumDriver.java, java/src/org/openqa/selenium/remote/AddHasAuthentication.java, java/src/org/openqa/selenium/remote/AddHasLogEvents.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/devtools/v155/v155Network.java:136— `base64Body.getBase64Encoded() != null && base64Body.getBase64Encoded()` appears character-identically in 3 files — java/src/org/openqa/selenium/devtools/v155/v155Network.java, java/src/org/openqa/selenium/devtools/v156/v156Network.java, java/src/org/openqa/selenium/devtools/v157/v157Network.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/grid/security/SecretOptions.java:75— `config.get(SERVER_SECTION, "https-private-key").isPresent() && config.get(SERVER_SECTION, "https-certificate").isPresent()` appears character-identically in 2 files — java/src/org/openqa/selenium/grid/security/SecretOptions.java, java/src/org/openqa/selenium/grid/server/BaseServerOptions.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/json/ConstructorCoercer.java:227— `doubleValue % 1 != 0 || doubleValue < Long.MIN_VALUE || doubleValue > Long.MAX_VALUE` appears character-identically in 2 files — java/src/org/openqa/selenium/json/ConstructorCoercer.java, java/src/org/openqa/selenium/json/JsonTypeCoercer.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/docker/client/V140Adapter.java:80— `endpointsConfig != null && endpointsConfig.size() > 1` appears character-identically in 3 files — java/src/org/openqa/selenium/docker/client/V140Adapter.java, java/src/org/openqa/selenium/docker/client/V144Adapter.java, java/src/org/openqa/selenium/docker/client/V148Adapter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:394— `entry.getKey().startsWith("SE_") || entry.getKey().equalsIgnoreCase("LANGUAGE")` appears character-identically in 2 files — java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java, java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java:360— `eventType == null || eventType.isEmpty()` appears character-identically in 2 files — java/src/org/openqa/selenium/grid/node/k8s/OneShotNode.java, java/src/org/openqa/selenium/grid/node/local/LocalNode.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/net/HostIdentifier.java:47— `host == null && Platform.getCurrent().is(Platform.MAC)` appears character-identically in 2 files — java/src/org/openqa/selenium/net/HostIdentifier.java, java/src/org/openqa/selenium/net/NetworkUtils.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/grid/distributor/selector/DefaultSlotSelector.java:52— `node.hasCapacity(capabilities, slotMatcher) && node.getAvailability() == UP` appears character-identically in 2 files — java/src/org/openqa/selenium/grid/distributor/selector/DefaultSlotSelector.java, java/src/org/openqa/selenium/grid/distributor/selector/GreedySlotSelector.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:76— `port.isPresent() && hostname.isPresent()` appears character-identically in 3 files — java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java, java/src/org/openqa/selenium/grid/sessionmap/config/SessionMapOptions.java, java/src/org/openqa/selenium/grid/sessionqueue/config/NewSessionQueueOptions.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/grid/node/docker/DockerOptions.java:92— `possibleHost.isPresent() && possiblePort.isPresent()` appears character-identically in 2 files — java/src/org/openqa/selenium/grid/node/docker/DockerOptions.java, java/src/org/openqa/selenium/grid/node/relay/RelayOptions.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/bidi/Connection.java:359— `raw.get("id") instanceof Number && (raw.get("result") != null || raw.get("error") != null)` appears character-identically in 2 files — java/src/org/openqa/selenium/bidi/Connection.java, java/src/org/openqa/selenium/devtools/Connection.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/bidi/Connection.java:362— `raw.get("method") instanceof String && raw.get("params") instanceof Map` appears character-identically in 2 files — java/src/org/openqa/selenium/bidi/Connection.java, java/src/org/openqa/selenium/devtools/Connection.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:544— `recordVideo.isPresent() && Boolean.parseBoolean(recordVideo.get().toString())` appears character-identically in 2 files — java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java, java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java:620— `response.isLeft() && response.left() instanceof RetrySessionRequestException` appears character-identically in 2 files — java/src/org/openqa/selenium/grid/distributor/local/LocalDistributor.java, java/src/org/openqa/selenium/grid/distributor/redis/RedisBackedDistributor.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java:578— `routerUsername != null && !routerUsername.isEmpty() && routerPassword != null && !routerPassword.isEmpty()` appears character-identically in 2 files — java/src/org/openqa/selenium/grid/node/docker/DockerSessionFactory.java, java/src/org/openqa/selenium/grid/node/kubernetes/KubernetesSessionFactory.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java:72— `serverOptions.isSecure() || serverOptions.isSelfSigned()` appears character-identically in 3 files — java/src/org/openqa/selenium/grid/distributor/config/DistributorOptions.java, java/src/org/openqa/selenium/grid/sessionmap/config/SessionMapOptions.java, java/src/org/openqa/selenium/grid/sessionqueue/config/NewSessionQueueOptions.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate javascript/atoms/dom.js:552— `/^[\s]*$/.test(text) && /[\n\r\t]/.test(text)` appears character-identically in 2 files — javascript/atoms/dom.js, javascript/atoms/typescript/core/shown.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate javascript/selenium-webdriver/generate_bidi.mjs:350— `def.Type !== 'group' || !Array.isArray(def.Properties)` appears character-identically in 2 files — javascript/selenium-webdriver/generate_bidi.mjs, javascript/selenium-webdriver/normalize_bidi_ast.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate javascript/atoms/typescript/core/form.ts:63— `form.ownerDocument.defaultView || window` appears character-identically in 2 files — javascript/atoms/typescript/core/form.ts, javascript/atoms/typescript/submit.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
+ 15 more in this group — see findings.md.
P10 · Library API & versioning· Public type used only inside its own library · ×37
Public type used only inside its own library dotnet/src/webdriver/BiDi/BiDi.cs:25— `OpenQA.Selenium.BiDi.BiDi` (dotnet/src/webdriver/BiDi/BiDi.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextEvent.cs:24— `OpenQA.Selenium.BiDi.BrowsingContext.BrowsingContextEvent` (dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextEvent.cs:24— `OpenQA.Selenium.BiDi.BrowsingContext.BrowsingContextEvent` (dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Input/InputEvent.cs:24— `OpenQA.Selenium.BiDi.Input.InputEvent` (dotnet/src/webdriver/BiDi/Input/InputEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Input/InputEvent.cs:24— `OpenQA.Selenium.BiDi.Input.InputEvent` (dotnet/src/webdriver/BiDi/Input/InputEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Json/Converters/CamelCaseEnumConverter.cs:25— `OpenQA.Selenium.BiDi.Json.Converters.CamelCaseEnumConverter` (dotnet/src/webdriver/BiDi/Json/Converters/CamelCaseEnumConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Json/Converters/CamelCaseEnumConverter.cs:25— `OpenQA.Selenium.BiDi.Json.Converters.CamelCaseEnumConverter` (dotnet/src/webdriver/BiDi/Json/Converters/CamelCaseEnumConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:25— `OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetConverter` (dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:38— `OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetSecondsConverter` (dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:38) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:25— `OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetConverter` (dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:38— `OpenQA.Selenium.BiDi.Json.Converters.DateTimeOffsetSecondsConverter` (dotnet/src/webdriver/BiDi/Json/Converters/DateTimeOffsetConverter.cs:38) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Json/Converters/KebabCaseEnumConverter.cs:25— `OpenQA.Selenium.BiDi.Json.Converters.KebabCaseEnumConverter` (dotnet/src/webdriver/BiDi/Json/Converters/KebabCaseEnumConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Json/Converters/KebabCaseEnumConverter.cs:25— `OpenQA.Selenium.BiDi.Json.Converters.KebabCaseEnumConverter` (dotnet/src/webdriver/BiDi/Json/Converters/KebabCaseEnumConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Json/Converters/OptionalConverter.cs:25— `OpenQA.Selenium.BiDi.Json.Converters.OptionalConverter` (dotnet/src/webdriver/BiDi/Json/Converters/OptionalConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Json/Converters/OptionalConverter.cs:25— `OpenQA.Selenium.BiDi.Json.Converters.OptionalConverter` (dotnet/src/webdriver/BiDi/Json/Converters/OptionalConverter.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Log/LogEvent.cs:24— `OpenQA.Selenium.BiDi.Log.LogEvent` (dotnet/src/webdriver/BiDi/Log/LogEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Network/NetworkEvent.cs:24— `OpenQA.Selenium.BiDi.Network.NetworkEvent` (dotnet/src/webdriver/BiDi/Network/NetworkEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Script/ScriptEvent.cs:24— `OpenQA.Selenium.BiDi.Script.ScriptEvent` (dotnet/src/webdriver/BiDi/Script/ScriptEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Script/ScriptEvent.cs:24— `OpenQA.Selenium.BiDi.Script.ScriptEvent` (dotnet/src/webdriver/BiDi/Script/ScriptEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Speculation/SpeculationEvent.cs:24— `OpenQA.Selenium.BiDi.Speculation.SpeculationEvent` (dotnet/src/webdriver/BiDi/Speculation/SpeculationEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/BiDi/Speculation/SpeculationEvent.cs:24— `OpenQA.Selenium.BiDi.Speculation.SpeculationEvent` (dotnet/src/webdriver/BiDi/Speculation/SpeculationEvent.cs:24) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/DefaultFileDetector.cs:28— `OpenQA.Selenium.DefaultFileDetector` (dotnet/src/webdriver/DefaultFileDetector.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/DefaultFileDetector.cs:28— `OpenQA.Selenium.DefaultFileDetector` (dotnet/src/webdriver/DefaultFileDetector.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/DevTools/CommandResponseTypeMap.cs:27— `OpenQA.Selenium.DevTools.CommandResponseTypeMap` (dotnet/src/webdriver/DevTools/CommandResponseTypeMap.cs:27) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library dotnet/src/webdriver/DevTools/CommandResponseTypeMap.cs:27— `OpenQA.Selenium.DevTools.CommandResponseTypeMap` (dotnet/src/webdriver/DevTools/CommandResponseTypeMap.cs:27) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Selenium.Support.Tests`, `Selenium.Testing.NUnit`, `Selenium.WebDriver.Remote.Tests`, `Selenium.WebDriver.Tests`, `Selenium.WebDriver.UnitTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Fat interface: IJavaScriptEngine (20 members) dotnet/src/webdriver/IJavaScriptEngine.cs:27— `IJavaScriptEngine` declares 20 members: `JavaScriptCallbackExecuted`, `JavaScriptExceptionThrown`, `JavaScriptConsoleApiCalled`, `DomMutated`, `InitializationScripts`, `ScriptCallbackBindings`, `StartEventMonitoring`, `StopEventMonitoring`, `EnableDomMutationMonitoring`, `DisableDomMutationMonitoring`, `AddInitializationScript`, `RemoveInitializationScript`, `ClearInitializationScripts`, `PinScript`, `UnpinScript`, `AddScriptCallbackBinding`, `RemoveScriptCallbackBinding`, `ClearScriptCallbackBindings`, `ClearAll`, `Reset`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IWebElement (16 members) dotnet/src/webdriver/IWebElement.cs:31— `IWebElement` declares 16 members: `TagName`, `Text`, `Enabled`, `Selected`, `Location`, `Size`, `Displayed`, `Clear`, `SendKeys`, `Submit`, `Click`, `GetAttribute`, `GetDomAttribute`, `GetDomProperty`, `GetCssValue`, `GetShadowRoot`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IBiDi (19 members) dotnet/src/webdriver/BiDi/IBiDi.cs:34— `IBiDi` declares 19 members under just 15 distinct name(s): `Browser`, `BrowsingContext`, `Emulation`, `Input`, `Log`, `Network`, `Script`, `Storage`, `WebExtension`, `StatusAsync`, `NewAsync`, `EndAsync`, `SubscribeAsync`, `SubscribeAsync`, `SubscribeAsync`, `SubscribeAsync`, `StreamAsync`, `StreamAsync`, `AsModule`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: IBrowsingContextModule (28 members) dotnet/src/webdriver/BiDi/BrowsingContext/IBrowsingContextModule.cs:22— `IBrowsingContextModule` declares 28 members: `ActivateAsync`, `CaptureScreenshotAsync`, `CloseAsync`, `CreateAsync`, `GetTreeAsync`, `HandleUserPromptAsync`, `LocateNodesAsync`, `NavigateAsync`, `ContextCreated`, `ContextDestroyed`, `DomContentLoaded`, `DownloadEnd`, `DownloadWillBegin`, `FragmentNavigated`, `HistoryUpdated`, `Load`, `NavigationAborted`, `NavigationCommitted`, `NavigationFailed`, `NavigationStarted`, `UserPromptClosed`, `UserPromptOpened`, `PrintAsync`, `ReloadAsync`, `SetViewportAsync`, `StartScreencastAsync`, `StopScreencastAsync`, `TraverseHistoryAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: INetworkModule (18 members) dotnet/src/webdriver/BiDi/Network/INetworkModule.cs:22— `INetworkModule` declares 18 members: `AddDataCollectorAsync`, `AddInterceptAsync`, `DisownDataAsync`, `ContinueRequestAsync`, `ContinueResponseAsync`, `ContinueWithAuthAsync`, `FailRequestAsync`, `GetDataAsync`, `AuthRequired`, `BeforeRequestSent`, `FetchError`, `ResponseCompleted`, `ResponseStarted`, `ProvideResponseAsync`, `RemoveDataCollectorAsync`, `RemoveInterceptAsync`, `SetCacheBehaviorAsync`, `SetExtraHeadersAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: NodeRegistry (18 abstract methods) java/src/org/openqa/selenium/grid/distributor/NodeRegistry.java:38— `NodeRegistry` declares 18 abstract methods: `add`, `drain`, `getActiveSlots`, `getAvailableNodes`, `getDownNodeCount`, `getIdleSlots`, `getNode`, `getNode`, `getStatus`, `getUpNodeCount`, `getUpNodes`, `refresh`, `register`, `remove`, `reserve`, `runHealthChecks`, `setSession`, `updateNodeAvailability`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 18 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: WebElement (16 abstract methods) java/src/org/openqa/selenium/WebElement.java:32— `WebElement` declares 16 abstract methods: `clear`, `click`, `findElement`, `findElements`, `getAttribute`, `getCssValue`, `getLocation`, `getRect`, `getSize`, `getTagName`, `getText`, `isDisplayed`, `isEnabled`, `isSelected`, `sendKeys`, `submit`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
redundant comment REDACTED:391— "Wait for process to exit" repeats the code it sits on: 3 of its 3 words (wait, process, exit) are already in `await WaitForProcessExitAsync(process, timeoutCts.Token).ConfigureAwait(false);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment dotnet/src/webdriver/Firefox/FirefoxDriver.cs:189— "Add the custom commands unique to Firefox" repeats the code it sits on: 4 of its 5 words (add, custom, commands, firefox) are already in `this.AddCustomFirefoxCommands();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment dotnet/test/webdriver/Firefox/FirefoxDriverTests.cs:207— "Switch to the new window." repeats the code it sits on: 3 of its 3 words (switch, new, window) are already in `Driver.SwitchTo().Window(newWinHandle);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment javascript/atoms/touchscreen.js:298— 5 comments in this file only repeat the code they sit on (lines 298, 301, 306, 336, 367), for example "Fire a mousemove event.". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment javascript/selenium-webdriver/common/seleniumManager.js:57— "Set the flag to true after printing the debug message" repeats the code it sits on: 5 of its 6 words (set, true, printing, debug, message) are already in `debugMessagePrinted = true // Set the flag to true`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment javascript/selenium-webdriver/test/bidi/permissions_test.js:123— "Set permission only for the user context" repeats the code it sits on: 4 of its 5 words (set, permission, user, context) are already in `await permission.setPermission({ name: 'geolocation' }, PermissionState.GRANTED, originValue, userContext)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment javascript/selenium-webdriver/test/bidi/storage_test.js:130— "Create a new browsing context with the user context" repeats the code it sits on: 4 of its 5 words (create, new, context, user) are already in `const createParams = new CreateContextParameters().userContext(userContext)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Silent fallback default in catch py/test/selenium/webdriver/common/network.py:42— `get_lan_ip` swallows every exception into `return '0.0.0.0'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch javascript/atoms/locators/id.js:86— `bot.locators.id.many` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch javascript/grid-ui/src/components/Node/Node.tsx:87— `Node` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch javascript/selenium-webdriver/io/index.js:223— `findInPath` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch third_party/closure/goog/html/safeurl.js:759— `goog.html.SafeUrl.extractScheme` swallows every exception into `return 'https:'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Orphaned file dotnet/src/webdriver/Edge/EdgeOptions.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file dotnet/src/webdriver/Chrome/ChromeOptions.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file dotnet/src/webdriver/BiDi/Json/Converters/SpecialNumberConverter.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file dotnet/src/webdriver/DevTools/Json/StringConverter.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Pass-through layer dotnet/src/webdriver/DevTools/v155/V155Log.cs:27— V155Log: all 3 public methods forward their arguments unchanged to adapter and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call adapter directly, or give the layer a job.
Pass-through layer dotnet/src/webdriver/DevTools/v156/V156Log.cs:27— V156Log: all 3 public methods forward their arguments unchanged to adapter and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call adapter directly, or give the layer a job.
Pass-through layer dotnet/src/webdriver/DevTools/v157/V157Log.cs:27— V157Log: all 3 public methods forward their arguments unchanged to adapter and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call adapter directly, or give the layer a job.
P10 · Library API & versioning· Implementation type on the public API · ×3
Implementation type on the public API dotnet/src/webdriver/Interactions/ICoordinates.cs:27— 3 public types in `OpenQA.Selenium.Interactions.Internal` are marked as implementation by their own namespace, folder or name: `ICoordinates` (dotnet/src/webdriver/Interactions/ICoordinates.cs:27, `Internal`), `ICoordinates` (dotnet/src/webdriver/Interactions/ICoordinates.cs:27, `Internal`), `ICoordinates` (dotnet/src/webdriver/Interactions/ICoordinates.cs:27, `Internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API dotnet/src/webdriver/Internal/AndroidOptions.cs:25— 15 public types in `OpenQA.Selenium.Internal` are marked as implementation by their own namespace, folder or name: `AndroidOptions` (dotnet/src/webdriver/Internal/AndroidOptions.cs:25, `Internal`), `AndroidOptions` (dotnet/src/webdriver/Internal/AndroidOptions.cs:25, `Internal`), `AndroidOptions` (dotnet/src/webdriver/Internal/AndroidOptions.cs:25, `Internal`), `Base64UrlEncoder` (dotnet/src/webdriver/Internal/Base64UrlEncoder.cs:32, `Internal`), `Base64UrlEncoder` (dotnet/src/webdriver/Internal/Base64UrlEncoder.cs:32, `Internal`), `Base64UrlEncoder` (dotnet/src/webdriver/Internal/Base64UrlEncoder.cs:32, `Internal`), `IFindsElement` (dotnet/src/webdriver/Internal/IFindsElement.cs:27, `Internal`), `IFindsElement` (dotnet/src/webdriver/Internal/IFindsElement.cs:27, `Internal`), and 7 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API dotnet/src/webdriver/Internal/Logging/FileLogHandler.cs:25— 45 public types in `OpenQA.Selenium.Internal.Logging` are marked as implementation by their own namespace, folder or name: `FileLogHandler` (dotnet/src/webdriver/Internal/Logging/FileLogHandler.cs:25, `Internal`), `FileLogHandler` (dotnet/src/webdriver/Internal/Logging/FileLogHandler.cs:25, `Internal`), `FileLogHandler` (dotnet/src/webdriver/Internal/Logging/FileLogHandler.cs:25, `Internal`), `ILogContext` (dotnet/src/webdriver/Internal/Logging/ILogContext.cs:25, `Internal`), `ILogContext` (dotnet/src/webdriver/Internal/Logging/ILogContext.cs:25, `Internal`), `ILogContext` (dotnet/src/webdriver/Internal/Logging/ILogContext.cs:25, `Internal`), `ILogHandler` (dotnet/src/webdriver/Internal/Logging/ILogHandler.cs:25, `Internal`), `ILogHandler` (dotnet/src/webdriver/Internal/Logging/ILogHandler.cs:25, `Internal`), and 37 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 35 significant file(s) lose their only recent owner: dotnet/src/webdriver/BiDi/Broker.cs, dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextModule.cs, dotnet/src/webdriver/BiDi/Network/NetworkModule.cs, dotnet/src/webdriver/BiDi/Emulation/EmulationModule.cs, dotnet/src/webdriver/BiDi/Emulation/SetMediaFeaturesOverride.cs, dotnet/src/webdriver/BiDi/EventDispatcher.cs, dotnet/src/webdriver/Internal/Logging/LogContext.cs, dotnet/src/webdriver/BiDi/BiDi.cs (+27 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (36 single-owned of 215 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 215 of the 519 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: dotnet/src/webdriver/InitializationScript.cs.
ADR not followed: 17685. The network async/event API docs/decisions/17685-network-handler-behavior.md:146— docs/decisions/17685-network-handler-behavior.md:146 rules out `submit`, but production code uses it: javascript/webdriver/atoms/inject/action.js:56, javascript/webdriver/atoms/inject/action.js:57, REDACTED:3117, javascript/atoms/index.ts:63, javascript/atoms/action.js:259 (+8 more). Remove the use, or supersede the record if the decision changed.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion dotnet/src/webdriver/Selenium.WebDriver.csproj:1— `Selenium.WebDriver(net462)` overshoots its size bounds (44026 LoC, 730 public types across 33 namespaces). 1 of 9 project(s) overshoot their size bounds, lowering Project Cohesion to 7.8/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 4 of 215 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 215 of the 519 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: dotnet/src/webdriver/Edge/EdgeOptions.cs, dotnet/src/webdriver/Chrome/ChromeOptions.cs, dotnet/src/webdriver/BiDi/Json/Converters/SpecialNumberConverter.cs, dotnet/src/webdriver/DevTools/Json/StringConverter.cs. 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.
DM9 · Scattered domain decisions· Rule about [DriverPathFromEnvironment, DriverServicePath] decided in 4 places · ×1
Rule about [DriverPathFromEnvironment, DriverServicePath] decided in 4 places — OpenQA.Selenium.DriverService's [DriverPathFromEnvironment, DriverServicePath] are judged in OpenQA.Selenium.Chromium.ChromiumDriver, OpenQA.Selenium.Firefox.FirefoxDriver, OpenQA.Selenium.IE.InternetExplorerDriver, OpenQA.Selenium.Safari.SafariDriver — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions· Rule about [height, width] decided in 3 places · ×1
Rule about [height, width] decided in 3 places — javascript.atoms.typescript.core.geometry.Rect's [height, width] are judged in javascript.atoms.typescript.click, javascript.atoms.typescript.core.overflow, javascript.atoms.typescript.core.shown — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions· Measurement [height, width] produced in 5 places · ×1
Measurement [height, width] produced in 5 places — org.openqa.selenium.Dimension's [height, width] are built independently in org.openqa.selenium.Rectangle, org.openqa.selenium.grid.node.docker.DockerSessionFactory, org.openqa.selenium.grid.node.kubernetes.KubernetesSessionFactory, org.openqa.selenium.remote.RemoteWebElement, org.openqa.selenium.remote.RemoteWindow — the same reading, produced twice. Two producers can disagree without either looking wrong on its own: whichever population, filter or rounding one of them applies, the other need not, and nothing compares them. Give the measurement ONE producer and let the other call it.
DM9 · Scattered domain decisions· Measurement [x, y] produced in 3 places · ×1
Measurement [x, y] produced in 3 places — org.openqa.selenium.Point's [x, y] are built independently in org.openqa.selenium.Rectangle, org.openqa.selenium.remote.RemoteWebElement, org.openqa.selenium.remote.RemoteWindow — the same reading, produced twice. Two producers can disagree without either looking wrong on its own: whichever population, filter or rounding one of them applies, the other need not, and nothing compares them. Give the measurement ONE producer and let the other call it.
README/code drift common/src/web/accessibility/README.md:4— common/src/web/accessibility/README.md links to `../../../../docs/decisions/18205-accessibility-tree-snapshot.md`, but `docs/decisions/18205-accessibility-tree-snapshot.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 13 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
Null-forgiving operator (`!`) suppressions override nullable warnings — ~0.6 `!` suppressions per 1k syntax nodes — 6 suppression(s) across the 10181 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Skipped (documented): CanHandleSecureCookie dotnet/test/webdriver/CookieTests.cs:468— Skipped with a documented reason — a deferral, not lazy debt: Unable to open secure url
Skipped (documented): ShouldRetainCookieSecure dotnet/test/webdriver/CookieTests.cs:484— Skipped with a documented reason — a deferral, not lazy debt: Unable to open secure url
Skipped (documented): VerifyEntryAddedAndClearLog dotnet/test/webdriver/DevTools/DevToolsLogTests.cs:27— Skipped with a documented reason — a deferral, not lazy debt: Unable to open secure url
Skipped (documented): VerifyRequestReceivedFromCacheAndResponseBody dotnet/test/webdriver/DevTools/DevToolsNetworkTests.cs:175— Skipped with a documented reason — a deferral, not lazy debt: The request ID is not getting added to cache
Skipped (documented): VerifyCertificatesAndOverrideUserAgent dotnet/test/webdriver/DevTools/DevToolsNetworkTests.cs:294— Skipped with a documented reason — a deferral, not lazy debt: Unable to open secure url
Skipped (documented): VerifySignedExchangeReceived dotnet/test/webdriver/DevTools/DevToolsNetworkTests.cs:448— Skipped with a documented reason — a deferral, not lazy debt: Unable to open secure url
Skipped (documented): CanListDownloadableFiles dotnet/test/webdriver/DownloadsTests.cs:40— Skipped with a documented reason — a deferral, not lazy debt: Needs to run with Remote WebDriver
Skipped (documented): CanDownloadFile dotnet/test/webdriver/DownloadsTests.cs:51— Skipped with a documented reason — a deferral, not lazy debt: Needs to run with Remote WebDriver
Skipped (documented): CanDeleteFiles dotnet/test/webdriver/DownloadsTests.cs:69— Skipped with a documented reason — a deferral, not lazy debt: Needs to run with Remote WebDriver
Skipped (documented): ShouldThrowExceptionIfExecutingOnNoPage dotnet/test/webdriver/ExecutingJavascriptTests.cs:732— Skipped with a documented reason — a deferral, not lazy debt: Reason for ignore: Failure indicates hang condition, which would break the test suite. Really needs a timeout set.
Skipped (documented): ShouldBeAbleToAccessPagesWithAnInsecureSslCertificate dotnet/test/webdriver/PageLoadingTests.cs:275— Skipped with a documented reason — a deferral, not lazy debt: Unable to open secure url
doc comments repeat the names javascript/atoms/test/text_util.js:50— 1 of 7 documented parameters and 0 of 63 summaries in `@selenium/atoms` only repeat the member or parameter name (e.g. "The name of the current test." for `testName`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names dotnet/src/support/Events/EventFiringWebDriver.cs:1035— 2 of 116 documented parameters and 2 of 225 summaries in `Selenium.Support` only repeat the member or parameter name (e.g. "The index of the" for `frameIndex`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names dotnet/src/webdriver/By.cs:82— 43 of 1211 documented parameters and 65 of 2409 summaries in `Selenium.WebDriver(net462)` only repeat the member or parameter name (e.g. "Gets the value of the mechanism for this class instance." for `Mechanism`). 6 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names javascript/selenium-webdriver/bidi/browser.js:38— 35 of 869 documented parameters and 27 of 1002 summaries in `selenium-webdriver` only repeat the member or parameter name (e.g. "Creates a new user context." for `createUserContext`). 42 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 41 file(s) — `dotnet/src/webdriver/BiDi/Browser/BrowserModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextInputModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextLogModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextModule.cs`, `dotnet/src/webdriver/BiDi/BrowsingContext/BrowsingContextNetworkModule.cs`, … (+36 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1d51a-646a-713c-9809-42fc1d1a06a5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 2 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 190 · Warnings: 1394 · Recommendations: 127 · Info: 18 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 13-11-2026 @ 13:30 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.